-
Notifications
You must be signed in to change notification settings - Fork 0
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
Error with epochEnd Block 450020: Closing the block failed with error Error(Engine(FailedSystemCall("Invalid data")) #3
Comments
Block reward calls started to happen again at block 450001. a new validator set took over at block ..10. with only 1 node being part of the validatorset (HBBFT3) |
watchdog output for the problematic block range:
why was there immediatly a new epoch switch with new pending validators ? |
announce availability:
|
early epoch end:
|
Unit Test or an End2End: What happens if there is an epoch, and during the epoch EVERY validator gets flagged as disconnected by the ConnectivityTracker, but the network did not stall at all, and it did not trigger an Early epoch end. |
last write of availability information: was the same for all nodes, what is very unrealistic to happen. |
happened on alpha5 as well: happened on an epoch switch with "all keys written". here are the details:
|
forked the network with hardhat, and the function call just works fine:
|
have a clue, but i am also baffled how solidity handles return value on external calls. |
alpha5 after fixing the problem:
|
Could be connected to a faulty contract upgrade.
The text was updated successfully, but these errors were encountered: