Fix: Block stream ignoring configured endBlock in specific cases#6474
Merged
dimitrovmaksim merged 2 commits intographprotocol:masterfrom Apr 1, 2026
Merged
Conversation
e458193 to
eda46fd
Compare
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.
Fixes two issues that caused subgraphs to scan blocks well beyond their configured endBlock.
max_end_blockcheck when block has no triggers, which causes the block stream to scan for blocks beyond the max end block until another condition is met.max_end_blockis set toNonewhen multiple data sources share the sameendBlock.max_end_blockwas computed by comparingdata_sources.len()withend_blocks.len(), butend_blocksis aBTreeSet, which removes duplicated values, resulting indata_sourcesandend_blockslegths to not be equal in this case.