fix(pruner): history indices cursor.prev() emptiness check#4301
Merged
fix(pruner): history indices cursor.prev() emptiness check#4301
cursor.prev() emptiness check#4301Conversation
cursor.prev() empty check
Codecov Report
... and 9 files with indirect coverage changes
Flags with carried forward coverage won't be shown. Click here to find out more.
|
cursor.prev() empty checkcursor.prev() emptiness check
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.
Problem
First row in
AccountHistoryandStorageHistorytables wasn't pruned, but instead the row after it was. The issue is in this snippet:reth/crates/prune/src/pruner.rs
Lines 690 to 709 in 34b68de
When we move a cursor to the previous row, it can be the first row of the table, so the cursor will not be actually moved and the
cursor.prev()will returnNone. We assumed that we always move it, so the next movement forward viacursor.next()was actually going forward too much.Solution
Check that previous row wasn't empty and we actually moved the cursor:
reth/crates/prune/src/pruner.rs
Lines 706 to 708 in 434d0a0
Also, save on a no-op
seek_exactif we were already at the last shard:reth/crates/prune/src/pruner.rs
Lines 724 to 727 in 4a5d8d2
The rest is just reformatting of the comments.