LSP wait timeout not applied to baseline snapshot
Cluster 75551 · agent/lsp. Data as of
Nothing open on GitHub. Fix merged in #115719 on 19 Sep 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 #115719. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #115719. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where the configured lsp.wait_timeout value was ignored during the pre-write baseline snapshot, which instead used a hardcoded 5-second timeout. The cluster includes the bug report and related fix attempts.
Open issues0
Open PRs0
Fixes on record
-
#115719 fix(lsp): lsp.wait_timeout also bounds the pre-write baseline snapshot (#75551, salvage #75559)
files:
agent/lsp/manager.py,tests/agent/lsp/_mock_lsp_server.py,tests/agent/lsp/test_service.py,website/docs/user-guide/features/lsp.md
1 PR closed without merging
From the close comments: merged via another change 1
-
#75559 fix(lsp): honor lsp.wait_timeout in baseline snapshot · merged via another change →
0bd59ba,#115719
Closed issues · 1
- Closed#75551[Bug]: lsp.wait_timeout ignored on the pre-write baseline snapshot — edits pay a hardcoded 5s regardless of config
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
- #115719
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 19 Sep 2026