vitest-dev / vscode

VS Code extension for Vitest
https://vitest.dev/vscode
MIT License
726 stars 78 forks source link

Vitest process exited with exit code null #430

Open henriksjostrom opened 4 days ago

henriksjostrom commented 4 days ago

Describe the bug

On vscode start I'm presented with an error from the vtest extenstion. Nothing seems to work after this error. No abnormal memory or cpu consumption.

Reproduction

I'm afraid that I'm at a loss where to even start with the reproduction.

Output

[INFO 4:28:43 PM] [v0.12.4] Vitest extension is activated because Vitest is installed or there is a Vite/Vitest config file in the workspace.
[INFO 4:28:44 PM] [API] Running Vitest v1.6.0 (config-service/vitest.config.ts) with Node.js: /snap/bin/node
[Error 4:28:45 PM] [Error Error] Vitest process exited with code null
Error: Vitest process exited with code null
    at ChildProcess.d (/home/henrik/.vscode/extensions/vitest.explorer-0.12.4/dist/extension.js:20:170)
    at ChildProcess.emit (node:events:514:28)
    at ChildProcess._handle.onexit (node:internal/child_process:294:12)


### Version

v0.12.4

### Validations

- [X] Check that you are using the latest version of the extension
- [X] Check that there isn't [already an issue](https://github.com/vitest-dev/vscode/issues) that reports the same bug to avoid creating a duplicate.
- [X] Check that this is a concrete bug. For Q&A open a [GitHub Discussion](https://github.com/vitest-dev/vscode/discussions) or join our [Discord Chat Server](https://chat.vitest.dev).
- [X] The provided reproduction is a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of the bug.
github-actions[bot] commented 4 days ago

Hello @henriksjostrom. Please provide a minimal reproduction using a GitHub repository or StackBlitz (you can also use examples). Issues marked with needs reproduction will be closed if they have no activity within 3 days.

garyking commented 3 days ago

The issue starts happening after updating VSC to 1.91.0.

0.6.3 of this extension is the latest version that doesn't have this error.

This issue is presumably related to #383.