Handle none-responses from open_url#809
Merged
dagwieers merged 1 commit intoadd-ons:masterfrom Aug 31, 2020
Merged
Conversation
dagwieers
force-pushed
the
none-response
branch
from
6426699 to
0c952b1
Compare
This handles all none-responses from open_url(). I am not sure this is the best way to handle this, it is not very elegant. Raising an exception helps in one case, but would not be elegant in the other cases either.
dagwieers
force-pushed
the
none-response
branch
from
0c952b1 to
79fc62f
Compare
Collaborator
Author
|
So I will merge this. My concern is that |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This handles all none-responses from open_url().
I am not sure this is the best way to handle this, it is not very
elegant. Raising an exception helps in one case, but would not be
elegant in the other cases either.
This relates to #807 and #385