go/worker/storage: Handle state sync before runtime is operational #4311
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.
Previously there was an edge case that was not handled when the runtime was
registered in the consensus layer but not yet operational (e.g., there have been
no normal blocks yet). If a new node used state sync to quickly catch up with
the consensus layer and sync to a height after runtime's genesis, the node would
never register as it would keep waiting for storage checkpoints (which wouldn't
exist yet).
TODO