-
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
rust-analyzer crashing after switching to other crate in the same workspace #4451
Comments
Hm, I rebuilt last revision (88d3959) with
but no back trace for some reason:
|
I bisected. The problem introduced by: commit 1a2d4e2 (HEAD, refs/bisect/bad)
cc @lnicola The problem that after editing source that not belong to crate:
Have no idea how to move father, because of there is no backtrace ( |
There are limitations with handling files outside of the workspace and it's possible that 1a2d4e2 might have made things worse. As a workaround, you can set the Still, I don't think that scenario was well-supported even before my change. Do you have a sample project that exhibits the problem? |
Just encountered this. Could the immediate problem be solved by not panicking if this case occurs but simply doing nothing? |
Clone Dushistov/flapigen-rs@90f0404 cpp_tests/src/cpp_glue.rs.in I just tested 4cacedd . I tried |
I got a couple of panics, but not the one in the original report:
cc @edwin0cheng |
May be number of threads matter? I run this on machine with 16 real cores and 32 logic one. |
Mine is 4C8T. By the way, did you enable the proc macro and build script support? |
I suppose no. I heard about these options, but have no time to look at how to configure them in emacs. So all of them should have default values. |
I think it is #4676 ? |
I doubt it will be of much help, but I'm this is the error I'm getting (in nvim, using LanguageClient-neovim):
This seems to happen spontaneously, without me opening a new file at all. I'm just working on the code, periodically doing go-to-definition. At some point I'll notice it died because I get a This is on the 2020-06-08 release. If it matters, it's in a Rust project which is a workspace composed of several subprojects. |
I get the same error as #4451 (comment) |
The "Rust file outside current workspace is not supported yet." should be fixed now. The proc-macro one seems unrelated. |
@matklad I'm still getting that error regularly and then rust-analyzer stops working. This is with the 2020-06-29 release. |
@dkasak that's strage, as we no longer have "Rust file outside current workspace is not supported yet" string in the codebase. So, either our release process is broken and we've relased some very old code, or you might not be using the version you think you use. |
The releae process seem to use the right hash: https://github.com/rust-analyzer/rust-analyzer/runs/818231478?check_suite_focus=true#step:2:385 |
Indeed, thanks for the hint... I just saw the new VFS commit. I was running the previous release accidentally. So I can finally start using rust-analyzer again, I feel like I've recovered a superpower. 😄 Thanks! |
Here what I got in
I build rust-analyzer from source rev 1b136aa
The text was updated successfully, but these errors were encountered: