Don't set socket timeout if it's already disabled when streaming #1057
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.
Problem
When streaming responses, socket timeouts are set to
None
to avoid read timeouts. Normally this is fine, but causes issues when using gevent. When using gevent, the socket class will be patched to be non-blocking (ietimeout == 0.0
). If the timeout is set toNone
the socket becomes blocking again causing all greenlets to be blocked until the stream has finished.Solution
The proposed fix is to only set the socket timeout if it isn't already disabled.
Reproduction Steps
test.py
Without these changes:
With changes: