Skip to content
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

Merged
merged 1 commit into from
Jun 25, 2015

Conversation

pshc
Copy link
Contributor

@pshc pshc commented Jan 24, 2014

The exception handler in handle_one_response() was catching and dumping socket errors before the handler in handler_one_request() ever got to see them and squash their tracebacks. So, I just moved the exception handler over to handle_one_response.

Fixes #136.

@pshc
Copy link
Contributor Author

pshc commented Feb 24, 2014

Rebased it to include PY3 changes.

@basilfx
Copy link

basilfx commented Apr 24, 2014

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.

@xsleonard
Copy link

#445 too

@tomislater
Copy link
Contributor

👍

5 similar comments
@ktarasz
Copy link

ktarasz commented Dec 17, 2014

👍

@bivald
Copy link

bivald commented Dec 17, 2014

👍

@kroman0
Copy link

kroman0 commented Dec 17, 2014

👍

@yankee7
Copy link

yankee7 commented Dec 23, 2014

👍

@myroslav
Copy link

+1

@jetz
Copy link

jetz commented Jan 27, 2015

same problem for long polling after client (eg. browser) close, so +1

@pshc
Copy link
Contributor Author

pshc commented Jan 28, 2015

C'mon @gevent, what do you think? It's been a year.

@jetz
Copy link

jetz commented Jan 29, 2015

@pshc I wonder if it's a problem to ignore all EPIPE, ECONNRESET errs at framework level? So I just patch the BaseServer in my project, like this

@trainiac
Copy link

trainiac commented Feb 9, 2015

👍

1 similar comment
@maxcountryman
Copy link

👍

@pshc
Copy link
Contributor Author

pshc commented Jun 25, 2015

👏✌️

On Jun 25, 2015, at 14:16, Jason Madden [email protected] wrote:

Merged #377.


Reply to this email directly or view it on GitHub.

@parasyte
Copy link
Contributor

🎉 Thanks for this! (It has been bugging me for years.)

@fxah
Copy link

fxah commented Jul 21, 2015

Happened to me on an SSE service with bottle. All is well now. ❤️

tilgovi added a commit to hypothesis/h that referenced this pull request Sep 17, 2015
This should stop the logging that occurs when clients disconnect.
gevent/gevent#377
tilgovi added a commit to hypothesis/h that referenced this pull request Sep 17, 2015
This should stop the logging that occurs when clients disconnect.
gevent/gevent#377
tilgovi added a commit to hypothesis/h that referenced this pull request Sep 18, 2015
This should stop the logging that occurs when clients disconnect.
gevent/gevent#377
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

pywsgi: shouldn't spew debugging data for normal network and timeout errors