-
Notifications
You must be signed in to change notification settings - Fork 2k
Separate SSLError from HTTPError
#11564
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
Conversation
3615b67 to
704212e
Compare
6d8956c to
efbffe1
Compare
bf6dc8e to
cf862d6
Compare
jezdez
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This increases the number of our test runs drastically just for one test. Can you think of another way that would successfully monkeypatch this, so the tests are run in place and we don't have as much test matrix sprawl?
|
@jezdez I agree, I dislike that I had to implement the tests this way, but I don't see a simple alternative. Trying to properly mock the import as part of the regular unit test suite is not straightforward. The problem is that Edit: @travishathaway suggested mocking the |
Description
Previously
SSLErrorswere grouped withHTTPErrorsand hence became more difficult to diagnose since we'd receive a non-obvious HTTP 000 error. This defines a newCondaSSLErrorsand passes through theSSLErrorfor further diagnosis.See #11367 (not a complete solution as HTTP 000 is still possible).
Checklist - did you ...
newsdirectory (using the template) for the next release's release notes?Add / update outdated documentation?