This repository has been archived by the owner on Feb 6, 2025. It is now read-only.
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
fix: bsc panic in fullnode mode
Rationale
In the original implementation, a forkchoice event was emitted to the sync engine for every update from latest_head to local_finality_head.
However, the local_finality_head in the parlia engine task is read by a separate coroutine (the parlia snapshot reader) and then re-emitted via an fcu event. If this coroutine lags, it can lead to duplicate forkchoice events, which in turn causes repeated import of the same block.
This ultimately results in attempting to import blocks onto a state that has already been pruned (in fullnode mode), causing an abnormal exit.
Example
n/a
Changes
Notable changes:
Potential Impacts