fix(opencode): increase LSP diagnostics timeout to 10s#13281
Open
Danztee wants to merge 1 commit intoanomalyco:devfrom
Open
fix(opencode): increase LSP diagnostics timeout to 10s#13281Danztee wants to merge 1 commit intoanomalyco:devfrom
Danztee wants to merge 1 commit intoanomalyco:devfrom
Conversation
Fixes anomalyco#13272. Increased diagnostics timeout from 3s to 10s to accommodate slow LSP servers like ESLint during initialization.
Contributor
|
The following comment was made by an LLM, it may be inaccurate: No duplicate PRs found |
Contributor
Author
|
please can you check this @rekram1-node @adamdotdevin |
This was referenced Feb 12, 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
1 participant
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.
What does this PR do?
Found out that the 3s timeout for LSP diagnostics is a bit too short for ESLint. It usually takes around 4-5s to spin up and send the first set of issues, so it was basically timing out and getting empty results for no reason. I bumped it to 10s which should be plenty.
How did you verify your code works?
I mocked a slow server that takes 4s to respond... worked fine with the 10s limit whereas the old code just gave up.
Fixes #13272