-
Notifications
You must be signed in to change notification settings - Fork 11.2k
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
[Consensus] Core to read last proposed round from DagState #20173
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
3 Skipped Deployments
|
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.
I guess we will need to rebase ancestor selection on this PR?
consensus/core/src/core.rs
Outdated
}); | ||
assert!(our_ancestor_included.is_some()); | ||
let our_ancestor_included = block | ||
.ancestors() |
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.
Blocks proposed by Core
should have the 1st ancestor as own ancestor.
Yes. If it's going to be a hassle @arun-koshy I can hold of until you merge, although the changes are quite small. |
Either way is fine with me! Feel free to merge and I can rebase as I am still waiting for approvals. |
Description
Refactoring Core to read the last proposed block from DagState rather than local cached value. This change:
Test plan
CI
Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.