-
Notifications
You must be signed in to change notification settings - Fork 832
Fix SubprocessRunner blocking cooperative thread pool, causing permanent refresh stall #566
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
steipete
merged 7 commits into
steipete:main
from
bryant24hao:fix/subprocess-cooperative-pool-starvation
Apr 8, 2026
+214
−24
Merged
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
b90380f
Fix SubprocessRunner blocking cooperative thread pool, causing perman…
bryant24hao eca08e4
Address Codex bot review: fix timeout race classification
bryant24hao 527f4eb
Replace wall-clock race guard with explicit KillFlag
bryant24hao 8666cb0
Fix SwiftFormat lint: expand KillFlag method bodies
bryant24hao 85b0ad3
Trigger CI re-run
bryant24hao 036ec7f
Merge branch 'main' into fix/subprocess-cooperative-pool-starvation
steipete f2eda48
test: shorten subprocess timeout fixtures
steipete 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
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.
After
waitUntilExit()was moved behindDispatchQueue.global()inSubprocessRunner.run, there is now an extra scheduling hop beforeexitCodeTaskcan finish. For commands that complete right around the deadline, this timeout task can wake first,terminateProcesswill no-op becauseprocess.isRunningis already false, and we still throw.timedOut. That turns successful near-threshold commands into false failures/fallbacks; the timeout branch should only throw if the process was still running or if it actually performed the kill.Useful? React with 👍 / 👎.