You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When debugging a Rust test in VSCode by clicking the "Debug" button above the test function, and then subsequently hitting the "Restart" button in the debug controls, rust-analyzer does not appear to recompile the code. This means that if changes have been made to the code since the initial debug launch, those changes are not reflected when the debug session is restarted.
The rust-analyzer.debug.buildBeforeRestart setting is set to true, which according to the documentation, should trigger a rebuild before restarting a debug session. However, this is not the observed behavior.
Steps to Reproduce:
Have a Rust project with a test function like the example provided.
Ensure "rust-analyzer.debug.buildBeforeRestart": true is set in your VSCode settings (preferably workspace settings).
Click the "Debug" button above the test function to start a debug session.
Make a change to the code that would affect the test's execution
Click the "Restart" button in the debug controls.
Observe that the debug session starts without recompiling the code, and the changes made in step 4 are not reflected in the restarted debug session.
Expected Behavior:
When the "Restart" button is clicked during a debug session, and rust-analyzer.debug.buildBeforeRestart is set to true, rust-analyzer should trigger a recompilation of the project before starting the new debug session, ensuring that the latest code changes are included.
The text was updated successfully, but these errors were encountered:
rust-analyzer version:
rust-analyzer version: 0.3.2228-standalone (fa4a40bbe8 2024-12-22)
rustc version:
rustc 1.83.0 (90b35a623 2024-11-26)
editor or extension: VSCode
relevant settings:
code snippet to reproduce:
Description of the Issue:
When debugging a Rust test in VSCode by clicking the "Debug" button above the test function, and then subsequently hitting the "Restart" button in the debug controls, rust-analyzer does not appear to recompile the code. This means that if changes have been made to the code since the initial debug launch, those changes are not reflected when the debug session is restarted.
The
rust-analyzer.debug.buildBeforeRestart
setting is set totrue
, which according to the documentation, should trigger a rebuild before restarting a debug session. However, this is not the observed behavior.Steps to Reproduce:
"rust-analyzer.debug.buildBeforeRestart": true
is set in your VSCode settings (preferably workspace settings).Expected Behavior:
When the "Restart" button is clicked during a debug session, and
rust-analyzer.debug.buildBeforeRestart
is set totrue
, rust-analyzer should trigger a recompilation of the project before starting the new debug session, ensuring that the latest code changes are included.The text was updated successfully, but these errors were encountered: