Regression in v0.2.686: `OUT_DIR` not set, enable "run build scripts" to fix

[shikhar]

Repro: https://github.com/shikhar/bazel-tonic/tree/4a27fbf7fe15a26804a3eb5eb3f7b62dafa9fba4

The error does not make sense because that setting defaults to true.

The error is gone after after rolling back to the last release v0.2.678.

[jonas-schievink]

I cannot reproduce this on current master (8a6bac3) with Rust 1.53.0

[shikhar]

How do I try master? I switched to the nightly channel and still see this.

[jonas-schievink]

You can follow the instructions here: https://github.com/rust-analyzer/rust-analyzer/tree/master/docs/dev#launching-rust-analyzer

Can you post the configuration picked up by the extension? It should be printed to the "Output" tab under "Rust Analyzer Client".

[shikhar]

Hmm, I can't reproduce this problem on another machine, so closing

[asaaki]

I have seen this issue right now myself, currently running RA nightly / 0.3.708 (VSC 1.59.0, Win10).
Have not a repro repo, but I have a suspicion:
The error happens when I work in a VSCode workspace with multiple folders/projects, but it does not happen when I open the project individually.

[trentbb]

Same as @asaaki
I am seeing this error when I have my whole workspace open. Opening up the individual project fixes the issue.

[chris-ricketts]

Same as @asaaki & @trentbb: discovered this when using bindgen in a workspace member crate.
Made a reproduction repo with a minimal bindgen
rust-analyzer --version: rust-analyzer 516eb40ba 2021-09-13 stable
OS: Arch Linux x86_64 (5.14.2)
Editor: Neovim 0.5

[declark1]

Also seeing this error when having my whole workspace open with multiple crates. Has anyone figured out a solution?

[shikhar]

Reopening as folks are running into it, although I am not currently experiencing this problem.

ED: also running into this!

[Raz-Hemo]

Also running into this when opening a workspace with multiple crates on vscode remote ssh.

[h0ru5]

had the same effect on single-project workspace after deleting and rewriting build.rs
restarting vs code did solve.