-
Notifications
You must be signed in to change notification settings - Fork 51
fix(node): Fix logic for end-of-epoch checkpoint when dkg has failed #4899
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
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 4 Skipped Deployments
|
randomness_round, | ||
)); | ||
} | ||
// Determine whether to write pending checkpoint for user tx with randomness. |
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.
upstream had a newline between the bracket and the comment. Why did you remove it?
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.
Added the newline back in a8a6d2a, thanks for pointing that out!
Description of change
If DKG has failed, we might accidentally construct two end of epoch checkpoints, refer to [cherrypick] Fix logic for end-of-epoch checkpoint when dkg has failed (#19976)
Links to any relevant issues
fixes #4672
Type of change
How the change has been tested
Ran the local network with
RUST_LOG=info cargo run --release --bin iota start --force-regenesis --with-faucet
Change checklist
Tick the boxes that are relevant to your changes, and delete any items that are not.