Repository navigation
fix(history): bound the integrity check wait (#7984) #7997
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
Merged
Changes from all commits
Commits
Show all changes
2 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
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.
Script executed:
Repository: lidge-jun/opencodex
Length of output: 9627
Script executed:
Repository: lidge-jun/opencodex
Length of output: 45635
Script executed:
Repository: lidge-jun/opencodex
Length of output: 13774
Bound retries by actual worker liveness.
After a timeout,
activebecomesnull, andinspect()ignores same-generation entries indraining. The 30-second cooldown can therefore start another check while the previous worker is still alive.RebuildWorkerJob.dispose()callsworker.terminate(), but waits only 5 seconds. The worker performs synchronousPRAGMA quick_check, and the implementation allows native I/O to outlive that disposal bound. Repeated scans that remain alive across cooldowns can therefore accumulate without a source-level capacity limit.Add a capacity limit for timed-out workers that have not actually exited. Return
unavailablewhile that capacity is full. Track actual worker exit rather than onlydraining, becauseafterExit()schedules its cleanup callback after an overrun but resolves its own promise before that callback runs. Document that the fresh-after-cooldown retry is subject to this capacity limit.