-
Notifications
You must be signed in to change notification settings - Fork 529
Prefer close backfill points (absolute distance) #19748
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
Merged
MadLittleMods
merged 3 commits into
develop
from
madlittlemods/prefer-close-backfill-points
May 15, 2026
+16
−4
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| Prefer close backfill points (absolute distance). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -275,11 +275,22 @@ async def _maybe_backfill_inner( | |
| ) | ||
| ] | ||
|
|
||
| # we now have a list of potential places to backpaginate from. We prefer to | ||
| # start with the most recent (ie, max depth), so let's sort the list. | ||
| # we now have a list of potential places to backpaginate from. Figure out which | ||
| # ones we should prefer, so let's sort the list. | ||
| sorted_backfill_points: list[_BackfillPoint] = sorted( | ||
| backwards_extremities, | ||
| key=lambda e: -int(e.depth), | ||
| key=lambda e: ( | ||
| # Prefer backfill points that are closer to the `current_depth` | ||
| # (absolute distance) | ||
| abs(current_depth - e.depth), | ||
| # For the tie-break, we care about events that are actually in the past | ||
| # as they're more likely to reveal history that we can return (something | ||
| # absolutely in the past is better than something can potentially extend | ||
| # into the past). | ||
| # | ||
| # This sorts ascending so 0 sorts before 1 | ||
| 0 if current_depth >= e.depth else 1, | ||
| ), | ||
| ) | ||
|
|
||
| logger.debug( | ||
|
|
@@ -300,7 +311,7 @@ async def _maybe_backfill_inner( | |
| str(len(sorted_backfill_points)), | ||
| ) | ||
|
|
||
| # If we have no backfill points lower than the `current_depth` then either we | ||
| # If we have no backfill points lower than the `nearby_depth` then either we | ||
|
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Not exactly related to this PR but just a little correction since #19611 was merged. |
||
| # can a) bail or b) still attempt to backfill. We opt to try backfilling anyway | ||
| # just in case we do get relevant events. This is good for eventual consistency | ||
| # sake but we don't need to block the client for something that is just as | ||
|
|
||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
No tests but I sanity checked this sort with the snippet in the PR description