Exception when using bloop v1.5.4. Is this a bug in metals, nvim-metals, bloop, or my configuration?

[trmckay]

I am trying to use nvim-metals with bloop v1.5.4, however I keep encountering the following error when viewing the logs with :MetalsToggleLogs:

2022.12.14 16:33:26 INFO  time: Connected to build server in 0.16s
2022.12.14 16:33:26 INFO  Connected to Build server: Bloop v1.5.4
2022.12.14 16:33:26 INFO  Scala targets not supported by serverorg.eclipse.lsp4j.jsonrpc.MessageIssueException: Message could not be parsed.
        at org.eclipse.lsp4j.jsonrpc.RemoteEndpoint.handleResponseIssues(RemoteEndpoint.java:358)
        at org.eclipse.lsp4j.jsonrpc.RemoteEndpoint.handle(RemoteEndpoint.java:317)
        at org.eclipse.lsp4j.jsonrpc.json.StreamMessageProducer.handleMessage(StreamMessageProducer.java:198)
        at org.eclipse.lsp4j.jsonrpc.json.StreamMessageProducer.listen(StreamMessageProducer.java:94)
        at org.eclipse.lsp4j.jsonrpc.json.ConcurrentMessageProcessor.run(ConcurrentMessageProcessor.java:113)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:750)

I found this issue for lsp4j, though it doesn't appear to be exactly the same. Does anyone have any idea where I can begin debugging this?

[ckipp01]

Huh odd. Just to check, could you try something for me. Can you try the latest Metals, which will bring in a newer Bloop version. You can do this by setting the following settings.serverVersion in your Metals config table that you pass into initialize_or_attach. You can just set this to latest.snapshot and it will automatically pull in the latest snapshot. Then after you install restart and do a :MetalsRestartBuild which should turn off the old Bloop server and start the new one. You should then see the new server version reflected in the metals doctor. Does this make any difference?

[trmckay]

Yes this worked! Thank you for the help!!

[trmckay]

For anyone else having issues, here was the config that worked for me.

local metals_config = vim.tbl_deep_extend("force", require("metals").bare_config(), {
    settings = {
        serverVersion = "latest.snapshot",
    },
    on_attach = function(client, bufnr)
        lsp_on_attach(client, bufnr)
        -- Metals keybindings
    end,
})

vim.api.nvim_create_autocmd("FileType", {
    pattern = { "scala" },
    callback = function()
        require("metals").initialize_or_attach(metals_config)
    end,
    group = vim.api.nvim_create_augroup("Metals", { clear = true }),
})