Repository navigation
fix(trie): tighten iterator seek boundary (v2.5.2 backport) - #39
Merged
danyalprout merged 1 commit intoNov 5, 2026
Merged
Conversation
(cherry picked from commit 8572c88)
BrianBland
approved these changes
Nov 5, 2026
wlawt
approved these changes
Nov 5, 2026
This was referenced Nov 5, 2026
danyalprout
added a commit
to base/base
that referenced
this pull request
Nov 5, 2026
Carries base/reth#39, the trie node iterator seek-boundary fix, on the releases/v1.5.3 line. Generated with Claude Code Co-authored-by: Claude <noreply@anthropic.com>
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
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.
Why
Backports the upstream trie node iterator seek-boundary fix onto
backport/v2.5.2/mainfor the Basereleases/v1.5.3line.When the iterator seeks to a hashed key at a cached branch boundary, it decides whether it can skip the seek by checking the walker's current key. The old check accepted any walker key that merely started with the seek prefix. If the stored branch sits deeper than the seek prefix, hashed entries between the prefix and that branch were never visited, so an inserted leaf in that gap was left out of the incremental root.
What
Cherry-picked with
-xprovenance:fix(trie): tighten iterator seek boundary.The skip now requires the walker key to equal the seek prefix exactly. The production change applied cleanly. The only conflict was a
U256import in the test module, resolved by taking the upstream import list. The upstream incremental-root test is carried along unchanged.Testing
cargo test -p reth-trie --lib node_iter: 2 passed.cargo clippy -p reth-trie --lib --tests -- -D warnings: clean.Notes
Not tagged yet; after merge the next tag in the series is
base-v2.5.2.11.