Spam of "server cancelled the request" from rust-analyzer

edevil commented 2 weeks ago

Have you read the docs and searched existing issues?

[X] I have read the README's troubleshooting guide and FAQ(https://github.com/mrcjkb/rustaceanvim?tab=readme-ov-file#left_speech_bubble-faq).
[X] I am using the latest rustaceanvim release.
[X] I have searched existing issues.
[X] I have searched existing discussions.
[X] I have searched the existing issues of other plugins related to this issue (if applicable).
[X] I have searched the existing rust-analyzer issues (if applicable).
[ ] I can reproduce the issue with stable Neovim (not a distribution or nightly) and the minimal config.
[X] This is an issue about rustaceanvim, not rust-analyzer or Neovim.
[X] This is not an issue with autocompletion.

Neovim version (nvim -v)

v0.10.2

Operating system/version

MacOS

Output of :checkhealth rustaceanvim

==============================================================================
rustaceanvim: require("rustaceanvim.health").check()

Checking for Lua dependencies ~
- OK [mfussenegger/nvim-dap](https://github.com/mfussenegger/nvim-dap) installed.

Checking external dependencies ~
- OK rust-analyzer: found rust-analyzer 0.0.0 (8eef1c527 2024-10-25)
- OK Cargo: found cargo 1.82.0 (8f40fc59f 2024-08-21)
- OK rustc: found rustc 1.82.0 (f6e511eec 2024-10-15)
- OK debug adapter: found codelldb 

Checking config ~
- OK No errors found in config.

Checking for conflicting plugins ~
- OK No conflicting plugins detected.

Checking for tree-sitter parser ~
- OK tree-sitter parser for Rust detected.
- OK .vscode/settings.json loaded without errors.

How to reproduce the issue

Ever since https://github.com/rust-lang/rust-analyzer/commit/8eef1c52757f1ca444792b22433e696364a2b86d I get spammed whenever I'm editing a Rust file.

Issues have been reported for neovim (https://github.com/neovim/neovim/issues/30985), RA (https://github.com/rust-lang/rust-analyzer/issues/18434), but it's hard for me to tell exactly where the problem lies, or if we should just ignore this message.

Please close this ticket if this is not an issue with rustaceanvim.

Expected behaviour

No messages.

Actual behaviour

The minimal config used to reproduce this issue.

Lazyvim with the latest rustaceanvim, and an RA version that includes the patch above.

mrcjkb commented 2 weeks ago

hey 👋

thanks for reporting.

Lazyvim with the latest rustaceanvim, and an RA version that includes the patch above.

LazyVim is not a minimal config (I have unchecked the respective checkbox). Please read the troubleshooting guide and ensure this is reproducible with a minimal config, with exact steps to reproduce (including creating a rust project or file). I'm afraid I don't have the capacity to follow up on issues that don't follow the steps outlined in the template.

This does sound like a rust-analyzer issue.

edevil commented 2 weeks ago

Yeah, it shouldn't be an issue with this plugin. Sorry for the noise. :)

mrcjkb / rustaceanvim