Watch warnings when running gulp dev
See original GitHub issueDeployment type
- Cloud Foundry Application (cf push)
- Kubernetes, using a helm chart
- Docker, using docker compose
- Docker, single container deploying all components
- [x ] Other (please provide below)
Expected behaviour
Actual behaviour
I deployed the Back End & Now I’m developing the Front End in Local. When running command gulp dev I get these warnings. The application runs just fine though.
Steps to reproduce the behavior
Log output covering before error and any error statements
gulp dev
[10:08:23] Using gulpfile ~/stratos-ui/gulpfile.js
[10:08:23] Starting 'dev-build'...
[10:08:23] Starting 'clean'...
[10:08:24] Finished 'clean' after 1.43 s
[10:08:24] Starting 'prepare-frontend'...
[10:08:25] Finished 'prepare-frontend' after 494 ms
[10:08:25] Starting 'copy:configjs'...
[10:08:25] Starting 'copy:bowerjs'...
[10:08:25] Finished 'copy:configjs' after 72 ms
[10:08:25] Finished 'copy:bowerjs' after 60 ms
[10:08:25] Starting 'copy:js'...
[10:08:30] Finished 'copy:js' after 5.51 s
[10:08:30] Starting 'copy:lib'...
[10:08:31] Finished 'copy:lib' after 347 ms
[10:08:31] Starting 'css:generate'...
[10:08:32] Finished 'css:generate' after 1.74 s
[10:08:32] Starting 'css'...
[10:08:33] Finished 'css' after 866 ms
[10:08:33] Starting 'i18n'...
[10:08:33] Finished 'i18n' after 35 ms
[10:08:33] Starting 'dev-template-cache'...
[10:08:33] Finished 'dev-template-cache' after 2.96 ms
[10:08:33] Starting 'copy:html'...
[10:08:36] Finished 'copy:html' after 2.89 s
[10:08:36] Starting 'copy:assets'...
[10:08:36] Finished 'copy:assets' after 36 ms
[10:08:36] Starting 'i18n'...
[10:08:36] Starting 'copy:index'...
[10:08:36] Finished 'copy:index' after 9.83 ms
[10:08:36] Finished 'i18n' after 39 ms
[10:08:36] Starting 'inject:index'...
[10:08:37] gulp-inject 304 files into index.html.
[10:08:37] Finished 'inject:index' after 304 ms
[10:08:37] Finished 'dev-build' after 14 s
[10:08:37] Starting 'dev'...
[10:08:37] Starting 'browsersync'...
[10:08:37] Serving HTTPS with the default BrowserSync certificate
[10:08:37] Proxying API requests to: https://ows.cf.nd-paas.itn.ftgroup/pp
[10:08:37] Finished 'dev' after 294 ms
[Browsersync] Access URLs:
--------------------------------------
Local: https://localhost:3100
External: https://10.194.9.216:3100
--------------------------------------
UI: http://localhost:3001
UI External: http://10.194.9.216:3001
--------------------------------------
[Browsersync] Serving files from: ./bower_components
[Browsersync] Serving files from: ./dist
[10:08:37] Finished 'browsersync' after 363 ms
[10:08:37] Starting 'watch'...
[10:08:37] 'watch' errored after 232 ms
[10:08:37] Error: watch /home/qdmb9595/stratos-ui/components/suse-branding/assets/images/ ENOSPC
at exports._errnoException (util.js:1020:11)
at FSWatcher.start (fs.js:1443:19)
at Object.fs.watch (fs.js:1470:11)
at Gaze._watchDir (/home/qdmb9595/stratos-ui/node_modules/gaze/lib/gaze.js:289:30)
at /home/qdmb9595/stratos-ui/node_modules/gaze/lib/gaze.js:358:10
at iterate (/home/qdmb9595/stratos-ui/node_modules/gaze/lib/helper.js:52:5)
at Object.forEachSeries (/home/qdmb9595/stratos-ui/node_modules/gaze/lib/helper.js:66:3)
at Gaze._initWatched (/home/qdmb9595/stratos-ui/node_modules/gaze/lib/gaze.js:354:10)
at Gaze.add (/home/qdmb9595/stratos-ui/node_modules/gaze/lib/gaze.js:177:8)
at new Gaze (/home/qdmb9595/stratos-ui/node_modules/gaze/lib/gaze.js:74:10)
[10:08:37] Error in plugin 'run-sequence(watch)'
Message:
watch /home/qdmb9595/stratos-ui/components/suse-branding/assets/images/ ENOSPC
Details:
code: ENOSPC
errno: ENOSPC
syscall: watch /home/qdmb9595/stratos-ui/components/suse-branding/assets/images/
filename: /home/qdmb9595/stratos-ui/components/suse-branding/assets/images/
Stack:
Error: watch /home/qdmb9595/stratos-ui/components/suse-branding/assets/images/ ENOSPC
at exports._errnoException (util.js:1020:11)
at FSWatcher.start (fs.js:1443:19)
at Object.fs.watch (fs.js:1470:11)
at Gaze._watchDir (/home/qdmb9595/stratos-ui/node_modules/gaze/lib/gaze.js:289:30)
at /home/qdmb9595/stratos-ui/node_modules/gaze/lib/gaze.js:358:10
at iterate (/home/qdmb9595/stratos-ui/node_modules/gaze/lib/helper.js:52:5)
at Object.forEachSeries (/home/qdmb9595/stratos-ui/node_modules/gaze/lib/helper.js:66:3)
at Gaze._initWatched (/home/qdmb9595/stratos-ui/node_modules/gaze/lib/gaze.js:354:10)
at Gaze.add (/home/qdmb9595/stratos-ui/node_modules/gaze/lib/gaze.js:177:8)
at new Gaze (/home/qdmb9595/stratos-ui/node_modules/gaze/lib/gaze.js:74:10)
[12:27:17] GET /v1/auth/session/verify```
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Watching Files | gulp.js
The watch() API connects globs to tasks using a file system watcher. It watches for changes to files that match the globs and...
Read more >How can a gulp task know if a gulp.watch task is running?
I have a gulp git task that does a checkout, thus changes the current working dir. I also have gulp watch tasks that...
Read more >Add option for gulp.watch to ignore task errors #216 - GitHub
I am trying to setup Gulp, so it displays any errors that plugins throw and then continues watching files. I tried gulp-plumber which...
Read more >gulp-watch - npm
Start using gulp-watch in your project by running `npm i gulp-watch`. There are 946 other projects in the npm registry using gulp-watch.
Read more >Super simple Gulp tutorial for beginners - freeCodeCamp
The Watch task will watch the files that you tell it to for any changes. Once it detects a change, it will run...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
So I suspect you’ve hit this issue. The fix mentioned on Stack Overflow is:
You need to increase
max_user_watches
, also, you may try bumping up the number of max open files (ulimit -n).It worked, thank you 😃