fix: sync: atomically switch chains when checkpointing #11595
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.
Related Issues
F3
Proposed Changes
We can now atomically switch chains when checkpointing. Previously, we'd call
SetHead
followed bySetCheckpoint
. Unfortunately, that's not atomic and the "head" could have reverted before we calledSetCheckpoint
(causing the latter to fail).Now, we just call
SetCheckpoint
and letSetCheckpoint
adjust our head. This changes the behavior ofChainStore.SetCheckpoint
, butSyncer.SyncCheckpoint
is the only caller anyways.Checklist
Before you mark the PR ready for review, please make sure that:
<PR type>: <area>: <change being made>
fix: mempool: Introduce a cache for valid signatures
PR type
: fix, feat, build, chore, ci, docs, perf, refactor, revert, style, testarea
, e.g. api, chain, state, market, mempool, multisig, networking, paych, proving, sealing, wallet, deps