fix: Remove legacy offset bitmap length test #36
Merged
Conversation
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
astubbs
force-pushed
the
bug/bitset_too_long_exception
branch
from
2f54541 to
3094a71
Compare
astubbs
force-pushed
the
bug/bitset_too_long_exception
branch
2 times, most recently
from
9fa3f92 to
ee0e2b2
Compare
Was left over from old code, before WorkManager#maybeStripOffsetPayload was added
astubbs
force-pushed
the
bug/bitset_too_long_exception
branch
from
ee0e2b2 to
69b62a2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixes #35 RuntimeException when running with very high options in 0.2.0.0 (Bitset too long to encode) #35
Was left over from old code, before WorkManager#maybeStripOffsetPayload was added