fix a corner case, reading a transition value which is spread across 2 chunks #90
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
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.
fix a bug in reading transition values during construction which can be spread across 2 chunks.
This issue found in the code has probably not much impact in practice, nevertheless worth to fix. If a transition value is stored between 2 chunks (1st part in chunk x, 2nd part in chunk x+1) the value wasn't read correctly. Note that chunking is only done at construction time, so lookup isn't affected. Reading the transition value is part of minimization, so worst case this bug prevented minimization of this particular state. I can not think this issue can cause data corruption.