What's the correct way to debug a test in Rust Rover?

I have a test in my Rust code that I want to debug. While RustRover picks up the test and the hover/context menu allows me to run it, when I click the debug option I get an error

error: the option `Z` is only accepted on the nightly compiler

It looks like RustRover automatically appends --format=json --exact -Z unstable-options --show-output to the test. I would think this is an issue with the compiler but it looks like VSCode doesn't have this problem and I'm able to debug my tests with no problem. Is there something I'm missing like an option or otherwise in RustRover?

Solution

Turns out it's a known bug in RustRover. See Youtrack Issue. Updating to the newest version (2024.2 EAP) fixed it

Defining and blanket implementing a common trait to avoid dependencies in Rust
Migrating from BASIC to Rust, what do I do with On Gosub?
Batch-update adjacent elements in a Vec in Rust (for performance)
Diagonal matrix from vector
How to define a const closure inside a generic struct
Circular Reference Construction in Rust
Failed to select a version for the requirement `rand = "^0.9.0"`
Is Mutex/Lock required if runing on a single core CPU
How do I choose a random value from an enum?
Use a different cargo profile for CI
How can I debug why a dependency is in my Cargo.lock?
Use `write!` without bringing the Write trait into scope in Rust
Polars Rust API creating a dataframe from a string variable / reading csv with options from a string
expected associated type, found type parameter
Format specifier for truncating string-like types
Matching enum variant without specifying variants in Rust macro
How do you create a column of a vector/list type in Polars using Rust
How to create a Rust struct with string members?
Schedule wakeup with WinAPI in Rust
Projection matrix causes vertical offset
Iterate over a generic iterable without having to clone
Unauthorized access. 'Listen' claim(s) are required - Azure function using RUST (event hub)
Rust: double linked list
Is there a nicer way to implement Display for structs that own collections of things with Display?
Swift catch with case let
Why does Rust consider an owning closure to exist for 'static lifetime?
Error: "linker 'cc' not found" when cross compiling a rust project from windows to linux using cargo
Why am I getting "App state is not configured" in Ntex despite using App::state()?
How do I inspect local variables or use the watch window with Rust code using VSCode and LLDB?
How to share a HashMap state amongst Yew Rust components?