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

More information provided when errors raised #256

Closed
rightaway opened this issue Jan 23, 2015 · 5 comments
Closed

More information provided when errors raised #256

rightaway opened this issue Jan 23, 2015 · 5 comments
Labels

Comments

@rightaway
Copy link

I'm getting several ClientResponseErrors but there is no additional information in the error object to hint at why it might have failed. Would be helpful if errors include more detail and documentation includes descriptions of when various errors are raised.

@asvetlov
Copy link
Member

ClientResponseErrors is raised on server side when client disconnects without proper shutdown procedure.
In general those errors are fine, with slight performance degradation comparing to well-formed client side shutdown.

@fafhrd91
Copy link
Member

@asvetlov thats different exception, ClientResponseError is raised by http client, but we use raise from exc form so original exception should be visible.

@asvetlov
Copy link
Member

Oops, sorry. @fafhrd91, you are right.

@fafhrd91
Copy link
Member

closing. ClientResponseError has exceptions chain.

@lock
Copy link

lock bot commented Oct 29, 2019

This thread has been automatically locked since there has not been
any recent activity after it was closed. Please open a new issue for
related bugs.

If you feel like there's important points made in this discussion,
please include those exceprts into that new issue.

@lock lock bot added the outdated label Oct 29, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Oct 29, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants