grunt watch doesn't work anymore

[svycka]

I have set autoWatch: true and thats all I changed. So I do grunt watch everything seems like working but when I change any file I get some errors.

Thats my console log:

Running "karma:unit:run" (karma) task
[2013-09-17 15:02:20.284] [DEBUG] config - Loading config C:\wamp\www\ng-boilerp
late\build\karma-unit.js
[2013-09-17 15:02:20.286] [WARN] config - config.configure() is deprecated, plea
se use config.set() instead.
WARN [watcher]: Pattern "C:/wamp/www/ng-boilerplate/src/**/*.coffee" does not ma
tch any file.
Fatal error: socket hang up
... Reload src\app\app.js ...
Completed in 120.938s at Tue Sep 17 2013 15:04:20 GMT+0300 (FLE Daylight Time) -
 Waiting...
OK
>> File "src\app\app.js" changed.

Running "jshint:src" (jshint) task
>> 4 files lint free.

Running "karma:unit:run" (karma) task
[2013-09-17 15:04:53.194] [DEBUG] config - Loading config C:\wamp\www\ng-boilerp
late\build\karma-unit.js
[2013-09-17 15:04:53.196] [WARN] config - config.configure() is deprecated, plea
se use config.set() instead.
Waiting for previous execution...
INFO [karma]: Delaying execution, these browsers are not ready: Firefox 23.0.0 (
Windows 8)
WARN [watcher]: Pattern "C:/wamp/www/ng-boilerplate/src/**/*.coffee" does not ma
tch any file.

also maybe related I have firefox 23.0.1 but karma says its 23.0.0 so I tried change firefox with PhantomJS same problem.

also maybe related karma-runner/karma#411

[brocksamson]

I'm seeing the same behavior within my application based on ng-boilerplate build process. I've made a few changes to the process and build but nothing that should affect this. I'm seeing this on both ubuntu 13.04 and windows 7 64 bit machines.

A few google searches led me to this: mklabs/tiny-lr#8 which sounds like the same issue on the grunt-contrib-live-reload plugin.

I think the root cause is changes to the behavior of nodejs in the .8.2 release, specifically the new behavior of raising exceptions when attempting to write to a destroyed socket. Previously writes to a destroyed socket were causing memory leaks in node.

My guess is that grunt-contrib-watch v 0.4.4 (specified in the package.json file) has this issue. I'll try upgrading to 0.5.3 on Monday to see if that resolves it.

[joshdmiller]

I'll see if I get the same behavior locally, but please let us know if
upgrading grunt-contrib-watch solves your issue.

Grunt watch and karma and their dirty little friends are ruining my day...

[roychoo]

had tried upgrading to v 0.5.3, still doesn't work :(

[roychoo]

Hmmmm, it seems that specifying port instead of runnerPort solve the issue for me.

from #37
is there already a PR for this?

[roychoo]

just submitted PR #153 for this.

[brocksamson]

This change is working for me as well. My computer running ubuntu 13.04 64 bit began working after changing the port. I'll check the windows one on Monday.

Nice work :)