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]: LiteLLM conflicts with OpenAI #471

Open
3 tasks
areibman opened this issue Oct 29, 2024 · 2 comments Β· May be fixed by #480
Open
3 tasks

[Bug]: LiteLLM conflicts with OpenAI #471

areibman opened this issue Oct 29, 2024 · 2 comments Β· May be fixed by #480
Assignees
Labels
bug Something isn't working

Comments

@areibman
Copy link
Contributor

Contact Details

No response

πŸ“¦ Package Version

0.3.14

🎞️ Framework Version

openai==1.52.2, litellm==1.50.2

πŸ”Ž Describe the Bug

LiteLLM alone: Works
image

OpenAI alone: Works
image

Import both OpenAI and LiteLLM - Doesn't Work
image

Same does not apply when you only use LiteLLM
image

🀝 Contribution

  • Yes, I'd be happy to submit a pull request with these changes.
  • I need some guidance on how to contribute.
  • I'd prefer the AgentOps team to handle this update.
@areibman areibman added bug Something isn't working help wanted Extra attention is needed labels Oct 29, 2024
@sarath59
Copy link

Working on this

@teocns teocns linked a pull request Oct 31, 2024 that will close this issue
@the-praxs the-praxs linked a pull request Nov 6, 2024 that will close this issue
@teocns
Copy link
Contributor

teocns commented Nov 14, 2024

How does LLMTracker co-live with the instrumentation provider? Also what's its deprecation status? do we have a feature flag?
I am feeling they collide thus causing issues, but without knowing specifics I can only guess

@areibman areibman removed the help wanted Extra attention is needed label Nov 26, 2024
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

Successfully merging a pull request may close this issue.

3 participants