Strange errors as if the extension forget to execute the linter

[mariogeiger]

rust-analyzer version: rust-analyzer version: 0.4.2248-standalone (bfb8127 2025-01-06)

rustc version: rustc 1.83.0 (90b35a623 2024-11-26)

editor or extension: VSCode

code snippet to reproduce:

fn main() {
    println!("Hello, world!");
    let x = 5;
}

I get errors that make no sense, it's like if the extension forgot the execute the linter.

[seanhouli]

manually downgrading the extension to 0.3.2237 fixed it.

[Veykril]

Found the issue see https://github.com/rust-lang/rust-analyzer/pull/18848/files#r1904656621

Cant fix it right now though

[ChayimFriedman2]

To everyone: This is fixed by #18858, and there will probably be another stable release tomorrow. Sorry for the breakage. In the meantime you can revert to an older version.

[ChayimFriedman2]

@JoshLambda Sorry, I deleted your reply instead of replying to it. Here's my answer:

Good idea. Just let thousands of people get confused until tomorrow, instead of them seeing a fixed update pop in VS Code, that they could just apply right now.

I completely understand the frustration, but I cannot release a new rust-analyzer release. The keys are not in my hands. And @lnicola needs to sleep sometimes.

[JoshLambda]

The keys are not in my hands. And @lnicola needs to sleep sometimes.

Then I must apologize for directing my comment at you. So, it's a bigger issue related to the "bus factor", but it's probably off topic here.

[lnicola]

The bus factor might be relevant in other cases, but all of the developers who've ever put up an out-of-band nightly release are in a European time zone. The bus only runs there.

[lnicola]

This should now be fixed in v0.3.2253 (https://github.com/rust-lang/rust-analyzer/releases/tag/2025-01-07 on GitHub).