Create TrieDBBrokenIterator replicating version <0.16 iterator bug. #42
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
Merged
|
Instead, a Kusama CC3 was released, so backwards compatibility is not required. |
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.
In versions <0.16.0 of trie-db, a bug in
TrieDBIteratorwould causeseekto position the cursor incorrectly in some cases. In particular, the cursor would be positioned at the beginning of a branch or extension node even if the key parameter follows it. This bug has become part of the consensus logic on certain deployed blockchains including Kusama.This is part of the solution for fixing the storage root mismatch bug on Kusama.