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
I'm filing this here from microsoft/vscode#162551 where they identified it as coming from parcel's watcher.
Type: Bug
Reproduction is hard, but something like the following should work:
use something like Rust where compiling can put a lot of load on the system, with a LSP that will start up when vscode does, and uses randomly named directories in the source tree. Rust-analyzer in particular triggers this.
have a very large project - I found this with a workspace with 10 different rust projects, each of which had 300-400 dependencies
start vscode, it will trigger the LSP which will start building.
Now, when the race happens something like the following is logged:
[2022-10-03 11:09:21.334] [renderer1] [error] [File Watcher (parcel)] Unexpected error: inotify_add_watch on '/home/robertc/Documents/src/projectname/target/debug/deps/rmetaWmhbGH' failed: No such file or directory (EUNKNOWN) (path: /home/robertc/Documents/src/projectname)
[2022-10-03 11:09:21.336] [renderer1] [error] [File Watcher (universal)] restarting watcher after error: inotify_add_watch on '/home/robertc/Documents/src/projectname/target/debug/deps/rmetaWmhbGH' failed: No such file or directory
What is happening here as far as I can tell is that the parent directory watch (on deps) informs the watcher that a new child directory exists (rmetaWmhbGH in this case). Then an arbitrary amount of time passes (this is why you need a loaded system, and the watcher now adds the recursive watch for this directory. However in the intervening time, the new directory was deleted again.
This is a totally normal thing to happen. tl;dr inotify_add_watch errors of the kind ENOENT should be ignored.
VS Code version: Code 1.71.2 (74b1f979648cc44d385a2286793c226e611f59e7, 2022-09-14T21:12:14.256Z)
OS version: Linux x64 5.15.0-48-generic snap
Modes:
Sandboxed: No
System Info
Item
Value
CPUs
Intel(R) Core(TM) i7-1065G7 CPU @ 1.30GHz (8 x 1500)
I'm filing this here from microsoft/vscode#162551 where they identified it as coming from parcel's watcher.
Type: Bug
Reproduction is hard, but something like the following should work:
Now, when the race happens something like the following is logged:
[2022-10-03 11:09:21.334] [renderer1] [error] [File Watcher (parcel)] Unexpected error: inotify_add_watch on '/home/robertc/Documents/src/projectname/target/debug/deps/rmetaWmhbGH' failed: No such file or directory (EUNKNOWN) (path: /home/robertc/Documents/src/projectname)
[2022-10-03 11:09:21.336] [renderer1] [error] [File Watcher (universal)] restarting watcher after error: inotify_add_watch on '/home/robertc/Documents/src/projectname/target/debug/deps/rmetaWmhbGH' failed: No such file or directory
What is happening here as far as I can tell is that the parent directory watch (on
deps
) informs the watcher that a new child directory exists (rmetaWmhbGH
in this case). Then an arbitrary amount of time passes (this is why you need a loaded system, and the watcher now adds the recursive watch for this directory. However in the intervening time, the new directory was deleted again.This is a totally normal thing to happen. tl;dr inotify_add_watch errors of the kind
ENOENT
should be ignored.VS Code version: Code 1.71.2 (74b1f979648cc44d385a2286793c226e611f59e7, 2022-09-14T21:12:14.256Z)
OS version: Linux x64 5.15.0-48-generic snap
Modes:
Sandboxed: No
System Info
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: disabled_software
multiple_raster_threads: enabled_on
opengl: disabled_off
rasterization: disabled_software
raw_draw: disabled_off_ok
skia_renderer: enabled_on
video_decode: disabled_software
video_encode: disabled_software
vulkan: disabled_off
webgl: unavailable_software
webgl2: unavailable_software
webgpu: disabled_off
Extensions (45)
A/B Experiments
The text was updated successfully, but these errors were encountered: