Do not prematurely issue a response if still waiting on block validate response#6850
Conversation
…ion response Signed-off-by: Jacinta Ferrant <236437600+jacinta-stacks@users.noreply.github.com>
e2ccd0f to
eeda833
Compare
Codecov Report❌ Patch coverage is ❌ Your project status has failed because the head coverage (73.43%) is below the target coverage (80.00%). You can increase the head coverage or adjust the target coverage. Additional details and impacted files@@ Coverage Diff @@
## develop #6850 +/- ##
===========================================
- Coverage 74.44% 73.43% -1.02%
===========================================
Files 593 595 +2
Lines 358727 358946 +219
===========================================
- Hits 267065 263597 -3468
- Misses 91662 95349 +3687
... and 333 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
… into bugfix/wait-for-validation-before-issuing-signature
Signed-off-by: Jacinta Ferrant <236437600+jacinta-stacks@users.noreply.github.com>
1d0f97c
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
When investigating GSM:
Signer received block proposal S
Submitted S to node for validation
While validating, signer received >70% pre-commits over block S.
Signer immediately issued BlockAccept across S
Signer received block validate Ok, checked against local state: saw reorg of same block-> issued a BlockRejection
Signer should not prematurely issue the original Accept as the node could have responded with a BlockValidateReject.
Fixed and added a test.