-
Notifications
You must be signed in to change notification settings - Fork 2.2k
fix: disable state root task when no changesets #19869
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
Conversation
yongkangc
left a comment
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.
Changes makes sense to me
Why is it not safe to run without change sets? Or what might be the case that it doesn't work
16e4d47 to
3315a55
Compare
Because the DB might move between two db tx creations, in the case of a reorg this can lead to a situation where we can no longer get the correct trie state, for example the bugs that led to the creation of trie changesets in the first place |
3315a55 to
8e3e5ba
Compare
|
fixed clippy |
Co-authored-by: Alexey Shekhirin <[email protected]>
shekhirin
left a comment
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.
LGTM, @mediocregopher please take a look
|
closing, I think this is a bit of an edge case that we can continue to |
It's not safe to run the state root task or parallel state root anyways if there are not merkle changesets, so we disable it when we have no merkle changesets