-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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(root): drop sparse trie tx sender when state updates finished #14004
Conversation
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.
why is this necessary?
not obvious why we need to do this, I assume because there is some internal wiring that will only close the channel if this sender is dropped, but unclear why the loop here doesn't just break naturally
@mattsse we can't just break the loop, because we're still waiting on the reth/crates/engine/tree/src/tree/root.rs Lines 684 to 704 in fa29d98
reth/crates/engine/tree/src/tree/root.rs Line 759 in fa29d98
reth/crates/engine/tree/src/tree/root.rs Lines 524 to 529 in fa29d98
|
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.
ah okay, I get this now
lgtm
If
StateRootMessage::FinishedStateUpdates
is received after the lastStateRootMessage::ProofCalculated
is processed, we never drop thesparse_trie_tx
.To fix that, we need to do the same checks for dropping the sender in
StateRootMessage::FinishedStateUpdates
, as we do inStateRootMessage::ProofCalculated
.