-
Notifications
You must be signed in to change notification settings - Fork 33
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
Incorrect exit on non-started block #774
Comments
Fixed |
Looks it's still there:
|
Related to skalenetwork/skaled#1425 |
As of consensus 0ea0cae:
So, when consensus receives exitGracefully() call BEFORE proposing block 7, it should abort this proposal and exit (at block 6). |
skaled: 3.17.0-beta.1 |
Actual for skalenetwork/schain:3.17.0-beta.7 When consensus receives exitGracefully() call BEFORE proposing block 56693, it aborts this proposal and exit (at block 56693). But consensus proposed 56693 and skaled creating 56694 block, and only after this block, consensus going to terminating. |
Moving to 2.3 since it requires deep investigation and since it is not critical |
Moved to 2.4 as not critical for now |
Moving to 2.5 as we do not have time for it in 2.4 |
Actual:
Expected:
consensus should exit immediately, because new block was not proposed yet
The text was updated successfully, but these errors were encountered: