failed to write request: Broken pipe (os error 32)rust-analyzermacro-error

[kulame]

/// Instructions supported by the generic Name Registry program
#[derive(Clone, BorshSerialize, BorshDeserialize, PartialEq)]
pub enum AggregatorInstruction {
    /// Accounts:
    ///   0. [writable] The aggregator to initialize
    ///   1. [sign] Owner
    ///   2. [] Rent sysvar
    ///   3. [] Clock sysvar
    Initialize(Config),
    /// Accounts:
    ///   0. [writable] The aggregator
    ///   1. [sign] Oracle
    ///   2. [] Clock sysvar
    Submit { timestamp: Timestamp, value: Value },
}

it show some error

failed to write request: Broken pipe (os error 32)rust-analyzermacro-error
failed to write request: Broken pipe (os error 32)rust-analyzermacro-error

[bjorn3]

Just to confirm. Are those proc macros from the borsh crate?

[kulame]

yep, it used borsh

[yotamofek]

This is breakage probably caused by the merging of this PR: rust-lang/rust#87264
I'm guessing it has to do with being on the latest rustc nightly rather than a specific crate's proc macros :)

[kulame]

TvT

[bjorn3]

https://github.com/rust-lang/rust/pull/87264/files#diff-b42e9adad2cfc0be65632a15d616c95b812effe27357d9f5aee13cd949d68190R65

the proc macro bridge will need to be updated. https://github.com/rust-analyzer/rust-analyzer/tree/master/crates/proc_macro_srv/src/abis needs to get a new directory for the 1.58 abi. @alexjg would you mind doing this?

[alexjg]

I'll sort it out tomorrow!

[qm3ster]

idk if tomorrow means fix will ship this Monday or next, but to whomst'd've it may've concerned, the temporary fix is:

rustup default nightly-2021-11-12

to undo:

rustup default nightly
rustup uninstall nightly-2021-11-12

(obviously not hurrying anyone anywhere, btw)

[kulame]

great!!!

[Sword-Smith]

Having the same problem in VS Code with rust-analyzer. Will prefer to stay on stable and not upgrade to nightly, so there is no fix for me yet.

[qm3ster]

@Sword-Smith we were downgrading the nightly, and that has since been resolved in #10769 and released yesterday.
We can all return to the current nightly now.
If you are currently having a problem with stable rustc, which is 1.56.1, it's either a regression for the old ABI or an unrelated problem altogether.

Please make sure:

1. you rustup update your stable
2. Ctrl-Shift-P > Rust Analyzer: Show RA Version shows rust-analyzer version: 183ef048f 2021-11-22 stable (that's the actual rust-analyzer binary that the matklad.rust-analyzer VS Code extension downloads separately). If not, close all your VS Code windows, it will try to update on next open.
3. cargo clean your project

and then post the particular error you are getting.

[Sword-Smith]

1. you `rustup update` your stable

2. Ctrl-Shift-P > Rust Analyzer: Show RA Version shows `rust-analyzer version: 183ef048f 2021-11-22 stable` (that's the actual rust-analyzer binary that the `matklad.rust-analyzer` VS Code extension downloads separately). If not, close **all** your VS Code windows, it will try to update on next open.

3. `cargo clean` your project

I went through all your steps but had to add another one, even though VS Code showed the version you described in step 2:

4. Close all VS Code windows and open them again.

Edit: I took the liberty to post this on Stack Exchange as there is there are too few Rust questions on Stack Exchange: https://stackoverflow.com/questions/70079983/rust-analyzer-failed-to-write-request-broken-pipe-os-error-32/70079984

[ErwanDL]

Just encountered the same problem as @Sword-Smith, I believed it happened just after I updated to the latest version of VSCode. I ran rustup update and then quit VSCode and restarted it and the error messages went way (not sure if the rustup update was necessary or if fully restarting VSCode would have sufficed).