fix(engine): attempt to advance persistence after it finished #13928
Conversation
This file contains 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
klkvr
requested review from
rkrasiuk,
mattsse,
Rjected and
fgimenez
as code owners
mattsse
approved these changes
Jan 22, 2025
rkrasiuk
approved these changes
Jan 22, 2025
rkrasiuk
reviewed
Jan 22, 2025
Comment on lines
1216
to
+1218
| } | ||
|
|
||
| if !self.persistence_state.in_progress() { |
There was a problem hiding this comment.
or early return, to remove indent
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.
Sometimes we are able to persist canonical chain right after on-disk reorged blocks were cleared. However, right now we are never trying to advance persistence after it have finished