-
Notifications
You must be signed in to change notification settings - Fork 943
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
Suppress EPIPE and ECONNRESET tracebacks properly #377
Conversation
Rebased it to include PY3 changes. |
I can benefit from this very much. I built a streaming audio application, and each time the client picks another number, the connection is abruptly closed, resulting in broken pipe errors. |
#445 too |
👍 |
5 similar comments
👍 |
👍 |
👍 |
👍 |
+1 |
same problem for long polling after client (eg. browser) close, so +1 |
C'mon @gevent, what do you think? It's been a year. |
👍 |
1 similar comment
👍 |
👏✌️
|
🎉 Thanks for this! (It has been bugging me for years.) |
Happened to me on an SSE service with bottle. All is well now. ❤️ |
This should stop the logging that occurs when clients disconnect. gevent/gevent#377
This should stop the logging that occurs when clients disconnect. gevent/gevent#377
This should stop the logging that occurs when clients disconnect. gevent/gevent#377
The exception handler in
handle_one_response()
was catching and dumping socket errors before the handler inhandler_one_request()
ever got to see them and squash their tracebacks. So, I just moved the exception handler over tohandle_one_response
.Fixes #136.