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

API POST request fails if no Provider/no Auto Provider allowed #2222

Closed
SpecialAro opened this issue Sep 12, 2024 · 8 comments
Closed

API POST request fails if no Provider/no Auto Provider allowed #2222

SpecialAro opened this issue Sep 12, 2024 · 8 comments
Assignees
Labels
bug Something isn't working stale

Comments

@SpecialAro
Copy link

Bug description
Previously, when using version v0.3.0.7 I could make a request using the API at http://localhost:1337/v1/chat/completions I could easily not specify the Provider and at each request, a different provider was used. Now, using the latest version, if I don't specify the provider when making the POST call the request fails. Specifying a provider allows me to get a successful POST request, though, it doesn't allow rotation of providers (that was present in v0.3.0.7)

Steps to reproduce:

  1. Use v0.3.0.7
  2. Make POST request WITHOUT specifying "provider" in body
  3. Watch that providers rotate at each request (which is the behaviour I intend)
    --
  4. Use latest tag
  5. Make POST request WITHOUT specifying "provider" in body
  6. POST Request fails (this is also an issue by itself)
  7. Make POST request specifying "provider" in body
  8. POST Request succeeds but does not allow me to rotate providers at each request (as in v0.3.0.7)

Let me know if you need further clarification or help in solving this.

Thank you very much upfront! 😄

@SpecialAro SpecialAro added the bug Something isn't working label Sep 12, 2024
Copy link

Bumping this issue because it has been open for 7 days with no activity. Closing automatically in 7 days unless it becomes active again.

@github-actions github-actions bot added the stale label Sep 20, 2024
@svmrw
Copy link

svmrw commented Sep 23, 2024

Indeed, everything is so. Exactly the same problem and it is relevant.

@github-actions github-actions bot removed the stale label Sep 24, 2024
Copy link

github-actions bot commented Oct 1, 2024

Bumping this issue because it has been open for 7 days with no activity. Closing automatically in 7 days unless it becomes active again.

@github-actions github-actions bot added the stale label Oct 1, 2024
@SpecialAro
Copy link
Author

I think this issue is still relevant.

@github-actions github-actions bot removed the stale label Oct 3, 2024
Copy link

Bumping this issue because it has been open for 7 days with no activity. Closing automatically in 7 days unless it becomes active again.

@github-actions github-actions bot added the stale label Oct 13, 2024
@svmrw
Copy link

svmrw commented Oct 13, 2024

It seems that most of the bugs are fixed by this bot

@github-actions github-actions bot removed the stale label Oct 14, 2024
Copy link

Bumping this issue because it has been open for 7 days with no activity. Closing automatically in 7 days unless it becomes active again.

Copy link

Closing due to inactivity.

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

No branches or pull requests

3 participants