Third party extension can break starting the default build task

[joaomoreno]

Edit: See below for more details

Version: 1.70.0-insider (user setup)
Commit: 3da2d669a4dcf93938a262ba92f50b128ca7262a
Date: 2022-07-20T05:16:09.131Z
Electron: 18.3.5
Chromium: 100.0.4896.160
Node.js: 16.13.2
V8: 10.0.139.17-electron.0
OS: Windows_NT x64 10.0.22000

Ctrl Shift B does nothing in today's build.

Also, running Tasks: Run Build Task shows this:

[joaomoreno]

After restarting, pressing Ctrl Shift B shows this:

No output :(

[Balastrong]

I had the same issue this morning with the Insiders build, Cmd + Shift + B was not working and showing the "corrupted build" toast instead.

However, after restarting vscode a couple times now it works (build starts) but the terminal does not automatically open.

Here my specs:

Version: 1.70.0-insider
Commit: 3da2d669a4dcf93938a262ba92f50b128ca7262a
Date: 2022-07-20T05:31:50.008Z
Electron: 18.3.5
Chromium: 100.0.4896.160
Node.js: 16.13.2
V8: 10.0.139.17-electron.0
OS: Darwin arm64 21.5.0

[joaomoreno]

Oh my. This is due to having the Deno extension installed. Very bad!

Unsure what to do here. I think it's worthwhile investigating how an extension can break the setup so badly, maybe they are doing something which we've overlooked? Keeping the issue open so some investigation can happen.

[Tyriar]

I had the same issue this morning with the Insiders build, Cmd + Shift + B was not working and showing the "corrupted build" toast instead.

The Deno extension modifies source? 😕

[joaomoreno]

Unsure if @Balastrong hit the same issue as me. :(

[Balastrong]

I had the issue only the first time this morning, but I don't have the Deno extension so maybe it's not the same.
Considering it happened on Insiders as soon as it was updated, maybe it's not something to worry about too much (in my case).

The Deno thing looks different ^^'

[meganrogge]

Closing this for now, but pls comment if you see it again or can reproduce