-
Notifications
You must be signed in to change notification settings - Fork 11
Description
Problem
I'm working on a project that has rust code alongside other stuff. It seems that during it's activation process, Argus scans down from an open rust file and lands on the wrong "Workspace root"
Activating Argus in workspace [object Object]
setting up Argus backend
Getting workspace root
Looking for workspace root between /data/code_projects/godot/godot_rapier and /data/code_projects/godot/godot_rapier/rust/param_solver/src/equation_system/mod.rs
Workspace root /data/code_projects/godot/godot_rapier
So argus has decided /data/code_projects/godot/godot_rapier is the root, and indeed it's the root of the vscode project (where the .vscode folder lives), but the root of the rust project is one folder below that, at /data/code_projects/godot/godot_rapier/rust, so Argus can't find the relevant Cargo.toml.
Perhaps a simple setting "rust root" setting that can be optionally overridden per vscode workspace would be a good fix for this?
Possibly related to #38, though the exact error message reported there seems a bit different?
Logs
OS: linux (6.8.0-90-generic)
VSCode: 1.108.0
Error message
thread 'main' (885054) panicked at /home/bc/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/rustc_plugin-0.14.1-nightly-2025-08-20/src/cli.rs:28:6:
called `Result::unwrap()` on an `Err` value: CargoMetadata { stderr: "error: could not find `Cargo.toml` in `/data/code_projects/godot/godot_rapier` or any parent directory\n" }
stack backtrace:
0: __rustc::rust_begin_unwind
1: core::panicking::panic_fmt
2: core::result::unwrap_failed
3: rustc_plugin::cli::cli_main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.
Full log: https://paste.rs/ZQRNn