-
Notifications
You must be signed in to change notification settings - Fork 5.7k
Webhook Broken Pipe after connection reset, kills dispatcher #970
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
Labels
📋 pending-reply
work status: pending-reply
Comments
tsnoam
added a commit
that referenced
this issue
Jan 20, 2018
BaseServer.handle_error() default behaviour is to print to stdout or stderr (depends on the python version). In case that the file descriptor is closed an additional exception will be raised, resulting with the webhook thread to quit. Fixes #970
Patched and running, will let it run and see what happens. p.s. I used updater.idle(stop_signals=(2, 15, 6, 13)) to pick up broken pipe signals as a temp fix. |
@yusufk Thanks. Just make sure you've disabled the work around ;-) |
Howdy, Seems to have done the trick! Continued functioning despite multiple connection resets etc. Thanks |
tsnoam
added a commit
that referenced
this issue
Jan 25, 2018
BaseServer.handle_error() default behaviour is to print to stdout or stderr (depends on the python version). In case that the file descriptor is closed an additional exception will be raised, causing the webhook thread to quit. Fixes #970
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Uh oh!
There was an error while loading. Please reload this page.
Steps to reproduce
Standard Webhook with updater and dispatcher:
Expected behaviour
Bot should run and remain responsive
Actual behaviour
It runs, but after a few hours becomes unresponsive.
Configuration
Operating System:
Linux Cappucino 4.4.0-104-generic #127-Ubuntu SMP Mon Dec 11 12:16:50 UTC 2017 i686 athlon i686 GNU/Linux
Version of Python, python-telegram-bot & dependencies:
Logs
The text was updated successfully, but these errors were encountered: