-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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
Is the timeout logic handling correct? #454
Comments
Follow-on from the above: in the
This is causing issues if that Getting
So the caller should probably check if response is not a dict then act accordingly? |
@afourney is this related to an observation in your test suite? |
Yes I was getting many timeouts, but I hadn’t tracked down the source of the errors. To mitigate the problem, I extended the timeout. Let me investigate. This logic will also be replaced after #203 is merged since it uses OpenAI v1.0. |
I have run into the same question but still don't know why |
openai.error.Timeout: Request timed out: HTTPSConnectionPool(host='api.openai.com', port=443): Read timed out. (read timeout=60) |
I too am seeing this error, openai.error.Timeout: Request timed out: HTTPSConnectionPool(host='api.openai.com', port=5001): Read timed out. (read timeout=60). However, I am using autogen with LM Studio I did try and increase timeouts to see if that will help, but not sure I am addressing the root cause. llm_config = { |
In v0.2 these settings changed: https://microsoft.github.io/autogen/docs/Installation#python |
We are closing this issue due to inactivity; please reopen if the problem persists. |
I've got the following config setup:
However, I'm noticing that when there's a read timeout, there's no retry happening:
Exception: Timeout: Request timed out: HTTPSConnectionPool(host='blah123.openai.azure.com', port=443): Read timed out. (read timeout=30)
I'm unsure if the timeout handling in
oai/completion.py
is correct:In this case, it's not a rate limit exception, but just a Timeout exception. Why is there a check for
...and "request_timeout" not in config
? This seems to be skipping the retry for non-RateLimit timeouts.Can that check be removed, and within the
except
logic,?
The text was updated successfully, but these errors were encountered: