node: Validate copy offset against earliest_block_number#6384
Merged
dimitrovmaksim merged 1 commit intoFeb 19, 2026
Merged
Conversation
dimitrovmaksim
force-pushed
the
fix/copy-earliest-block-validation
branch
from
267a625 to
724799d
Compare
incrypto32
added a commit
that referenced
this pull request
Jun 9, 2026
Mirrors the guard added for `graphman copy` in #6384. Without this, grafting at a block below `base.earliest_block_number` silently produces a destination missing all pre-graft mutable entity versions, and (when the base has dynamic data sources) handlers fail with `unexpected null in handler` because `data_sources$` registrations survive pruning while the entities they reference do not.
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.
Resolves #6366