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

Problems with fallback configuration #855

Open
rodrigoSantosZup opened this issue Jan 2, 2025 · 0 comments
Open

Problems with fallback configuration #855

rodrigoSantosZup opened this issue Jan 2, 2025 · 0 comments
Labels
bug Something isn't working triage

Comments

@rodrigoSantosZup
Copy link

What Happened?

When it's instantiated a client for portkey, and invoked the chat.completions.create function, we found some possible problems when we configure the fallback process.

  1. No matter if i overload the custom_host field inside config payload. The custom host never changes when we trigger the endpoint to use other deployments.
    image

  2. i've already passed the azure api_version when the client was instantiated, but if i do not pass again on fallback config, the result will be a 404 not found because portkey tries to hit the model endpoint with undefined apiVersion.
    image

  3. With this configuration, i got the fallback, but it always happen, no matter the configuration to trigger only when receive a 429 status code.
    image

What Should Have Happened?

No response

Relevant Code Snippet

No response

Your Twitter/LinkedIn

https://www.linkedin.com/in/rodrigo-costa-59203632/

@rodrigoSantosZup rodrigoSantosZup added the bug Something isn't working label Jan 2, 2025
@github-actions github-actions bot added the triage label Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage
Projects
None yet
Development

No branches or pull requests

1 participant