Retry on both ConnectTimeout and ReadTimeout #1529
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Solves #1526 (cc @alexmojaki). Issue caused CI failures in huggingface/transformers#24384 (comment) (cc @ydshieh).
At the moment HTTP requests failing with a
ConnectTimeout
orProxyError
when downloading a file are retried with a backoff strategy. This PR addsReadTimeout
as an exception to retry on as well. More precisely, we now retry on anyrequests.exceptions.Timeout
error (meaning both connect and read timeouts).This change does not introduce a breaking change as
ConnectTimeout
errors are still caught. It should fix downloads in some rare occasions.