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.

Sign up for GitHub

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

Jump to bottom

TermSeconds changes should be effective after a TermClose event #1710

Closed
foriequal0 opened this issue Jul 22, 2019 · 0 comments · Fixed by #1715
Closed

TermSeconds changes should be effective after a TermClose event #1710

foriequal0 opened this issue Jul 22, 2019 · 0 comments · Fixed by #1715
Assignees
@foriequal0
Labels
consensus

Comments

@foriequal0
Copy link
Contributor

Currently, The effect of changes in term_seconds can kick in any time. This can leads to unexpected too short term change. We should wait until the current term is fully finished.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@foriequal0 foriequal0

Labels
consensus
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Apply termSeconds change after a term foriequal0/codechain
1 participant
@foriequal0