Vscode-rust: Versions 0.4.6 and 0.4.7 on Windows stop tasks working on VSCode

[Aidan24]

Selecting any build or run task from the tasks menu never gets past the "> Executing task: cargo run <" line and leaves the status bar saying the task is still executing. Manually downgrading to 0.4.5 from https://ms-vscode.gallery.vsassets.io/_apis/public/gallery/publisher/rust-lang/extension/rust/0.4.5/assetbyname/Microsoft.VisualStudio.Services.VSIXPackage fixes the problem.

Windows 10 Version 1803 (Build 17134.165)
VSCode version 1.25.1
2017 C++ buildtools
stable-x86_64-pc-windows-msvc 1.27.1
Terminal Powershell

[robo-corg]

I downloaded https://marketplace.visualstudio.com/_apis/public/gallery/publishers/rust-lang/vsextensions/rust/0.4.5/vspackage and installed the vsix package and that got it working. Also on the same windows version and vscode.

edit: fixed url

Windows 10 Version 1803 (Build 17134.165)
VSCode version 1.25.1

[Aidan24]

Thanks robo-hamburger. I downloaded from your link and installed manually and still no joy. I've now tried on a (relatively) new install on a second machine and get the same results so there's clearly something I'm doing wrong. Both machines work fine on 0.4.5 but neither work on 0.4.7. I can get cargo build to work fine from the PowerShell prompt in VSCode on both machines but they both just stay at the > Executing task: cargo build < with no further progress on 0.4.7 when the task is selected from the menu (or Ctrl-Shift-B). If I then try to run another task it adds to the running tasks list but none ever progress. I've tried starting VSCode with code -e and looking in the developer logs, but I'm not sure what I'm looking for and nothing jumps out at me. Any advice to track this down? Thanks

[scautura]

I mentioned this in #359 as it seems to be because of the "fix" to make Tasks show in 1.25 (looks like 1.25.1 has added a solution to the "no tasks" issue because of how many addons it broke)

It's possible to edit the existing tasks created by 0.4.7 to change the line "type": "cargo", to "type": "shell" for each task, which then ends up with them working.

[Aidan24]

Thanks scautura that totally fixes it for me. The configured tasks now work as expected.
I'm still confused why it just worked for robo-hamburger and if there's something in my settings that is wrong or not as the extension should expect.

[robo-corg]

I posted the wrong url. Should have been to the 0.4.5 download. Sorry about that.

[apage43]

I was having a similar issue, and posted #371 which fixes it for me.

[Aidan24]

Fantastic thanks, hopefully a future update with this will make the extension work in Windows again.

[nrc]

This should be fixed on 0.4.9. Could someone report whether it is please?

[scautura]

Everything seems to be working as expected from here. Removed the customised tasks to be sure and they all run properly.

[Aidan24]

Seems to work for me too. Many thanks

[nrc]

Thanks for testing!