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
It would be a nice feature to provide a non-recursive watch flag.
Recursive watch can cause inotify watch exhaustion on linux.
non-recursive flag would give the ability to library users to watch with exclusions (e.g. node_modules), by first calculating themselves all directory paths that should be watched and then registering that many watchers on nsfw.
vscode currently faces an issue with this. They register each of the root directory paths in the workspace, and then just filter-out event delivery in case the path is in the exclusion list. But the inotify watches are already registered. see related code
I think providing this feature might solve this issue and many duplicates of it (with low effort on vscode side) without the need to switch to a different watcher library.
The text was updated successfully, but these errors were encountered:
It would be a nice feature to provide a
non-recursive
watch flag.Recursive watch can cause inotify watch exhaustion on linux.
non-recursive
flag would give the ability to library users to watch with exclusions (e.g.node_modules
), by first calculating themselves all directory paths that should be watched and then registering that many watchers onnsfw
.vscode currently faces an issue with this. They register each of the root directory paths in the workspace, and then just filter-out event delivery in case the path is in the exclusion list. But the inotify watches are already registered. see related code
I think providing this feature might solve this issue and many duplicates of it (with low effort on vscode side) without the need to switch to a different watcher library.
The text was updated successfully, but these errors were encountered: