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've been running into issues with VSCode complaining about not being able to watch such a large workspace even though my host is already configured with "fs.inotify.max_user_watches=524288" (and has been for years).
I use a combination of search.useIgnoreFiles (set to its default of enabled) and manual files.watcherExclude settings to attempt to ignore chunks of my workspace. I've been debugging these issues and trying to figure out how VSCode could be running into the inotify limit despite these ignore settings, and despite the fact that (using tree and other tools) I've confirmed that my workspace is way under 524288 directory+files with just a couple of my excluded directories (much less all of them).
I found a nice script that uses /proc's fdinfo data to dump the list of files being watched (from a comment on another VSCode issue; #45295 (comment)).
The first issue I noticed while digging through this tool's output was that the file watcher was watching directories and files that should have been ignored by my .gitignore and search.useIgnoreFiles. If it included a directory in files.watcherExclude, it would be properly not watched, but entries in .gitignore were still getting watched. Inside VSCode, the Explorer does show .gitignore'd directories greyed out and file search does not include them in results, so that part is working correctly, but it seems like the list of .gitignore'd directories is not making it over to the file watcher.
VS Code version: Code 1.47.2 (17299e4, 2020-07-15T18:18:50.054Z)
OS version: Darwin x64 19.5.0
Remote OS version: Linux x64 5.2.17-1rodete3-amd64
System Info
Item
Value
CPUs
Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 x 2800)
search.useIgnoreFiles is used for search, not for file watching. .gitignore is not used for filewatching either. You want files.watcherExclude which is looks like you have found.
Issue Type: Bug
I've been running into issues with VSCode complaining about not being able to watch such a large workspace even though my host is already configured with "fs.inotify.max_user_watches=524288" (and has been for years).
I use a combination of search.useIgnoreFiles (set to its default of enabled) and manual files.watcherExclude settings to attempt to ignore chunks of my workspace. I've been debugging these issues and trying to figure out how VSCode could be running into the inotify limit despite these ignore settings, and despite the fact that (using
tree
and other tools) I've confirmed that my workspace is way under 524288 directory+files with just a couple of my excluded directories (much less all of them).I found a nice script that uses /proc's fdinfo data to dump the list of files being watched (from a comment on another VSCode issue; #45295 (comment)).
The first issue I noticed while digging through this tool's output was that the file watcher was watching directories and files that should have been ignored by my .gitignore and search.useIgnoreFiles. If it included a directory in files.watcherExclude, it would be properly not watched, but entries in .gitignore were still getting watched. Inside VSCode, the Explorer does show .gitignore'd directories greyed out and file search does not include them in results, so that part is working correctly, but it seems like the list of .gitignore'd directories is not making it over to the file watcher.
VS Code version: Code 1.47.2 (17299e4, 2020-07-15T18:18:50.054Z)
OS version: Darwin x64 19.5.0
Remote OS version: Linux x64 5.2.17-1rodete3-amd64
System Info
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
protected_video_decode: unavailable_off
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
viz_display_compositor: enabled_on
viz_hit_test_surface_layer: disabled_off_ok
webgl: enabled
webgl2: enabled
Extensions (19)
(2 theme extensions excluded)
The text was updated successfully, but these errors were encountered: