-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Completion "hangs" with no response #743
Comments
Getting rid of infinite waiting in LSContentAssistProcessor Issue: eclipse-lsp4e#743
Using If user opens several completions, a Thread is taken again and again from the pool and after several completion, there is no Thread in the pool and language server becomes unusable not only with completion but with other features like highlighting, validation etc I suspect that this issue with strange error comes from this problem with Thread which are not available in the pool eclipse-wildwebdeveloper/wildwebdeveloper#1251 On my side when I edit a pom.xml file after some operations like completion, validation, I loose my all LSP features and I have strange error like eclipse-wildwebdeveloper/wildwebdeveloper#1251 and when I try to higlight a tag name, it doesn't work, so I suspect that there is no Thread in the pool available to process LSP operations. |
Fixes eclipse-lsp4e#743 Signed-off-by: azerr <azerr@redhat.com>
Fixes eclipse-lsp4e#743 Signed-off-by: azerr <azerr@redhat.com>
Getting rid of infinite waiting in LSContentAssistProcessor Issue: #743
Fixes eclipse-lsp4e#743 Signed-off-by: azerr <azerr@redhat.com>
Fixes eclipse-lsp4e#743 Signed-off-by: azerr <azerr@redhat.com>
In some cases Completion hardly "hangs" without a response from server logged, like:
For reference issue see: eclipse-lemminx/lemminx-maven#444
I believe LSP4E has problems in sending a request to the server, - a problem which I'd like to be investigated - so the response cannot be generated, but even if a LS is causing the problem, completion request is never finishes on LSP4E due to "infinite waiting on the completion future by calling
.get()
:https://github.com/eclipse/lsp4e/blob/55ce45f20dba1147cfa8383412f0105bfe96fc2e/org.eclipse.lsp4e/src/org/eclipse/lsp4e/operations/completion/LSContentAssistProcessor.java#L114C11-L114C11
While it's very difficult to catch the reason of sending request/receiving response failures, the using
CompletableFuture.get()
is to be strongly avoided.The text was updated successfully, but these errors were encountered: