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

Handle none-responses from open_url #809

Merged
merged 1 commit into from
Aug 31, 2020

Conversation

dagwieers
Copy link
Collaborator

@dagwieers dagwieers commented Aug 31, 2020

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

@dagwieers dagwieers added the bug Something isn't working label Aug 31, 2020
@dagwieers dagwieers added this to the v2.4.1 milestone Aug 31, 2020
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
Copy link
Collaborator Author

So I will merge this. My concern is that open_url() may return None without raising an issue. But as far as I can see this should never happen, so I am fine with this, even if it is not very elegant, I don't see a better solution to exit a calling function prematurely on network issues.

@dagwieers dagwieers merged commit 4e17423 into add-ons:master Aug 31, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants