-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Bugfix: would_be_leader_shortly_fn period set to 1 slot instead of 20 #32468
Bugfix: would_be_leader_shortly_fn period set to 1 slot instead of 20 #32468
Conversation
@@ -53,8 +53,10 @@ impl DecisionMaker { | |||
}) | |||
}, | |||
|| { | |||
poh_recorder | |||
.would_be_leader(HOLD_TRANSACTIONS_SLOT_OFFSET * DEFAULT_TICKS_PER_SLOT) | |||
poh_recorder.would_be_leader( |
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.
this is would_be_leader_shortly_fn
.
Codecov Report
@@ Coverage Diff @@
## master #32468 +/- ##
=========================================
- Coverage 82.1% 82.1% -0.1%
=========================================
Files 778 778
Lines 210200 210200
=========================================
- Hits 172640 172592 -48
- Misses 37560 37608 +48 |
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.
The side effect of this bug is leaders stop forwarding if they receive transactions within 20 slots instead of 2?
Exactly. The pattern we use to have (and want) is:
the bug makes it so
|
Problem
#30618 did a bad copy pasta of constants.
Found this while investigating #32179 further, added some notes there on investigation.
#30618 was originally merged into v1.16. I reccommend we backport this.
My intent is to keep this fix PR simple so that it can be backported, and add tests to master in a follow-up PR.
Summary of Changes
revert constant for HOLD-only period from 20 slots to 1 slot.
Fixes #