blockchain: fix flaw in block import #19986
Merged
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.
This PR fixes a problem which we've seen on the monitoring nodes
The testcase added in this PR triggers the same bug. For some reason,
blockchain
is given a chunk of blocks that are already canon and imported, but have been pruned already (more than 128 blocks back). Pruned but canon blocks make the sidechain import loopcontinue
early, and unless a non-canon block is found, the loop ends without settingexternTd
, leaving itnil
, which causes a seg violation later on.