You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When debugging a test it feels like it never finishes, after digging into what could cause this I think i have traced it down to being inside a git repo but only when at the root(for example If I was to load a sub project folder of my monorepo in vscode it seemed to work fine)
To note the debugging of the test itself works fine, its just stuck after.
And after that get into a bad state that prevent any further test run(even plain test without the debugger)
Currently on 0.8.4 but this seems to have been happening since the rewrite(0.6.0)
Reproduction
git clone https://github.com/timotheeguerin/vitest-debug-repro (this is just the lib1 package from the workspace sample from vitest repo but inside a git repo)
cd vitest-debug-repro
npm install
code .
Run debug test for double.test.ts> double
Output
[INFO 10:13:40 AM] [v0.8.4] Vitest extension is activated because Vitest is installed or there is a Vite/Vitest config file in the workspace.
[INFO 10:13:40 AM] [API] Running Vitest: v1.5.0 (vite.config.ts)
[INFO 10:13:40 AM] [API] Starting Vitest process with Node.js: /Users/timotheeguerin/.nvm/versions/node/v20.11.1/bin/node
[INFO 10:13:40 AM] [API] Vitest process 36375 created
[INFO 10:13:41 AM] [API] Collecting tests: test/double.test.ts
[INFO 10:13:50 AM] Running 1 file(s) with name pattern: ^\s?double$
[INFO 10:13:53 AM] [DEBUG] Starting debugging on localhost:61240
[INFO 10:13:53 AM] Running 1 file(s) with name pattern: ^\s?double$
[Worker] Debugger listening on ws://127.0.0.1:61240/a4b52b9e-eb76-4469-be08-384bc9d49c83
For help, see: https://nodejs.org/en/docs/inspector
[Worker] Debugger attached.
[INFO 10:13:53 AM] [DEBUG] Debugging started
[INFO 10:13:54 AM] Running 1 file(s) with name pattern: ^\s?double$
[Worker] Debugger listening on ws://127.0.0.1:61240/8f44f777-501f-4866-9580-462735cc2d29
For help, see: https://nodejs.org/en/docs/inspector
[INFO 10:14:00 AM] Running 1 file(s) with name pattern: ^\s?double$
[INFO 10:14:01 AM] Running 1 file(s) with name pattern: ^\s?double$
Version
0.8.4
Validations
Check that you are using the latest version of the extension
Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
I'm experiencing the same, but the tests are not in root of the repo.
Trying to debug a test in ./tests/*.test.ts hangs. Actually, I tried moving the tests to other paths and it always hanged.
sheremet-va
added
p5-urgent
Fix build-breaking bugs affecting most users, should be released ASAP (priority)
and removed
p3-minor-bug
An edge case that only affects very specific usage (priority)
labels
May 7, 2024
Describe the bug
When debugging a test it feels like it never finishes, after digging into what could cause this I think i have traced it down to being inside a git repo but only when at the root(for example If I was to load a sub project folder of my monorepo in vscode it seemed to work fine)
To note the debugging of the test itself works fine, its just stuck after.
And after that get into a bad state that prevent any further test run(even plain test without the debugger)
Currently on 0.8.4 but this seems to have been happening since the rewrite(0.6.0)
Reproduction
git clone https://github.com/timotheeguerin/vitest-debug-repro
(this is just the lib1 package from theworkspace
sample from vitest repo but inside a git repo)cd vitest-debug-repro
npm install
code .
double.test.ts> double
Output
Version
0.8.4
Validations
The text was updated successfully, but these errors were encountered: