Debug fails to recognise the task has failed

[joaomoreno]

• Clone https://github.com/Pure-D/code-d and checkout commit 09ce158566e94bd28cfba9a9fd1365717fa863fd.
• Open that workspace in Code.
• Open launch.json and change the outDir values to use ${workspaceRoot}
• Hit F5

You get this error:

Open the task log and you'll see this:

Meaning that the npm task failed to execute.

When I run that task in the terminal, I can confirm that it returns a non-zero value. So why isn't Debug picking that up and informing me that the problem occurred in the task itself?

[isidorn]

Nice catch and cool repro steps - thanks!

[isidorn]

After talking to @dbaeumer there is a limitation in the task framework for this.

We need API to provide functionality of running a watch task that would return a TaskSummary both in the success and error case.
Once @dbaeumer adds API I can use it to address this issue, until then -> backlog.

[isidorn]

From 2016 -> closing as will not fix, outdated
fyi @alexr00 since there might be a duplicate, or this might have gotten fixed in the meantime