-
Notifications
You must be signed in to change notification settings - Fork 24
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
Error while consuming 'textDocument/codeAction' with language server 'Tools for MicroProfile' #521
Comments
Do you know how to reproduce it? Have you a sample project? Could you enable the LSP console trace https://github.com/redhat-developer/lsp4ij/blob/main/docs/UserGuide.md#lsp-console and share the LSP trace when this error occurs. |
I attached the log file. |
Do you have the latest versions of LSP4IJ and Quarkus Tools? |
LSP4IJ 0.5.0 |
Thanks for the log. The error is very strange, it should send some request like Here a sample of error:
This error is very strange because it should send:
but it seems it crashes? Is there any chance that you share your project? |
No, sorry. I don't remember all of these issues with LSF4IJ 0.4.0 |
It is very hard for me to understand the problem since I cannot reproduce it -( |
If you can find another relelvant logs, please attach it. |
After investigating again your LSP trace, the error comes from the MicroProfile LS at https://github.com/eclipse/lsp4mp/blob/46bdf69f725349371c401066f85f2034a6fbec2f/microprofile.ls/org.eclipse.lsp4mp.ls/src/main/java/org/eclipse/lsp4mp/ls/java/JavaFileTextDocumentService.java#L225 It seems According your LSP traces you close several files and after that you reopen them. I wonder if you are using a menu contextual or another thing to reopen them in same time? |
I wasn't opening or closing documents at all. The very long log file I attached was produced in just a bunch of seconds. |
Before having your issue, you have closed serveral files and open theJava file which causes the problemand after that you were in a bad state. I don't know why. I need to understand how to reproduce this usecase. Can you reproduce everytime? |
No, I generally close IJ when I end working with it and restart the following day with the same open files. Yesterday I rerun IJ several times, and every time it was producing the errors. BTW, I haven't installed/upgraded anything at OS level |
@mfortunat could you please install:
and tell me if it is working better. Any feedback are welcome! |
Hi @angelozerr, Thanks for the info. Thank you anyway! |
Ok I understand but I wanted to have some feedback from you because we plan to do releases next week and LSP4IJ should be improved by starting l1nguage servers when all indexing from all projects are finished. It should (I hope and according my tests, there are a big improvement) fix performance problem and a lot of awfull errors. |
Hi @angelozerr, I'm very busy this week and the next due to Thanksgiving, Black Friday, and Cyber Monday. |
Error while consuming 'textDocument/codeAction' with language server 'Tools for MicroProfile'
org.eclipse.lsp4j.jsonrpc.ResponseErrorException: Internal error.
at org.eclipse.lsp4j.jsonrpc.RemoteEndpoint.handleResponse(RemoteEndpoint.java:209)
at org.eclipse.lsp4j.jsonrpc.RemoteEndpoint.consume(RemoteEndpoint.java:193)
at com.redhat.devtools.lsp4ij.LanguageServerWrapper.lambda$start$1(LanguageServerWrapper.java:260)
at java.base/java.util.concurrent.CompletableFuture$AsyncRun.run(CompletableFuture.java:1804)
at java.base/java.util.concurrent.CompletableFuture$AsyncRun.exec(CompletableFuture.java:1796)
at java.base/java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:507)
at java.base/java.util.concurrent.ForkJoinPool$WorkQueue.topLevelExec(ForkJoinPool.java:1491)
at java.base/java.util.concurrent.ForkJoinPool.scan(ForkJoinPool.java:2073)
at java.base/java.util.concurrent.ForkJoinPool.runWorker(ForkJoinPool.java:2035)
at java.base/java.util.concurrent.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:187)
IntelliJ IDEA 2024.2.1 (Ultimate Edition)
Build #IU-242.21829.142, built on August 28, 2024
Additional info:
It has already occurred 46 times in the last 2 or 3 days.
Very annoying
The text was updated successfully, but these errors were encountered: