Version:
Domino 4.x 5.x with VSCode
Issue:
When running a workspace with VSCode an error prompt appears:
This is also visible in the support bundle logs with similar errors:
[File Watcher (node.js)] Failed to watch /home/ubuntu/.local/share/code-server/Machine/settings.json
for changes using fs.watch() (Error: ENOSPC: System limit for number of file watchers reached, watch
'/home/ubuntu/.local/share/code-server/Machine/settings.json
Root Cause:
This indicates that the VS Code file watcher is running out of handles because the workspace is large and contains many files
Resolution:
Before adjusting platform limits, make sure that potentially large folders, such as Python .venv, are added to the files.watcherExclude setting (more details below).
// Configure paths or glob patterns to exclude from file watching.
"files.watcherExclude": {
"**/.git/objects/**": true,
"**/.git/subtree-cache/**": true,
"**/node_modules/*/**": true,
"**/.hg/store/**": true
},
You would change this in either one of settings section as described here:
- User Settings- Settings that apply globally to any instance of VS Code you open.
- Workspace Settings- Settings stored inside your workspace and only apply when the workspace is opened.
See the settings editor section further to make those changes.
*Note - to ensure that you can make change in the settings editor UI, look for the following setting:
workbench.settings.useSplitJSON and enable this. This will give you two panes, a split pane on the left (read only editor) and a split pane on the right (writeable editor). Make your changes in the right pane and save.
You can also increase the max_user_watches value on the server side:
# insert the new value into the system config
echo fs.inotify.max_user_watches=<insert new watchers value> | sudo tee -a /etc/sysctl.conf && sudo sysctl -p
# check that the new value was applied
cat /proc/sys/fs/inotify/max_user_watches
The max value that could be placed here would be 524288 (maximum number of files that can be watched).
Notes:
Comments
0 comments
Please sign in to leave a comment.