JsonSyntaxException on startup

[SrDum]

Full log follows: lsp.log

This is happening after a clean build (and trying to use it with nvim, using lspconfig). Worth noting that just running the server outside of nvim (while not spamming me with erros like nvim did), still gives teh first warning that seems to be the root cause, that being the line
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder"
Now, full disclosure, It's completely possible this is somehow an error on my part while building, but I have already retried multiple times following the readme.md to the letter.

Thanks in advance for any assistence.

[fwcd]

The SLF4J warning is fine (maybe not fine, but expected 😄).

A delegate object is null, jsonrpc methods of 'public default org.eclipse.lsp4j.services.NotebookDocumentService org.eclipse.lsp4j.services.LanguageServer.getNotebookDocumentService()' are ignored

This is interesting. We don't provide this method, but the client shouldn't call it either since we don't advertise it in the server capabilities.

Internal error: com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was BEGIN_ARRAY at path $

The JSON error confuses me. I'd wager a guess and say that it's generally some misconfiguration on the client-side.

[SrDum]

The SLF4J warning is fine (maybe not fine, but expected 😄).

A delegate object is null, jsonrpc methods of 'public default org.eclipse.lsp4j.services.NotebookDocumentService org.eclipse.lsp4j.services.LanguageServer.getNotebookDocumentService()' are ignored

This is interesting. We don't provide this method, but the client shouldn't call it either since we don't advertise it in the server capabilities.

Internal error: com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was BEGIN_ARRAY at path $

The JSON error confuses me. I'd wager a guess and say that it's generally some misconfiguration on the client-side.

I don't doubt it. How would I go about troubleshooting this?

[fwcd]

Consult with the docs/maintainers of the language client you're using or try another client and see if the issues persist.

[SrDum]

Consult with the docs/maintainers of the language client you're using or try another client and see if the issues persist.

Alright, thank you.

[xsh005]

@SrDum using the default config for init_options solves this for me, previously I was using init_options = {}

edit: linux machine + neovim 10 nightly

[fwy]

I had the same JSON-related error when first trying this language server with neovim on Windows, and after a little debugging found that setting the init_options.storagePath property to a valid directory fixed it.

init_options = {
    storagePath = util.path.join(vim.env.XDG_DATA_HOME, "nvim-data"),
},

'util' is require('lspconfig/util'), and the environment variable plus the 'nvim-data' segment references a location on my machine. After starting the language server in neovim, I can see that the file kls_database.db is created there and the fatal error is gone.

Using the default init_options by omitting this property from my lua configuration did not help.