Fix skipped single-block scan in EventScanner - #201
Merged
Conversation
evgeny-stakewise
approved these changes
Sep 1, 2026
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
2 participants
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.
Description
EventProcessor.get_from_block()implementations return the first unscanned block (checkpoint + 1), sofrom_block == to_blockis a valid inclusive single-block range. The early-return guard inprocess_new_eventsused>=and skipped it, so the pending block was not scanned when the chain head advanced by exactly one block between iterations. Changed the guard to>so only a truly empty range (from_block > to_block) is skipped.