Skip to content
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

[Bug]: Crash if lago is defined as callback with last main branch #4224

Closed
superpoussin22 opened this issue Jun 16, 2024 · 4 comments
Closed
Labels
bug Something isn't working

Comments

@superpoussin22
Copy link

What happened?

just test the last main branch and have a crash of litellm when lago is used as callback

Relevant log output

File "/usr/local/lib/python3.11/site-packages/litellm/proxy/utils.py", line 247, in _init_litellm_callbacks
"NameError: name 'LagoLogger' is not defined",

Twitter / LinkedIn details

No response

@superpoussin22 superpoussin22 added the bug Something isn't working label Jun 16, 2024
@ishaan-jaff
Copy link
Contributor

cc @krrishdholakia might be related to recent changed in utils.py

@krrishdholakia
Copy link
Contributor

Fixed here - 2623bb2

should be live in v1.40.16+.

@superpoussin22 can we setup a direct support channel? Would love to learn how you're using litellm today

@superpoussin22
Copy link
Author

@krrishdholakia
no more error, will see if lago receive the infos but I'm confident.
No prob to exchange on litellm

@krrishdholakia
Copy link
Contributor

@superpoussin22 how do you use litellm today?

(want to learn so we can improve for a specific use-case)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants