-
Notifications
You must be signed in to change notification settings - Fork 487
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
Round Times: Period 0 deadline timeout #5850
Conversation
…o better reflect the variable's purpose. Fix deadline timeout references that either needed to provide period now or needed the default deadline timeout.
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #5850 +/- ##
==========================================
+ Coverage 55.88% 55.92% +0.04%
==========================================
Files 477 477
Lines 67259 67272 +13
==========================================
+ Hits 37586 37622 +36
+ Misses 27127 27109 -18
+ Partials 2546 2541 -5 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure any real harm will come from my concern.
Co-authored-by: John Jannotti <jannotti@gmail.com>
…te to for a possible version zero value.
…er.go, applying the resolved timeout to both issueSoftVote and nextVoteRanges.
Summary
This PR introduces a consensus parameter
AgreementDeadlineTimeoutPeriod0
, that as the name implies is used for setting a common period 0 deadline timeout. References to the deadline timeout in the codebase have been updated to reflect whether they need the existing default or to resolve a timeout based on a current period of consensus (and the active consensus version).Test Plan
Existing tests should all pass (several pass in period 0 or period 1 in agreement/service_test.go).