Retry requests even when there is no connectivity #1563
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
BitmapHunter was intended to eventually retry using NetworkPolicy.OFFLINE if there were enough failed retries. However, the code was (at some point) changed so that it would not retry if you had no connectivity. These two behaviors were at odds, so I changed it back to depending solely on BitmapHunter.shouldRetry().
f6de765
to
7b7c750
Compare
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.
BitmapHunter was intended to eventually retry using NetworkPolicy.OFFLINE
if there were enough failed retries. However, the code was (at
some point) changed so that it would not retry if you had no connectivity.
These two behaviors were at odds, so I changed it back to depending
solely on BitmapHunter.shouldRetry().