-
-
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
Connection broken: IncompleteRead #650
Comments
This is happening to me as well, I updated to the last version which is 3.5.0... i think I'm getting this error everytime I lost connection with the server... I'm not 100% sure any help? |
Same here, even with Tweepy 3.5.0 |
Same problem here |
Same issue .Could someone help me solve it? |
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.
Same problem for me too. Using python3.4 with tweepy 3.5.0 . I tried to capture exception using:
Exception details:
|
I like this solution I will try it here is the link |
how did this work out for you? Looking but can't seem to get it to work myself |
Sorry for the false hope I said I will try it, not I did and it work. I am still working on it. If I have any updates I will tell you
kind Regards
From: Aaron Lum<mailto:notifications@github.com>
Sent: Thursday, May 4, 2017 9:11 AM
To: tweepy/tweepy<mailto:tweepy@noreply.github.com>
Cc: israa-alsarsour<mailto:a7la.is@hotmail.com>, Comment<mailto:comment@noreply.github.com>
how did this work out for you? Looking but can't seem to get it to work myself
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#650 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/APLyw2c95TTxPJdbx_-lV73RVEbrUE-wks5r2WwbgaJpZM4F6CYl>.
|
Is there any error handling solution for this? |
I have the same problem. Has anyone had any progress? |
Same problem here - anybody solved it? |
Is there any way to solve this problem? |
On simple method to handle/suppress the exception is to override the on_exception() function in tweepy streaming listener class.
|
would adding the above under on_data solve it? I'll try it and let you know if it works... |
i don't think adding in on_data works.. just overriding on_exception() as i have done for example is simple and works perfectly. |
Overriding on_exception() works but for me it seems that this exception is raised every 10 minutes, which is really annoying. Is it possible to solve it thoroughly? |
It seems like you are trying to process to much each tweet, and this takes to much time, so twitter disconnects you. Just leave the process of the data to another thread. |
for tweepy v 3.5, the quick and dirty fix is to go to this function in your stream.py: file def _run(self): you might also want to comment out the snooze function inside the exception, if you dont want any delay in your real time capturing. |
https://developer.twitter.com/en/docs/basics/rate-limiting.html There is a limit at 15 minutes, so you just have to reconnect after it times out. |
i tried with your solution but it keeps coming same error again and again. |
Duplicate of #237 |
One way to go around is to restart the stream in def on_exception(self, exception): . |
This happened and wasn't handled properly. Expected behaviour - reconnection
The text was updated successfully, but these errors were encountered: