jestjs/jest
[Bug]: watch mode fails when git maintenance runs
Geschlossen
#13.869 geöffnet am 07.02.2023
:bug: BugHelp WantedPinnedWindows
Repository-Metriken
- Stars
- (45.361 Sterne)
- PR-Merge-Metriken
- (Durchschn. Merge 11T 22h) (11 gemergte PRs in 30 T)
Beschreibung
Version
29.4.0
Steps to reproduce
- Run your tests with
jest --watchand wait until they finish. - In another terminal, run
git maintenance run. - The watcher will fail
Expected behavior
Outside process shouldn't kill the watcher.
Actual behavior
Watcher dies immediately with
Error: EPERM: operation not permitted, lstat 'C:\Workspace\my-project\.git\objects\dc\a-very-long-hash'
Emitted 'error' event on NodeWatcher instance at:
at C:\Workspace\my-project\node_modules\jest-haste-map\build\watchers\NodeWatcher.js:274:14
at FSReqCallback.oncomplete (node:fs:207:21) {
errno: -4048,
code: 'EPERM',
syscall: 'lstat',
path: 'C:\\Workspace\\my-project\\.git\\objects\\dc\\a-very-long-hash'
}
I have also seen it point to .git\objects\maintenance.lock.
Additional context
This other issue is where I found the suggestion that it was a background git maintenance command that was causing the conflict, and once I knew that it was easy to reproduce.
Environment
System:
OS: Windows 10 10.0.22621
CPU: (12) x64 Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz
Binaries:
Node: 18.12.1 - ~\AppData\Local\fnm_multishells\30672_1675721836564\node.EXE
npm: 8.19.2 - ~\AppData\Local\fnm_multishells\30672_1675721836564\npm.CMD
npmPackages:
jest: ^29.3.1 => 29.4.0