Repository navigation
fix(server): editors appear once a slow discovery scan finishes #13917
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
Yash-Singh1
merged 3 commits into
pingdotgg:main
from
bfowler:t3code/editor-discovery-recovery
Oct 3, 2026
+359
−59
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
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.
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.
🟡 Medium
process/externalLauncher.ts:808A discovery scan that never completes permanently blocks
resolveAvailableEditors(): every later caller reuses the same unfinishedDeferredand no replacement scan can start until restart. This happens because the pending entry storesexpiresAtNanos: undefinedand is cleared only by the scan'sonExit; give pending scans a finite expiry so callers can start a replacement after the cache TTL.🤖 Copy this AI Prompt to have your agent fix this:
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.
Not changing this. A scan that never settles can't block anything unboundedly: its only callers are
server.getConfig/the config snapshot, which still bound it with the 5 sresolveAvailableEditorsForConfigtimeout and degrade to no editors (the pre-PR behavior), and the late-snapshot wait, which ends with its subscription.The suggested expiry would make things worse in the one case where a scan really hangs: a stat stuck on a dead network mount or PATH entry. A replacement scan every 60 s would hit the same entry and hang too, and each stuck
fs.statholds a libuv threadpool thread (4 by default), so piling up scans would starve every other filesystem call on the server. Keeping at most one scan in flight is deliberate. It also races with in-flight scans that take longer than the TTL, starting duplicates on a slow host, which is the situation this PR is about.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.
Sorry, I'm unable to act on this request because you do not have permissions within this repository.