instagram: catch parse errors #1702
Merged
Conversation
This file contains 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
Exirel
added
Tweak
Bugfix
Sometimes Instagram doesn't expose its payload: probably some loading errors or something alike. Since we can't do anything about it - usually all you can do is retry later - the bot now say so (and log an exception). This fix sopel-irc#1667 Co-Authored-By: dgw <dgw@technobabbl.es>
Exirel
force-pushed
the
instagram-catch-errors
branch
from
65efa12
to
a1cb3d2
Compare
|
@dgw changes applied, string length fixed, all squashed for good measure. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Sometimes Instagram doesn't expose its payload: probably some loading errors or something alike. Since we can't do anything about it - usually all you can do is retry later - the bot now say so (and log an exception).
This fix #1667