-
-
Notifications
You must be signed in to change notification settings - Fork 13.3k
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
Comments
Bumping this issue because it has been open for 7 days with no activity. Closing automatically in 7 days unless it becomes active again. |
Indeed, everything is so. Exactly the same problem and it is relevant. |
Bumping this issue because it has been open for 7 days with no activity. Closing automatically in 7 days unless it becomes active again. |
I think this issue is still relevant. |
Bumping this issue because it has been open for 7 days with no activity. Closing automatically in 7 days unless it becomes active again. |
It seems that most of the bugs are fixed by this bot |
Bumping this issue because it has been open for 7 days with no activity. Closing automatically in 7 days unless it becomes active again. |
Closing due to inactivity. |
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:
--
Let me know if you need further clarification or help in solving this.
Thank you very much upfront! 😄
The text was updated successfully, but these errors were encountered: