Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix storage sync from non-empty genesis and p2p multi call dispatch #5005

Merged
merged 4 commits into from
Oct 29, 2022

Conversation

kostko
Copy link
Member

@kostko kostko commented Oct 28, 2022

No description provided.

@kostko kostko added the c:bug Category: bug label Oct 28, 2022
If checkpoint sync is disabled but sync has been forced (e.g. because
the state at genesis is non-empty), we must request to sync the
checkpoint at genesis as otherwise we will jump to a later state which
may not be desired given that checkpoint sync has been explicitly
disabled via config.
Otherwise the shown state would be misleading, e.g. showing that it is
waiting for runtime host being provisioned while it is actually blocked
in initialization like storage sync.
@kostko kostko force-pushed the kostko/fix/rt-cp-sync-p2p-multicall branch from ca81c1c to 601be6d Compare October 28, 2022 19:26
@kostko kostko marked this pull request as ready for review October 28, 2022 19:27
@kostko kostko merged commit 978ea30 into master Oct 29, 2022
@kostko kostko deleted the kostko/fix/rt-cp-sync-p2p-multicall branch October 29, 2022 08:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c:bug Category: bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants