Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Required for gulp / grunt watch bump #137

Closed
3 tasks done
shama opened this issue Jul 25, 2014 · 5 comments
Closed
3 tasks done

Required for gulp / grunt watch bump #137

shama opened this issue Jul 25, 2014 · 5 comments

Comments

@shama
Copy link
Owner

shama commented Jul 25, 2014


Above issues are fixed in navelgazer and implemented in the navelgazer branch here. Just a few skipped tests to fix.

@meinaart
Copy link

@shama: our latest fixes should take care of point 2 right? Is point #3 already done? I am very anxious to upgrade grunt-contrib-watch because it's really hogging my CPU all day.

@shama
Copy link
Owner Author

shama commented Aug 28, 2014

@meinaart It doesn't. That is a different issue than what your PR addressed.

FWIW, you can increase the options: { interval: 500 } in grunt-contrib-watch and that might alleviate some of the CPU usage for the time being.

@meinaart
Copy link

meinaart commented Sep 1, 2014

GH-104 should fix the issues with events across multiple instances right?

Thanks for the tip :).

@heycalmdown
Copy link

Is this still alive issue? I'm having trouble with constant CPU usage with Gulp. Or can we navelgazer in production instead?

@polybuildr
Copy link

Ping?

@shama shama closed this as completed Aug 3, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants