Skip to content
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

jsonrpc internal error with no detail on the nature of the error #728

Open
tribbloid opened this issue Jan 6, 2025 · 4 comments
Open

jsonrpc internal error with no detail on the nature of the error #728

tribbloid opened this issue Jan 6, 2025 · 4 comments

Comments

@tribbloid
Copy link

Error while consuming 'textDocument/documentHighlight' with language server 'Scala Language Server (Metals)'

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$4(LanguageServerWrapper.java:315)
	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)

strangely, the stack doesn't contain any lsp4ij class, the only evidence is from the IDEA error reporting interface, so no idea how to refine it so far

@aboutZZ
Copy link

aboutZZ commented Jan 6, 2025

+1 same problem here.

  • First, LSP console did not print the full exception stack trace
Image
  • Second, I configured error reporting to the log file, but I did not see the error logs of the LSP plugin in the idea.log.
    Image
    Image

@angelozerr
Copy link
Contributor

angelozerr commented Jan 7, 2025

Internal error means that the error comes from the language server if I remember.

In Log means, showing error in the Log tab of the lsp console

@tribbloid
Copy link
Author

@angelozerr totally possible, in which case the client side should log as much info about requests/responses as possible.

IOException is obviously not relevant here

@angelozerr
Copy link
Contributor

I agree but I dont know how to reproduce your usecase and I am not sure if I can do something since this trace is managed by LSP4J (not LSP4IJ).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants