You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Even though we have addressed the missed proposal in issue #1438, there is a situation where the query-proposal may still get no response.
The scenario is as follows in time order:
Validator B is the proposer and becomes faulty after proposing the block.
Validator P decides on No in Change-Propose phase without having the proposal and queries the proposer from Validators X and Y. However, neither X nor Y has decided yet.
Validators X and Y then decide, but Validator P still has no proposal and cannot publish the PREPARE vote.
Using the random seed in the above test, you can reproduce the failed test again.
Workaround
This situation is very unlikely to happen in the mainnet, and even if it does, once the validator restarts its node, the proposal will be queried again, and the system will return to normal.
The text was updated successfully, but these errors were encountered:
b00f
changed the title
Consenssu quey-proposl message won't get response
Consensus query-proposal message won't get a response
Aug 3, 2024
Description
Even though we have addressed the missed proposal in issue #1438, there is a situation where the query-proposal may still get no response.
The scenario is as follows in time order:
No
in Change-Propose phase without having the proposal and queries the proposer from Validators X and Y. However, neither X nor Y has decided yet.This happened here: GitHub Actions Run.
How to Reproduce
Using the random seed in the above test, you can reproduce the failed test again.
Workaround
This situation is very unlikely to happen in the mainnet, and even if it does, once the validator restarts its node, the proposal will be queried again, and the system will return to normal.
The text was updated successfully, but these errors were encountered: