Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Changing to tasks.json v2.0.0 breaks Pester problem matching

See original GitHub issue

System Details

Operating system name and version:
VS Code version:
PowerShell extension version:
Output from $PSVersionTable:

Windows 10 CU
1.12.2
1.1.0
5.1.15063.296

Issue Description

When the version of tasks.json is set to 2.0.0 and there is a single Pester error, the error shows up multiple times - on the order of 6 to 12 times for the same error. Switch the version back to 0.1.0 and the problem matcher (correctly) finds just one error.

Issue Analytics

State:
Created 6 years ago
Comments:9 (3 by maintainers)

Top GitHub Comments

2reactions

rkeithhillcommented, Jun 1, 2017

@mattmcnabb remove the line "isShellCommand": true and try again.

0reactions

fourpastmidnightcommented, Jan 18, 2019

Can this be closed? For one thing, I know that Pester has disabled progress reporting during the test run since it broke running tests on Linux/macOS due to PSv6 not supporting it very well. I also know that detecting problems using a problem matcher with Pester does work, as I’ve been using Pester for some time now with VS Code. I am, however, not using the $pester problem matcher that comes with this extension, but rather I am using an explicit problem matcher since I have been contributing to the Pester project itself. So, I’m just wondering if this issue has been fixed and can be closed, or whether the $pester problem matcher still needs to be updated?