-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
Handle IncompleteRead error in Stream #237
Comments
This should handle both cases of incomplete read catched by requests, or catched by tweepy. This resolves tweepy#237, resolves tweepy#448, resolves tweepy#536, resolves tweepy#650, resolves tweepy#691, resolves tweepy#798. Similar to tweepy#498.
This seems to have been fixed with fae9091 (#498), but was reverted with 34af675, due to #501. For discussion on the cause of this issue and how to handle it, see #448 and these Stack Overflow posts: The error seems to be indicative of a full buffer disconnect. For reference: |
The retry logic does not always work, because the try/except block does not catch all possible errors (sometimes resp.read() can throw IncompleteRead errors, in which case the request is not retried).
The text was updated successfully, but these errors were encountered: