fix: debug lsp diagnostics cmd for certain lsps#5420
Merged
rekram1-node merged 1 commit intoDec 12, 2025
Conversation
… received config and indexed the file
rekram1-node
changed the title
rekram1-node
pushed a commit
that referenced
this pull request
Dec 27, 2025
xywsxp
pushed a commit
to xywsxp/opencode
that referenced
this pull request
Apr 24, 2026
Rwanbt
pushed a commit
to Rwanbt/opencode
that referenced
this pull request
May 5, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Some LSPs (e.g., https://github.com/cucumber/language-server) require configuration from the client and re-indexing of the files after the initial handshake has been established before they can produce relevant diagnostics. This results in invalid diagnostics returned for about a fraction of a second after the handshake has been initialized. After the code has been re-indexed the server sends another (correct) diagnostics response, so this is not a problem for a code editor or the coding agent.
The debug LSP command sends a diagnostic request right after the handshake has been initialized and will exit after the first response (which in this case will not be correct because of lacking configuration). The simple fix is to add a short timeout after the server has been initialized so that it has had time to receive configuration and do any required re-indexing.