Prevent mason-lspconfig from starting up a conflicting rust_analyzer LSP client

[OMGeeky]

With a basically default LazyVim config I get the following error with the :checkhealt rustaceanvim while having a rust file open.

- ERROR lspconfig.rust_analyzer has been setup. This will likely lead to conflicts with the rustaceanvim LSP client.

I have not setup anything to my knowledge that should setup rust_analyzer besides this and I can't figure out whats wrong...

Maybe you can take a look at my config here: OMGeeky/nvim-config-1

I am quite inexperienced with nvim so it might just be something stupid but I just can't figure it out. Thanks for any help you can provide.

[mrcjkb]

Hey 👋

I'm not familiar with the internals of LazyVim, and I can't see anything wrong in your config.

The health check searches for rust filetype autocommands created by lspconfig and reports the error if it finds one.

You could try opening a rust file and running :LspInfo. It should tell you if more than one client is attached.
If that's the case, then you can try explicitly disabling the rust_analyzer configuration in lspconfig with the following LazyVim snippet:

  {
    "neovim/nvim-lspconfig",
    opts = {
      setup = {
        rust_analyzer = function()
          return true 
        end,
      },
    },
  }

Or, more generally (for anyone not using LazyVim):

require("mason-lspconfig").setup_handlers {
  ["rust_analyzer"] = function() end,
}

[utensil]

It seems that none of the solutions work for me, after adding all these configs, tried some variants, e.g. the general one:

even after I manually run MasonUninstall rust-analyzer, I'll still be prompt that rust_analyzer installation in progress when opening a rust file,

then two instances come back:

Running the help gives me some errors:

But after a few enters I managed to read it. The solution inside is the same as this answer.

I have also tried a few times of a clean LunarVim installation.

[mrcjkb]

Perhaps you are setting up lspconfig.rust_analyzer somewhere else?
There's not much I can do to help here. You'll have to bisect your plugins and your config.

[utensil]

Thanks for your reply. My config is very short and nothing seems suspicious, it could be somewhere inside LunarVim, but I can't bisect it.

[mrcjkb]

I'm afraid I don't have the capacity to support all the Neovim distros out there.
It's best you ask in the LunarVim discussions.

[utensil]

Thanks, I just figured out why:

So my removing and reinstalling of LunarVim is not thorough, and :LvimCacheReset must be run for my config line

vim.list_extend(lvim.lsp.automatic_configuration.skipped_servers, { "rust_analyzer" })

to take effect.

Now only one rust analyzer is running (LSP progress updated by fidget.nvim, which showed two rust_analyzer running cargo check simultaneously before the fix):