-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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]: Incorrect parsing of new bedrock model names #6644
Comments
This was resolved in the recent versions |
I'm still seeing the issue for us.anthropic.claude-3-5-haiku-20241022-v1:0. The other model us.anthropic.claude-3-5-sonnet-20241022-v2:0 or us.anthropic.claude-3-5-sonnet-20240620-v1:0 work fine though. |
Actually i confused the client version with the proxy image. Updating the image to 1.52.10 fixed the issue.
|
I'm getting [Errno -2] Name or service not known for |
Works fine with completion in python sdk |
hi @bhushitagarwal-circle - curious do you use LiteLLM Proxy in production or are you evaluating it ? If yes, we'd love to hop on a call to get your feedback on how we can improve. Sharing our calendly for your convenience https://calendly.com/d/4mp-gd3-k5k/litellm-1-1-onboarding-chat |
What happened?
The new names for models released on bedrock have region prepended to them, example,
us.anthropic.claude-3-5-sonnet-20241022-v2:0
for new 3.5 sonnet,us.anthropic.claude-3-5-haiku-20241022-v1:0
for new 3.5 haiku,us.meta.llama3-2-90b-instruct-v1:0
for meta 3.2 vision instruct.This breaks the parsing of
provider
in the bedrock logic as it tries to separate the model name by.
and fetch the first element.Relevant log output
Twitter / LinkedIn details
No response
The text was updated successfully, but these errors were encountered: