-
Notifications
You must be signed in to change notification settings - Fork 1.7k
[permission] finalizeChange is not called when maximumEmptySteps is set #11445
Comments
@zean00 Is this a recent problem? Do you see the same issue with 2.6.8 for example? |
Actually I have tested on 2.5.7 , 2.6.6, and 2.7.1 , same issue |
To clarify, does this really depend on I'm not familiar with all the relevant code, but |
It works fine when I remove Not sure related or not, Is it normal when ** Node 1 ** Node 2 Node 3 |
That's very weird… this line looks like setting
That's definitely not normal; it means the nodes went out of sync… either they're rejecting each other's blocks, or disagreeing on the fork choice. Do you see any " |
Yes, that's what I meant, setting to 0 or not specifying it resulting
Yes, I see block verification failed message, perhaps it's related to this issue ? Note that this log always appear same as
|
I agree, it's probably a duplicate of that issue. @dvdplm: I wonder whether the feature should be removed entirely? I don't know if anyone is using it in production. It's set in |
You mean removing the |
I mean removing empty steps altogether… 😬 |
Personally I wish the empty steps feature is still remain, as for private network, this is useful when the user count and transaction count is still low at very beginning to reduce block number. |
@zean00 yeah, I don't think it should be removed either. :) I started work on setting things up to repeat the problem locally but got side tracked, but then I thought I could just ask if you perhaps have a setup already you can share? A repo somewhere? |
You could use my setup |
* debug signer * Don't panic if empty_steps_transition already happened Before this the `header_empty_steps_raw` would panic if the chain has already progressed beyond the block number set in `emptyStepsTransition`. As this is a user accessible configuration option I don't think we should panic. * Cleanup some code in Aura Nothing really interesting here, renames or removes some methods. Adds some docs and extends a test a bit to clarify the behaviour of the code. * Include the seal when populating the header for a new block (fixes #11445) * cleanup * cleanup2 * Review grumbles * Update ethcore/engines/authority-round/src/lib.rs Co-Authored-By: André Silva <[email protected]> * Update ethcore/engines/authority-round/src/lib.rs Co-Authored-By: André Silva <[email protected]> * Update ethcore/src/block.rs Co-Authored-By: André Silva <[email protected]> Co-authored-by: André Silva <[email protected]>
Actual
2020-02-04 12:46:45 UTC IO Worker #3 INFO engine Signal for switch to contract-based validator set. 2020-02-04 12:46:45 UTC IO Worker #3 INFO engine Initial contract validators: [0x662eb278299d1f2069a52d09f308a599a99afd39, 0x59f6566306843fb7d18f782733e19223ca5f07ab, 0xade4279d444bb1183e733dcc1adffa06b53d72d2] 2020-02-04 12:46:45 UTC IO Worker #3 INFO import Imported #7 0x6d71…8993 (0 txs, 0.00 Mgas, 3 ms, 1.30 KiB) 2020-02-04 12:47:08 UTC IO Worker #1 INFO import 2/25 peers 19 KiB chain 28 KiB db 0 bytes queue 3 KiB sync RPC: 0 conn, 1 req/s, 112 µs 2020-02-04 12:47:38 UTC IO Worker #1 INFO import 2/25 peers 19 KiB chain 28 KiB db 0 bytes queue 3 KiB sync RPC: 0 conn, 5 req/s, 69 µs 2020-02-04 12:48:08 UTC IO Worker #3 INFO import 2/25 peers 19 KiB chain 28 KiB db 0 bytes queue 3 KiB sync RPC: 0 conn, 4 req/s, 108 µs 2020-02-04 12:48:38 UTC IO Worker #2 INFO import 2/25 peers 19 KiB chain 28 KiB db 0 bytes queue 3 KiB sync RPC: 0 conn, 4 req/s, 107 µs 2020-02-04 12:49:08 UTC IO Worker #2 INFO import 2/25 peers 19 KiB chain 28 KiB db 0 bytes queue 3 KiB sync RPC: 0 conn, 1 req/s, 145 µs 2020-02-04 12:49:30 UTC IO Worker #0 INFO import Imported #8 0xad09…1e07 (0 txs, 0.00 Mgas, 0 ms, 1.30 KiB)
Expected
2020-02-04 12:55:40 UTC Verifier #1 INFO engine Signal for switch to contract-based validator set. 2020-02-04 12:55:40 UTC Verifier #1 INFO engine Initial contract validators: [0x662eb278299d1f2069a52d09f308a599a99afd39, 0x59f6566306843fb7d18f782733e19223ca5f07ab, 0xade4279d444bb1183e733dcc1adffa06b53d72d2] 2020-02-04 12:55:40 UTC Verifier #1 INFO import Imported #7 0x2040…c1b6 (0 txs, 0.00 Mgas, 1 ms, 0.57 KiB) 2020-02-04 12:55:45 UTC IO Worker #0 INFO engine Applying validator set change signalled at block 7 2020-02-04 12:55:45 UTC IO Worker #0 INFO import Imported #8 0xa4a4…609b (0 txs, 0.00 Mgas, 6 ms, 0.57 KiB)
Step to Reproduce
If
maximumEmptySteps
parameter is removed, messageApplying validator set change signalled at block 7
will be appeared on log output.If I set
emptyStepsTransition
higher than block number of validator contract supposed to activate, thenfinalizeChange
is successfully called and messageApplying validator set change signalled at block 7
will be present. But once block number reachemptyStepsTransition
, any method that should triggerfinalizeChange
called (i.e.addValidator
) will not triggerfinalizeChange
properlyThe text was updated successfully, but these errors were encountered: