-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Compiler panics on 1.52.0 after cargo run
and any file edit
#85003
Comments
This is a known issue - unfortunately, there isn't a fix for it at the moment. As a workaround, you can run |
We are seeing the same issue, note that I don't believe it has anything to do with rust-analyzer specifically, rather that the first build succeeds, then any edit which requires a new build will fail. Eg
|
@Jake-Shadle I can confirm this also happens with me. I will edit the |
cargo run
and any file edit
I was just coming here to report this. Here's one I saw in Nushell:
|
Thanks for filing the bug report! We just shipped a patch release to work around this issue and are currently triaging related issues related to ensure each underlying problem gets resolved. Since this appears to be a duplicate of #83538, I'm going to close in favor of that issue. |
Apologies as this is the most minimal example I've been able to produce; working on finding a better one that doesn't use the
kube-rs
crate.Steps to reproduce:
The second
cargo run
will give ICE.Code
Meta
rustc --version --verbose
:Error output
Backtrace
EDIT1: Thanks @Jake-Shadle for pointing out the issue is unrelated to
rust-analyzer
; any file change after the firstcargo run
will cause the issue.The text was updated successfully, but these errors were encountered: