"Task cannot be tracked" frustration

[jrieken]

• use https://github.com/microsoft/vscode-github-issue-notebooks
• run npm i
• the project defines an npm script bundle-all
• there is a task defined for the bundle-all script
• now, remove this line https://github.com/microsoft/vscode-github-issue-notebooks/blob/4c50e8f23b70dd073c4a181725f38867667e73cd/.vscode/tasks.json#L21
• press F5
• 🐛 you get a message about being unable to track a task, that message is really unhelpful

[connor4312]

I think this is because you have no problem matchers for the task

But the message could be more helpful

[jrieken]

hm... but I don't want problem matchers...

[jrieken]

As suggestion, I now added some problem matcher. It did need a reload of the renderer and now I can launch. Tho, I think a that shouldn't be needed at all

[jrieken]

updates steps: remove this line: https://github.com/microsoft/vscode-github-issue-notebooks/blob/4c50e8f23b70dd073c4a181725f38867667e73cd/.vscode/tasks.json#L21

[isidorn]

@alexr00 is out this week. We have always been behaving like this.
Thus assigning to February so I look into this in debt week. This experience definetly needs to be improved. Thanks for sharing feedback Joh!

[weinand]

I've removed the "debug" label because this issue is unrelated to debug.

[alexr00]

There's a long standing feature request for having background tasks be prelaunch tasks without having a problem matcher. Since background tasks go until they're killed, we don't have anything to trigger off of to say that the task is "done enough". The problem matcher lets us have something to key off of.

[isidorn]

After discussing with @alexr00 we decided that I improve the message in debug to make sure that the user is aware that a problem matcher is needed.
And I will also offer to Debug Anyway.

I have no better suggestion.
Since there is already an issue for tasks, I will unassing @alexr00