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

Rework all.rs to run all_forks and warp_sync syncing simultaneously #1591

Merged
merged 12 commits into from
Jan 20, 2024

Conversation

tomaka
Copy link
Contributor

@tomaka tomaka commented Jan 19, 2024

Close #1109
Close #1562

Previously, smoldot would always do a warp sync, then start syncing normally from the warp sync target.
What this PR does is always run the warp sync and normal syncing, and at the same time.

As described in the CHANGELOG, the consequence is that smoldot is able to perform a warp sync after it has been offline for a long time (or that the chain's finality has stalled for a long time) even if it has already warp synced before, and that it will no longer try to warp sync if peers are too close to the local best block.

This change opens the possibility for significant clean ups in all.rs. This module was a bit left rotten while waiting for this change.

@tomaka tomaka added this pull request to the merge queue Jan 20, 2024
Merged via the queue into smol-dot:main with commit 00899e3 Jan 20, 2024
22 checks passed
@tomaka tomaka deleted the all-forks-rewor branch January 20, 2024 10:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

GrandPa warp sync times out on github CI Warp syncing shouldn't be a one time process
1 participant