fix: Prevent LanguageServers.forProject().anyMatching() from blocking #1179
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.
This PR addresses #894
LanguageServers.forProject(...).anyMatching()
may unexpectedly block for up to 10 seconds per matching language server.The issue occurs because
LanguageServers.forProject(...).anyMatching()
internally callsLanguageServiceAccessor.capabilitiesComply()
, which in turn invokesLanguageServerWrapper.getServerCapabilities()
. This method waits up to 10 seconds for the server to initialize, causing potential delays.This fix ensures non-blocking behavior by addressing the synchronous invocation chain.
The offending call chain is: