-
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
[5.0] Fix unlinked blocks caused by deferred trx removal #1734
Conversation
…eos_chainbase_allocation_test.py
I started another test from a January 2022 snapshot. I print out when a transaction's |
…_DEFERRED_TRXS_STAGE_2 is activated
…E_DEFERRED_TRXS_STAGE_1 instead of DISABLE_DEFERRED_TRXS_STAGE_2
…_deferred_trxs_stage_1 is activated
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.
It seems like we can now undo the modify_gto_for_canceldelay_test
hack if we wanted to since libtester allows for delayed transactions to be properly created prior to stage 1 activation.
But I am good with the changes in this PR as is.
Thanks. I will undo it on |
… update disable_deferred_trxs_stage_1_no_op_test
Resolved #1730.
Unlinked block error was encountered in a replay of mainnet. It was caused by blocking any deferred trxs by #1643.
This PR
I have run replay tests from the mainnet and have passed the failed block 320405089 and trx 527bbf9029f604e7021be729c858fb520001c5c5413cbee2fc08dbcf735534bc,
starting from snapshot-2023-07-12-16-eos-v6-0319983883. The previously failed block was at Jul-14-2023, 10:33:36 PM.
I will do more replay tests over the weekend.