-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Fix skipped slot detection for eager rent collect #10890
Fix skipped slot detection for eager rent collect #10890
Conversation
Codecov Report
@@ Coverage Diff @@
## master #10890 +/- ##
=======================================
Coverage 81.8% 81.9%
=======================================
Files 308 308
Lines 71447 71468 +21
=======================================
+ Hits 58513 58549 +36
+ Misses 12934 12919 -15 |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
vec![(14, 31, 32), (0, 0, 64)] | ||
); | ||
bank = Arc::new(new_from_parent(&bank)); | ||
assert_eq!(bank.rent_collection_partitions(), vec![(0, 1, 64)]); |
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 know this is rather untasteful hard coding magic numbers. But, I want to first fix the bug and deploy the updated logic to tds along with #10206.
@sakridge Oops, I intended to ask a review from you but it seems that I wrongly assigned this pr to you.... ;) |
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.
lgtm
(cherry picked from commit f1c1152)
Problem
Sorry, skipped slot detection was half-way for eager-rent collection... Found today with tds's epoch 61 -> epoch 62 transition:
Bad (curent behavior; missing last pubkey range for previous epoch):
Summary of Changes
Correctly detect it.... Also adjust gating a bit. I think tweaking gated logic is safe because it's still not scheduled.
Good (future behavior; adding last pubkey range for previous epoch):
follow-up to #10206.
CC: @t-nelson FYI: @mvines