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

Fixed extra noise in logs from litellm routers #363

Merged
merged 1 commit into from
Sep 11, 2024

Conversation

whitead
Copy link
Collaborator

@whitead whitead commented Sep 11, 2024

Finally figured it out!

@whitead whitead changed the title Solved noisy logs Fixed extra noise in logs from litellm routers Sep 11, 2024
@@ -23,7 +23,7 @@ dependencies = [
"fhaviary[llm]>=0.6", # For info on Message
"html2text", # TODO: evaluate moving to an opt-in dependency
"httpx",
"litellm",
"litellm>=1.44", # to prevent sys.stdout on router creation
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Our internal envs pins an incompatible range with this, fyi. Maybe we should move the internal one to use LiteLLM router and/or not Anthropic in CI

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok - I tried to see if there was a compatible version with both - but there's none.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if we can pin litellm this way in just dev dependencies.

Do you think the verbose logs you're hitting impact all users (so we want to pin in core deps), or just your machine for development?

@whitead whitead merged commit 73d12ff into september-2024-release Sep 11, 2024
3 checks passed
@whitead whitead deleted the litellm-logging branch September 11, 2024 15:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants