rust-lang / rust-lang/rust-analyzer
Project causes multiple "Failed to run build scripts"
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.9k
- Forks
- 2.2k
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 72
Description
rust-analyzer version: rust-analyzer 0.3.1238-standalone (61504c8d9 2022-10-08)
rustc version: rustc 1.64.0 (a55dd71d5 2022-09-19)
Opening this project (https://github.com/wireapp/core-crypto) I'm running into the following errors:
[ERROR project_model::workspace] cyclic deps: mls_crypto_provider(CrateId(223)) -> core_crypto_keystore(CrateId(98)), alternative path: core_crypto_keystore(CrateId(98)) -> mls_crypto_provider(CrateId(223))
[ERROR project_model::workspace] cyclic deps: mls_crypto_provider(CrateId(223)) -> mls_crypto_provider(CrateId(223)), alternative path: mls_crypto_provider(CrateId(223))
[ERROR flycheck] Flycheck failed to run the following command: "cargo" "clippy" "--workspace" "--message-format=json" "--manifest-path" "/Users/augusto/projects/core-crypto/Cargo.toml" "--all-targets" "--all-features"
[ERROR rust_analyzer::lsp_utils] cargo check failed
Cargo watcher failed, the command produced no valid metadata (exit code: ExitStatus(unix_wait_status(25856))):
error: -Zbuild-std requires --target
[ERROR rust_analyzer::lsp_utils] rust-analyzer failed to run build scripts
error: -Zbuild-std requires --target
I could reproduce it in neovim and in vscode. The cyclic deps error are dev-dependencies and I think this is reported already.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the report with the core-crypto project in Neovim or VS Code, then trace the reported paths through project_model::workspace, flycheck, and the cargo watcher. Determine whether the cyclic dependency and -Zbuild-std errors are separate failures; done means the project produces valid metadata and no longer reports the build-script failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100