LSP client cleanup after transport/stdout loss
Cluster 82602 · agent/lsp. Data as of
Nothing open on GitHub. Fix merged in #94185 on 24 Aug 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #94185. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #94185. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a scenario where LSP clients become unresponsive after losing their transport connection, causing diagnostics requests to hang until timeout. The work involves detecting dead clients and retiring or replacing them so that pending diagnostics waits are aborted promptly.
Open issues0
Open PRs0
Fixes on record
-
#94185 fix(lsp): retire dead clients and abort diagnostics waits after transport death (#85125 3b)
files:
agent/lsp/client.py,tests/agent/lsp/_mock_lsp_server.py,tests/agent/lsp/test_client_e2e.py,tests/agent/lsp/test_service.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#82604 fix(lsp): replace dead language-server clients instead of timing out diagnostics · merged via another change →
#94185
Closed issues · 1
- Closed#82602[Bug]: LSP diagnostics repeatedly time out after the server loses stdout
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.67: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Subsystem
- agent/lsp
- Merged PRs
- #94185
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 24 Aug 2026