-
Notifications
You must be signed in to change notification settings - Fork 10
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
Replace active_finalizer_policy_digest with last_pending_finalizer_policy_digest #132
Conversation
…izer_policy_digest
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.
For the name, I would prefer not sure anymore newest_pending_...
to last_pending_...
as I find it less ambiguous.newest
is much better.
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.
Looks good to me. 👍
I've merged this PR into the branch I'm working on, tested it, and as far as I can tell, it produces the expected results.
@@ -135,6 +136,7 @@ namespace eosio::chain::snapshot_detail { | |||
, proposer_policies(bs.proposer_policies) | |||
, finalizer_policies(bs.finalizer_policies) | |||
, finalizer_policy_generation(bs.finalizer_policy_generation) | |||
, last_pending_finalizer_policy_digest(bs.last_pending_finalizer_policy_digest) |
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.
Should we add a comment on top of this function:
// When adding a member initialization here, also update block_state::block_state(snapshot_detail::snapshot_block_state_v7&& sbs)
.
Note:start |
Replace
active_finalizer_policy_digest
withlast_pending_finalizer_policy_digest
in finality digest computationResolves #128