-
Notifications
You must be signed in to change notification settings - Fork 26
feat(node): skip checkpoint sync when recent state data is in the db #403
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
Merged
MegaRedHand
merged 5 commits into
lambdaclass:main
from
conache:skip-checkpoint-sync-when-state-in-db
Jun 2, 2026
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
d4e1674
Resume from db state data if data is recent enough
conache 0221790
Add tests
conache 4bc539b
Probe latest finalized
conache 6886535
Merge branch 'main' into skip-checkpoint-sync-when-state-in-db
conache cfc5cb6
Merge branch 'main' into skip-checkpoint-sync-when-state-in-db
pablodeymo File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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
This file contains hidden or 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
from_db_stateonly validatesKEY_CONFIGbefore returning aStoreThe function checks that
KEY_CONFIGis present and thatgenesis_timematches, then constructs and returns aStore. Immediately in the caller (main.rs),store.latest_finalized().slotis invoked, which callsget_metadata(KEY_LATEST_FINALIZED). That helper unconditionally panics with"metadata key exists"if the key is absent. If the DB ever hasKEY_CONFIGbut is missingKEY_LATEST_FINALIZED(e.g. a schema change between node versions, a partially-migrated DB, or a crash between two separate write batches in future refactors), the node will panic at startup instead of falling through cleanly to checkpoint sync. Consider probingKEY_LATEST_FINALIZEDinsidefrom_db_stateand returningNonewhen it is absent, consistent with the function's existing "empty or inconsistent →None" contract.Prompt To Fix With AI
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added probe in 4bc539b