fix: expected hash in parent-chain linkage error #3628
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
rauljordan
approved these changes
Sep 19, 2025
|
Thanks for the PR! |
github-merge-queue
bot
removed this pull request from the merge queue due to no response for status checks
eljobe
approved these changes
Sep 23, 2025
auto-merge was automatically disabled
September 24, 2025 12:19
Pull Request is not mergeable
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Correct the error message to print the expected ParentChainBlockHash when verifying linkage against the incoming header’s ParentHash.
This field is the MEL head block hash we require to match the new header’s parent; printing ParentChainPreviousBlockHash was misleading and makes diagnosing reorgs and linkage issues harder.