Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
[Feature Request]: raise httpx exception instead of buildin ConnectionResetError and ConnectionError
See original GitHub issueThis is a feature requests instead of bug report.
I’m using requests in my web server to request upstream api. So I can handler all requests.RequestException in my middleware and return a 502 upstream error.
But after I migrated to httpx, httpx doesn’t have such exception when issuing a http(s) request, it will raise httpx.ConnectTimeout, buildin ConnectionError and ConnectResetError. And last 2 exception are not only raised by httpx.
Maybe httpx should also wrap ConnectionError and other buildin connection exception?
Issue Analytics
- State:
- Created 4 years ago
- Comments:20 (13 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Really we want to wrap as close to the exception as possible. Ie. Specifying what exceptions we expect from our backend
.read(),.write()and connection methods, and making sure we’re wrapping at that level.@florimondmanca thanks for your explanation