Proc macro server crashed

[Spanfile]

I don't think this is a duplicate of the other macro issues, I haven't seen this error message in them:

thread 'MacroExpander' panicked at 'assertion failed: `(left != right)`
  left: `0`,
 right: `0`', crates/proc-macro-srv/src/abis/abi_1_63/proc_macro/bridge/handle.rs:22:9
stack backtrace:
   0: rust_begin_unwind
             at /rustc/fe5b13d681f25ee6474be29d748c65adcd91f69e/library/std/src/panicking.rs:584:5
   1: core::panicking::panic_fmt
             at /rustc/fe5b13d681f25ee6474be29d748c65adcd91f69e/library/core/src/panicking.rs:143:14
   2: core::panicking::assert_failed_inner
   3: core::panicking::assert_failed
   4: proc_macro_srv::abis::abi_1_63::proc_macro::bridge::handle::InternedStore<T>::new
   5: proc_macro_srv::abis::abi_1_63::proc_macro::bridge::client::HandleStore<S>::new
   6: proc_macro_srv::abis::abi_1_63::proc_macro::bridge::server::run_server
   7: proc_macro_srv::abis::abi_1_63::proc_macro::bridge::server::<impl proc_macro_srv::abis::abi_1_63::proc_macro::bridge::client::Client<(proc_macro_srv::abis::abi_1_63::proc_macro::TokenStream,proc_macro_srv::abis::abi_1_63::proc_macro::TokenStream),proc_macro_srv::abis::abi_1_63::proc_macro::TokenStream>>::run
   8: proc_macro_srv::abis::abi_1_63::Abi::expand
   9: proc_macro_srv::abis::Abi::expand
  10: proc_macro_srv::ProcMacroSrv::expand
  11: proc_macro_srv::cli::run
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

Similarly to the other issues, the entire macro site is marked as an error with failed to write request: Broken pipe (os error 32).

Happens with at least all serde derives, tracing #[instrument], #[async_trait] and tonic's include_proto!.

rust-analyzer version: 0.0.0 (427061d 2022-06-19)

rustc version: rustc 1.63.0-nightly (bb8c2f411 2022-06-19) on Arch Linux

relevant settings: rust-analyzer.procMacro.attributes.enable is true, no macros have been ignored.

[lnicola]

Confirmed, looks like another ABI change. As a workaround you can downgrade to a nightly from around 2022-06-08.

[lnicola]

This broke between 2022-06-18 and 2022-06-19.

[bjorn3]

There are probably going to be a couple of other abi breakages in the near future. There are several PR's affecting libproc_macro open at the moment.

[dacut]

This workaround seems to work for me with VSCode:

1. Install rust-analyzer via rustup:

   % rustup +nightly component add rust-analyzer-preview

2. Get the path to the rust-analyzer nightly binary:

   % rustup which rust-analyzer
   /Users/dacut/.rustup/toolchains/nightly-aarch64-apple-darwin/bin/rust-analyzer

3. Add this to your VSCode settings.json, in the rust-analyzer.server.path setting:

   {
       "rust-analyzer.server.path": "/Users/dacut/.rustup/toolchains/nightly-aarch64-apple-darwin/bin/rust-analyzer"
   }

[flodiebold]

@dacut That's a different problem, caused by using an x86 VSCode and an ARM Rust toolchain. In that case, yours is indeed a possible workaround. (The other option would be to just install an aarch64 VSCode build.) This is unrelated to the problem in this issue though.

[dacut]

@flodiebold Where did you get the idea that I'm running x86 VSCode? I'm running ARM VSCode (from the Universal binary), ARM rust-analyzer, etc.:

% file /Applications/Visual\ Studio\ Code.app/Contents/MacOS/Electron
/Applications/Visual Studio Code.app/Contents/MacOS/Electron: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit executable x86_64
- Mach-O 64-bit executable x86_64] [arm64:Mach-O 64-bit executable arm64
- Mach-O 64-bit executable arm64]
/Applications/Visual Studio Code.app/Contents/MacOS/Electron (for architecture x86_64):	Mach-O 64-bit executable x86_64
/Applications/Visual Studio Code.app/Contents/MacOS/Electron (for architecture arm64):	Mach-O 64-bit executable arm64

% file ~/.vscode/extensions/rust-lang.rust-analyzer-0.4.1101-darwin-arm64/server/rust-analyzer
/Users/dacut/.vscode/extensions/rust-lang.rust-analyzer-0.4.1101-darwin-arm64/server/rust-analyzer: Mach-O 64-bit executable arm64

Same issue as here, with the failed to write request: Broken pipe (os error 32) resulting when rustup gets out-of-sync with the rust-analyzer binary.

[flodiebold]

@dacut It was a guess for the actual problem you're having, because the issue described here cannot be fixed by running another version of rust-analyzer. What's your rustc version, and what does the "Show RA Version" VSCode command say if you don't set rust-analyzer.server.path?

[dacut]

Hmm... it was suggested that ABI mismatches were at fault here from this Twitter reply by Lukas Wirth, hence my attempt to keep rust-analyzer in-sync with rustup.

Without rust-analyzer.server.path set, I currently get:

% rustc --version
rustc 1.63.0-nightly (5750a6aa2 2022-06-20)
> Rust Analyzer: Show RA version
rust-analyzer version: 0.0.0 (6fc5c3cd2 2022-06-20)

Interestingly, the version installed by rustup looks like it should be more broken... maybe?

% ~/.rustup/toolchains/nightly-aarch64-apple-darwin/bin/rust-analyzer --version
rust-analyzer 1.63.0-nightly (366bd7242 2022-06-12)

[flodiebold]

Ah yeah, the older version in rustup is likely just not showing the error message.