rust-analyzer does not have a configuration

[dr-kernel]

When I start up the server, I get these errors sometimes (haven't found a consistent root cause), as time goes on it will eventually fail entirely with this error. Trying to "restart" the server fails with this error. If i restart the editor SOMETIMES it will work but then eventually fail.

 ...m/lsp/client.lua:623	"LSP[rust-analyzer]"	"Cannot find request with id 3715 whilst attempting to cancel"
.../lua/vim/lsp.lua:393	"rust-analyzer does not have a configuration"

rust-analyzer version: latest and currently trying 0.3.2291

rustc version: 1.86 and 1.83

editor or extension: VScode and Nvim (0.11)

relevant settings: VScode (default),
Nvim:

return {
    "mrcjkb/rustaceanvim",
    opts = {
        server = {
            settings = {
                ["rust-analyzer"] = {
                    cargo = {
                        extraEnv = { CARGO_TARGET_DIR = ".ra_target" },
                        features = "all",
                    },
                    check = {
                        features = "all",
                    },
                },
            },
        },
    },
}

code snippet to reproduce:
n/a

Posted on LSP prabirshrestha/vim-lsp#1599 too

[ChayimFriedman2]

These are not errors rust-analyzer emits, so it's likely a problem with your client.

[dr-kernel]

Which client? I reached out to Nvim LSP (the client?) they say its RA's fault...

[ethanuppal]

I reached out to rustaceanvim a while back and they also said it's RA's fault

[mrcjkb]

I reached out to rustaceanvim a while back and they also said it's RA's fault

@ethanuppal the discussion you opened in the rustaceanvim repo does not seem related to this.

@dr-kernel you are using the rustaceanvim client.
Please follow the troubleshooting guide and if you can reproduce it with the minimal config, file a bug report in the rustaceanvim repo.
If you are using a Neovim distro like AstroNvim or LazyVim, please ask there if you can't reproduce with plain Neovim and the minimal config.

[ethanuppal]

@mrcjkb yes, I neglected to mention it in that issue because I didn't think that was the root of the issue (I still can only say it is correlated). I also tried reverting to Neovim 10 and that didn't solve the issue. I think I might need to both revert to Neovim 10 and use an older version of rustaceanvim/rust-analyzer.

[mrcjkb]

Note that the Neovim log entry, rust-analyzer does not have a configuration, is not an error.
Neovim just logs that when a client queries vim.lsp.config['rust-analyzer'] and there exists no configuration specifically for rust-analyzer that was set via the vim.lsp.config API.

Cannot find request with id 3715 whilst attempting to cancel may be an issue with Neovim's built-in LSP client.

[druskus20]

Experiencing this as well, using rustaceannvim and nvim 0.11.3. Lots of Cannot find request with id <N> whilst attempting to cancel
Which made me look into this is that sometimes obsolete diagnostics appear to not be cleared

[rafaelsmgomes]

Same here! Facing the exact same issue.

[mrcjkb]

To rustaceanvim users:

Please follow the troubleshooting guide and if you can reproduce it with the minimal config, file a bug report in the rustaceanvim repo. If you are using a Neovim distro like AstroNvim or LazyVim, please ask there if you can't reproduce with plain Neovim and the minimal config.

Please don't open issues in rustaceanvim if you're not willing to bisect your plugins and config! I cannot do that for you.

rustaceanvim doesn't try to cancel LSP client requests (which is what is happening according to the log).
This is most likely either a Neovim bug or an issue caused by another Neovim plugin.