-
Notifications
You must be signed in to change notification settings - Fork 3.7k
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 state merkle truncate #15800
Merged
Merged
Fix state merkle truncate #15800
Conversation
This file contains 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
in case of a partial commit on a unsharded state db, two things were wrong: 1. when we see a partial version, we need to look at the previous version before jumping the the epoch boundary (we forgot to substract 1 from the version) 2. the ledger meta db were not passed in as intended (instead, we passed the state merkle meta db) The test_db_restart smoke test does catch this sometimes but it's not easy to trigger. I bumpped the number of restarts on that test.
⏱️ 3h 1m total CI duration on this PR
🚨 1 job on the last run was significantly faster/slower than expected
|
areshand
approved these changes
Jan 23, 2025
grao1991
approved these changes
Jan 23, 2025
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
github-actions bot
pushed a commit
that referenced
this pull request
Jan 24, 2025
in case of a partial commit on a unsharded state db, two things were wrong: 1. when we see a partial version, we need to look at the previous version before jumping the the epoch boundary (we forgot to substract 1 from the version) 2. the ledger meta db were not passed in as intended (instead, we passed the state merkle meta db) The test_db_restart smoke test does catch this sometimes but it's not easy to trigger. I bumpped the number of restarts on that test. (cherry picked from commit f3d4dba)
github-actions bot
pushed a commit
that referenced
this pull request
Jan 24, 2025
in case of a partial commit on a unsharded state db, two things were wrong: 1. when we see a partial version, we need to look at the previous version before jumping the the epoch boundary (we forgot to substract 1 from the version) 2. the ledger meta db were not passed in as intended (instead, we passed the state merkle meta db) The test_db_restart smoke test does catch this sometimes but it's not easy to trigger. I bumpped the number of restarts on that test. (cherry picked from commit f3d4dba)
💔 Some backports could not be created
Manual backportTo create the backport manually run:
Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
github-actions bot
pushed a commit
that referenced
this pull request
Jan 24, 2025
in case of a partial commit on a unsharded state db, two things were wrong: 1. when we see a partial version, we need to look at the previous version before jumping the the epoch boundary (we forgot to substract 1 from the version) 2. the ledger meta db were not passed in as intended (instead, we passed the state merkle meta db) The test_db_restart smoke test does catch this sometimes but it's not easy to trigger. I bumpped the number of restarts on that test. (cherry picked from commit f3d4dba)
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation and see the Github Action logs for details |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
✅ Forge suite
|
✅ Forge suite
|
msmouse
added a commit
that referenced
this pull request
Jan 24, 2025
in case of a partial commit on a unsharded state db, two things were wrong: 1. when we see a partial version, we need to look at the previous version before jumping the the epoch boundary (we forgot to substract 1 from the version) 2. the ledger meta db were not passed in as intended (instead, we passed the state merkle meta db) The test_db_restart smoke test does catch this sometimes but it's not easy to trigger. I bumpped the number of restarts on that test. (cherry picked from commit f3d4dba) Co-authored-by: Alden Hu <[email protected]>
perryjrandall
pushed a commit
that referenced
this pull request
Jan 29, 2025
in case of a partial commit on a unsharded state db, two things were wrong: 1. when we see a partial version, we need to look at the previous version before jumping the the epoch boundary (we forgot to substract 1 from the version) 2. the ledger meta db were not passed in as intended (instead, we passed the state merkle meta db) The test_db_restart smoke test does catch this sometimes but it's not easy to trigger. I bumpped the number of restarts on that test. (cherry picked from commit f3d4dba)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
CICD:run-e2e-tests
when this label is present github actions will run all land-blocking e2e tests from the PR
v1.25
v1.26
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.
Description
in case of a partial commit on a unsharded state db, two things were wrong:
incomplete / faulty fix previously #15089
How Has This Been Tested?
The test_db_restart smoke test does catch this sometimes but it's not easy to trigger. I bumped the number of restarts on that test.
Key Areas to Review
Type of Change
Which Components or Systems Does This Change Impact?