Closed ryanluker closed 1 year ago
Turned out to be an issue with the vscode-test dependency, that was fixed with a quick upgrade of that package. https://github.com/ryanluker/vscode-coverage-gutters/pull/412/commits/637b6367e13ddb027c29b767f4c08161267ce44d
For some reason the vscode (insiders latest) with windows-latest had started failing recently due to the following warning.