Fix validation bug in --backfill-oldest-slot #16173
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
Inspector-Butters
previously approved these changes
Dec 19, 2025
james-prysm
previously approved these changes
Dec 19, 2025
kasey
dismissed stale reviews from james-prysm and Inspector-Butters
via
2d4dace
Inspector-Butters
approved these changes
Dec 19, 2025
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.
What type of PR is this?
Bug fix
What does this PR do? Why is it needed?
Validation of
--backfill-oldest-slotfails for values > 1056767, because the validation code is comparing the slot/32 toMIN_EPOCHS_FOR_BLOCK_REQUESTS(33024), instead of comparing it tocurrent_epoch - MIN_EPOCHS_FOR_BLOCK_REQUESTS.Which issues(s) does this PR fix?
Fixes #
Other notes for review
Acknowledgements