Skip to content
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

Recover TendermintState when empty the proposal timer is fired in a wrong time #1808

Merged
merged 3 commits into from
Oct 8, 2019

Conversation

majecty
Copy link
Contributor

@majecty majecty commented Oct 7, 2019

The Tendermint module was changing its step to 'Propose' when the "engine timeout empty proposal" timer is fired. If the timer is called in the wrong time, the step should not be changed. This commit makes the step change when it is needed.

@majecty majecty added bug Something isn't working consensus labels Oct 7, 2019
@ScarletBlue ScarletBlue changed the title Recover TendermintState when empty proposal timer is fired in a wrong time Recover TendermintState when empty the proposal timer is fired in a wrong time Oct 7, 2019
… time

The Tendermint module was changing its step to 'Propose' when the
"engine timeout empty proposal" timer is fired. If the timer is called
in the wrong time the step should not be changed. This commit makes
the step change when it is needed.
It is hard to know whether submit_proposal_block changes step or
not. Since submit_proposal_block has only two lines of code, it
doesn't remove code duplication. To clarify step transition, inline
the submit_proposal_block function.
@majecty majecty merged commit f3b58b4 into CodeChain-io:master Oct 8, 2019
@majecty majecty deleted the f/recover-state branch October 8, 2019 07:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working consensus
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants