-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Critical bug that completely prevents the use of rust-analyzer (1.78.0-nightly (3246e79 2024-02-19) in VS Code (1.86.2) #16622
Comments
Is this a thing for all projects you've tested? Are any particular steps needed to reproduce? btw r/suddenlycaralho |
I am working on just one project in Rust. Do you recommend any specific open source project to test? |
I'm getting this in the tree-sitter repository, when invoking goto definition in this file at this line, with the following error message:
The text that is mentioned in the error can be located here hope this helps a bit r-a version:
full error log
|
Just open VS Code. The rust-analyzer is able to make like a "first analysis". So, if I keep closing / opening / closing it is possible to detect some errors / warnings in the project. But few seconds later it starts to panic and the rust-analyzer doesn't work at all. |
Wasn't able to reproduce it on today's and yesterday's nightly r-a on tree-sitter |
What debugging strategies do you suggest for resolving this issue? It's significantly hindering my daily tasks. |
dang, I just reproduced it with today's nightly as well. I use neovim not vscode though fwiw, but that shouldn't really affect how r-a behaves. like @felipelalli said ^^ I'm happy to help debug further, just need pointers |
I have downgraded my version from I'm using this Rust toolchains and rust-analyzer nightly for Nix and there are 3 main branches:
I just have switched from For NixOS users: Instead of using:
you should use:
|
Might be https://docs.rs/indoc/latest/indoc/ causing troubles again given the linked source snippet |
Same here, but I use rust-analyzer on Nvim with Mason. I resolved by downgrading rust-analyzer to the 2024-02-11 version. |
Also experiencing this: [Error - 9:47:02 AM] Request textDocument/hover failed.
Message: request handler panicked: Fail to convert given literal Literal {
text: "\"\"PortableRegistry\"\"",
span: SpanData {
range: 391..392,
anchor: SpanAnchor(
FileId(
9334,
),
0,
),
ctx: SyntaxContextId(
20340,
),
},
} I'm not able to fix the issue by downgrading rust-analyzer. |
I don't think it should be open until a new release if it is fixed, however, I too can still reproduce my issue with I can paste my backtrace log on request |
The bug exists in the proc-macro server (a rustup component) so you'll have to update your rust toolchain to tomorrows nightly (as the sync only happened today). Hence why downgrading didn't help either for you |
Works great @Veykril, thanks so much for your work on this issue :) |
Thank you so much @Veykril, just updated and it works great now |
This is a serious regression in nightly and it's important to fix it before the next release.
rust-analizer extension: v0.4.1853 (pre-release)
rust-analyzer: 1.78.0-nightly (3246e79 2024-02-19)
rustup: 1.26.0 (1980-01-01)
rustc: 1.78.0-nightly (3246e7951 2024-02-19)
VS Code: 1.86.2
rust-analyzer analysis-stats .
the output is: https://pastebin.com/YRNzDaXV
RA_LOG=info rust-analyzer analysis-stats .
the output is so big that I had to upload it to Mega.nz:
https://mega.nz/file/IsIATYSR#LQMQZy5FR0JrXpB27J6dI8igABvMioHzaaiaExbfvfI
the Output inside VS Code is:
Please don't hesitate to contact me if you require any additional information or if there's any way I can assist you further.
The text was updated successfully, but these errors were encountered: