Repository navigation
fix(usage): yield between costly ledger rows #8455
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
lidge-jun
merged 8 commits into
lidge-jun:dev
from
atinseau:codex/fix-usage-ledger-yield
Nov 11, 2026
Merged
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
b786f38
fix(usage): yield between costly ledger rows
seedds e9d46cb
Merge origin/dev into usage ledger scheduling fix
seedds 3739479
Merge origin/dev for usage ledger review readiness
seedds f83e780
Merge current dev into usage scan responsiveness fix
seedds 0f45473
Merge current dev into usage scan responsiveness fix
seedds fcd6acb
Merge current dev into usage scan responsiveness fix
seedds e0249c7
Merge remote-tracking branch 'origin/dev' into pr-8455
lidge-jun 2349db4
fix(usage): yield inside a chunk on elapsed time only
lidge-jun 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
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
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
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
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.
On a contended worker, if the single-row checkpoint fixture crosses the 8 ms budget, this extra cancellation check moves its fourth
signal.abortedread before revision validation instead of after it. The getter intests/usage/usage-ledger-scanner.test.ts:472-477consequently rewrites the ledger at the wrong stage, and the checkpoint test rejects withcontent_changed, making the suite timing-dependent. With config-directory lookup isolated, the existing test fails under a controlled advancing clock on this commit and passes on its parent. Keep the cancellation check, but pin the clock in that fixture or replace its read-count trigger with an explicit post-validation seam.Useful? React with 👍 / 👎.