-
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 2.0] register failure points for new consensus for simtests #17275
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
3 Ignored Deployments
|
ddb8f9c
to
5f6e20e
Compare
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.
Everything else looks good, except I don't think commit timestamp enforces monotonicity at creation. Let me fix that in another PR first.
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.
Nice changes!
@@ -37,6 +37,8 @@ pub(crate) struct CommitObserver { | |||
sender: UnboundedSender<CommittedSubDag>, | |||
/// Persistent storage for blocks, commits and other consensus data. | |||
store: Arc<dyn Store>, | |||
/// The last committed sub dag | |||
last_sub_dag: Option<CommittedSubDag>, |
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.
nit: instead of keeping the entire last committed subdag in memory what if we just kept the commit index + timestamp?
3223d18
to
4e769a6
Compare
Description
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.