Replies: 6 comments
-
|
These are not errors rust-analyzer emits, so it's likely a problem with your client. |
Beta Was this translation helpful? Give feedback.
-
|
Which client? I reached out to Nvim LSP (the client?) they say its RA's fault... |
Beta Was this translation helpful? Give feedback.
-
|
I reached out to rustaceanvim a while back and they also said it's RA's fault |
Beta Was this translation helpful? Give feedback.
-
@ethanuppal the discussion you opened in the rustaceanvim repo does not seem related to this. @dr-kernel you are using the rustaceanvim client. |
Beta Was this translation helpful? Give feedback.
-
|
@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. |
Beta Was this translation helpful? Give feedback.
-
|
Note that the Neovim log entry,
|
Beta Was this translation helpful? Give feedback.
-
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.
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:
code snippet to reproduce:
n/a
Posted on LSP prabirshrestha/vim-lsp#1599 too
Beta Was this translation helpful? Give feedback.
All reactions