LSP versionless diagnostics stale-tagging during didChange
Cluster 108881. Data as of
Nothing open on GitHub. Fix merged in #108894 on 12 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 #108894. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #108894. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These members address a bug where versionless LSP diagnostics could be incorrectly tagged as stale during a didChange send. A fix involves tagging such diagnostics with the version the didChange is advancing to.
Open issues0
Open PRs0
Fixes on record
-
#108894 LSP: nested single-root diagnostics found again; versionless pushes no longer tagged stale (#108882, #108881)
files:
agent/lsp/client.py,agent/lsp/manager.py,tests/agent/lsp/_mock_lsp_server.py,tests/agent/lsp/test_nested_root_current_diagnostics.py,tests/agent/lsp/test_versionless_push_during_send.py
1 PR closed without merging
From the close comments: done elsewhere 1
-
#108890 fix(lsp): tag versionless diagnostics with the version a didChange is advancing to · done elsewhere →
bed4abd,#108894,#108881
Closed issues · 1
- Closed#108881LSP: versionless diagnostics can be tagged stale during didChange send
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
- Merged PRs
- #108894
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 12 Sep 2026