-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Conversation
@mvines since the leader schedule response returns epoch slot indices, I decided not to support cross-epoch responses. I don't think it's too awful for the client to handle when they are near an epoch boundary themselves. |
Yeah, ok. I foresee a small stream of epoch-boundary bugs due to this but I see how the current interface makes doing better troublesome |
246575e
to
335ce9d
Compare
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.
nice!
automerge label removed due to a CI failure |
Codecov Report
@@ Coverage Diff @@
## master #16057 +/- ##
=========================================
- Coverage 79.9% 79.9% -0.1%
=========================================
Files 409 409
Lines 107698 107774 +76
=========================================
+ Hits 86119 86162 +43
- Misses 21579 21612 +33 |
(adding v1.5 and v1.6, I don't want to wait for v1.7 to use this) |
(cherry picked from commit e7fd7d4) # Conflicts: # core/src/rpc.rs # core/src/validator.rs
(cherry picked from commit e7fd7d4)
(cherry picked from commit e7fd7d4)
(cherry picked from commit e7fd7d4)
(cherry picked from commit e7fd7d4)
Slipped my mind, thanks |
Problem
No way to get the upcoming leaders without fetching the entire leader schedule. It's also a pain for clients to get upcoming leaders across epoch boundaries.
Summary of Changes
getSlotLeaders
method which is similar togetSlotLeader
but fetches leaders for a given slot rangeFixes #16048