Closed mTvare6 closed 1 year ago
Can you check if there's anything in the log files? I've never seen the "unknown system error -8" before.
Can you check if there's anything in the log files? I've never seen the "unknown system error -8" before.
Once the LSP server quits, on checking the lsp.log file, nothing new is added, so it looks like nothing new is being added. The lop system seems to work anyway, for example clangd gives output
Can you try deleting your data directory? See https://github.com/mfussenegger/nvim-jdtls#the-client-exits-with-an-error--eclipsejdtls-stopped-working
On running the in built command, it wouldn't run, although after manual deletion the error persists.
And on checking the logs by setting different debug types, the following was observed
[START][2022-11-13 18:01:45] LSP logging initiated
[INFO][2022-11-13 18:01:45] .../lua/vim/lsp.lua:1814 "exit_handler" {}
[START][2022-11-13 18:04:30] LSP logging initiated
[INFO][2022-11-13 18:04:30] .../vim/lsp/rpc.lua:661 "Starting RPC client" { args = {}, cmd = "java-lsp.sh", extra = {}}
Not sure what could cause this. In any case it has something to do with your installation, and with eclipse.jdt.ls, not really with this plugin.
Maybe you can try to re-install it, and either use the new jdtls
start script or write out the long cmd
as it is documented in the readme.
LSP client configuration
in init.lua:
in java-lsp.sh(according to commits before b07dd81):
Eclipse.jdt.ls version
1.2.0
Steps to Reproduce
When opening any java file through neovim, regardless of other conditions, it quits with the above given error. On running the command 'java-lsp.sh' outside neovim, opens the lsp normally.
Expected Result
Normal functioning of the language server, as when it is opened outside neovim. It is note-worthy that I haven't used nvim-jdtls since nvim 0.5.0 and opening it after a long while, gives the above result.
Actual Result