-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LiteLLM integration is broken #2830
Comments
I am experiencing the same issue. An even simpler reproduction would be this (without a dependency on LiteLLM):
This bug also seems to have been introduced in
Disclaimer: I am not really familiar with the codebase, so feel free to correct me. But as far as I remember and understood, all properties are wrapped in This also seems to be related to this issue (for some strange reason I cannot reference it properly) I wrote a small helper that seems to get rid of the issue by recursively converting the wrapped object to its "Python equivalent":
Then, simply unboxing the value before copying should work just as expected:
|
Should be resolved with this set of PRs: |
Script to reproduce:
Stack Trace:
Removing the
self.system_prompt
usage fromweave.Model
predict
seems to fix it?!Claude response
I see the issue. The error occurs because LiteLLM is trying to do a deep copy of the messages, and there seems to be a threading lock object getting caught up in the attribute reference. This is likely due to how Weave handles class attributes internally.
The text was updated successfully, but these errors were encountered: