Closed gjsjohnmurray closed 2 years ago
On Windows at least, the node path auto-detect changes from #957 were producing intermittent failures. One of these was caused by vscode.env.shell sometimes being empty, perhaps a consequence of being called very early in VS Code startup.
Upstream issue https://github.com/microsoft/vscode/issues/160694
On Windows at least, the node path auto-detect changes from #957 were producing intermittent failures. One of these was caused by vscode.env.shell sometimes being empty, perhaps a consequence of being called very early in VS Code startup.