#TEMPORARILY INCREASE FILEWATCHER LIMIT CODE#
You may configure VS code file watcher exclusion patterns as described here. (by the way when it does not - run sudo code -user-data-dir -verbose to see what the problem is - that's how I figured out it had to do with file watchers limit). Now run sudo code -user-data-dir and it should open vscode with admin privileges this time. So to permanently fix the issue - either disable or remove this service/package. The above, however, will likely need to be done again when restarting the system - the process we identified as responsible for taking much of the file watchers will (in my case - baloo_file) - will again so the same in the next boot.Or you can simply kill the process you found in (1) that consumes the most file watchers (in my case, baloo_file).Sudo sysctl -w fs.inotify.max_user_watches=16384 The problem was: when a few builds are running simultaneously they would fail because watchers limit is reached.įirst things first I've tried to add the following to the : module.exports = and then set it to a different value (a lower value may do it)
In my case I wanted to disable watcher completely, because of the tests running on CI using vui-cli plugin which starts web-pack-dev server for each test. While almost everyone suggests to increase a number of watchers, I couldn't agree that it is a solution.
0 kommentar(er)
