Proc macros not expanding again in rust 1.78

[mkolopanis]

rust-analyzer version: rust-analyzer version: 0.4.1959-standalone

rustc version: rustc 1.78.0 (9b00956e5 2024-04-29)

editor or extension: VS-Code 1.89.1
dc96b837cf6bb4af9cd736aa3af08cf8279f7685
x64

relevant settings: None

Appears to be the same issue as #16331 again, as mentioned in #17178.

Have tried using the pre-release and stable releases of rust-analyzer in vscode which has no effect.
This seems to be the best MWE mentioned in #16331 and the proc macro expansion still fails with this MWE.
Occurs on a brand new project and even after removing target directory.

I haven't been able to find anything on this on the Forums, and the linked issues were asked to make a new one (e.g. this one).

Rust Analyzer Output

024-05-14T16:22:21.270686Z ERROR rust_analyzer::main_loop: FetchBuildDataError:
error: failed to run `rustc` to learn about target-specific information

Caused by:
  process didn't exit successfully: `/home/user/.vscode/extensions/rust-lang.rust-analyzer-0.4.1959-linux-x64/server/rust-analyzer /home/user/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/bin/clippy-driver /home/user/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/bin/rustc - --crate-name ___ --print=file-names --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro --print=sysroot --print=split-debuginfo --print=crate-name --print=cfg` (exit status: 1)
  --- stderr
  error: Unrecognized option: 'keep-going'


error: failed to run `rustc` to learn about target-specific information

Caused by:
  process didn't exit successfully: `/home/user/.vscode/extensions/rust-lang.rust-analyzer-0.4.1959-linux-x64/server/rust-analyzer /home/user/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/bin/clippy-driver /home/user/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/bin/rustc - --crate-name ___ --print=file-names --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro --print=sysroot --print=split-debuginfo --print=crate-name --print=cfg` (exit status: 1)
  --- stderr
  error: Unrecognized option: 'keep-going'

code snippet to reproduce:

#![no_std]

#[cfg(feature = "std")]
extern crate std;

#[derive(Debug, Clone, Copy, PartialEq, Eq)]
#[cfg_attr(feature = "std", derive(thiserror::Error))]
enum Test {
    One,
    Two,
}
impl core::fmt::Display for Test {
    fn fmt(&self, f: &mut core::fmt::Formatter<'_>) -> core::fmt::Result {
        write!(f, "{:?}", self)
    }
}
fn main() {}

Cargo.toml

[package]
 name    = "rust-test"
 version = "0.1.0"
 edition = "2021"

[features]
 std = [ "dep:thiserror" ]

[dependencies]
 thiserror = { version = "1.0.60", optional = true }

[Veykril]

Do you have any relevant cargo configs set in the vscode settings? I am a bit confused as to why the clippy-driver appears in your logs

#17127 related

[mkolopanis]

I was a bit confused to see that myself. I do have these overrides I found I needed to get the "Problems" tab to populate correctly with the clippy outputs at one point. Though they could be holdovers from a early workaround or something.

 "[rust]": {
        "editor.defaultFormatter": "rust-lang.rust-analyzer",
        "editor.formatOnSave": true
    },
 "rust-analyzer.cargo.features": "all",

 "editor.formatOnSave": true,
 "rust-analyzer.cargo.buildScripts.overrideCommand": [
    
        "cargo",
        "clippy",
        "--all-features",
        "--quiet",
        "--workspace",
        "--message-format=json",
        "--all-targets",
        "--",
        "-D",
        "warnings"
    ],
    "rust-analyzer.procMacro.enable": true,
    "rust-analyzer.check.command": "clippy",
    "rust-analyzer.check.extraArgs": [
        "--quiet",
        "--",
        "-D",
        "warnings"
    ],

[micolore]

neovim
rust 1.78
rust-analyzer 2024-05-13

upgrade rust version（1.78） has this error

[Veykril]

That rust-analyzer.cargo.buildScripts.overrideCommand is certainly questionable, but confirms my suspicion. #17232 should fix this, please try the latest nightly r-a release or next monday's stable

[mkolopanis]

Thank you!