-
Notifications
You must be signed in to change notification settings - Fork 69
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
IF: Fixes for IF to advance LIB #2105
Conversation
…n needed digests in block_state. Do not send out vote until after block is processed.
return my->block_data.aggregate_vote(vote); | ||
auto [valid, new_lib] = my->block_data.aggregate_vote(vote); | ||
if (new_lib) { | ||
my->if_irreversible_block_num = *new_lib; |
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.
Do we need to call log_irreversible
here?
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.
We db.commit()
in log_irreversible
, so don't want that called from net thread.
Trying some code cleanups
Note:start |
New integration test that verifies that LIB advances on all nodes under instant-finality.
Fixes for instant-finality:
net_plugin
strong
serialization in vote message.fork_database
block_state
implementation to usecore.last_final_block_num
forirreversible_blocknum()
Reviewers: Pay close attention to validation logic for
qc_info
. Not sure this is the best way to handle block validation withqc_info
.Works:
./tests/nodeos_lib_test.py -n 4 -p 3 -s mesh --activate-if --keep-logs -v
Works:
./tests/nodeos_lib_test.py -n 4 -p 3 -s ring --activate-if --keep-logs -v
Resolves #2100