-
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
The RA crashed into the 'proc-macro-srv-cli' #14991
Comments
Can't reproduce in 0.3.1541. Do you have any settings like |
That's using yesterdays rust nightly proc macro server, I wonder did something go wrong with the subtree sync? |
Oh, right, I had the previous nightly. Oof. |
-in-rust-tree = [
"proc-macro-srv/sysroot-abi",
"ide/in-rust-tree",
"syntax/in-rust-tree",
]
+sysroot-abi = ["proc-macro-srv-cli/sysroot-abi"]
+in-rust-tree = ["sysroot-abi", "ide/in-rust-tree", "syntax/in-rust-tree"] This is the only diff part that seems relevant, but this should work fine no? Only difference is the intermediate feature flag but to my knowledge that will pass through properly right? |
@zerodegress you can get around this by downgrading your toolchain to a version from before yesterday for now |
https://github.com/rust-lang/rust/blob/master/src/bootstrap/tool.rs#L707-L718 I think the proc macro server gets built with |
Ah, that explains it. So no subtree problems, we just need to update the build step |
Thanks, it realy works. |
…Veykril Fix rust-analyzer proc macro server The feature now exists on `proc-macro-srv-cli`, and without it the proc macro server will bail rigth out. CC rust-lang/rust-analyzer#14991
Fixed in the |
rust-analyzer version: rust-analyzer version: 0.3.1541-standalone (2f1b7ce 2023-06-04)
rustc version: rustc 1.72.0-nightly (e6d4725c7 2023-06-05)
looks like that.
i am using the crate bevy, and when i use some macros there comes the crash:
looks like it is saying 'the pipe is closing',but i dont know how it means.
i tried to restart the RA event the computer but not working.
The text was updated successfully, but these errors were encountered: