Watching files always detects changes

[rodnaph]

I'm running forever like this...

$> forever -w server.js

But changes are always detected in all the files in my project, and the script is restarted once a second.

If there is a legitimate change in a file then only that file is listed as being changed, and forever correctly restarts the script. But if there are no changes then it reports all files as having changed and restarts the script.

I'm on OSX 10.6.8, using zsh, node 0.4.10, and npm versions...

├─┬ [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├─┬ [email protected]
│ │ └── [email protected]
│ ├── [email protected]
│ ├─┬ [email protected]
│ │ └── [email protected]
│ ├─┬ [email protected]
│ │ └── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ ├── [email protected]
│ └─┬ [email protected]
│ ├─┬ [email protected]
│ │ └── [email protected]
│ └── [email protected]

[indexzero]

To my understanding you can use the .foreverignore file to control what files you would like to ignore from the watch list. @mmalecki would know more

[mmalecki]

Exactly what @indexzero said, you can just put some patterns into .foreverignore - files matching those pattern are ignored. Although, if if forever detect changes when no change happened, that's definitely a bug which I would love to hear more about.

[rodnaph]

Yes it detects changes when there are no changes. At first I thought maybe it was because I hadn't created a .foreverignore, but even creating one didn't change the behaviour.

If there's a way I can get you some more useful debugging info just let me know. Is it worth me doing any testing with the watch library?

[indexzero]

Try this:

forever config set debug true

[rodnaph]

forever config set debug true
info: Running action: config
data: {
data: root: '/Users/rod/.forever',
data: pidPath: '/Users/rod/.forever/pids',
data: sockPath: '/Users/rod/.forever/sock',
data: columns: [
data: 'uid',
data: 'command',
data: 'script',
data: 'forever',
data: 'pid',
data: 'logfile',
data: 'uptime'
data: ]
data: }

No extra info in the terminal sorry, it just lists every file in my working copy (except those in .gitignore) and restarts the script. It then does the same thing once a second.

[mmalecki]

@rodnaph Classic checklist: can you try with v0.4.12? Can you try on some different shell, like bash?

[rodnaph]

I think I've tracked this down to a bug in watch, which i've opened a pull request on:

mikeal/watch#13

[indexzero]

This has been resolved in watch: mikeal/watch#13 ... now waiting on the fix to get published to npm.

[geddski]

I'm getting this same issue. Wonder what the hold up is for publishing to npm.

[indexzero]

@GEDDesign the fix is published to npm. Have you reinstalled forever yet? Dependencies won't update themselves ;)

[geddski]

@indexzero cool you're right, watch 0.4.0 has been published to npm. I reinstalled forever but it still brought down watch 0.3.3. I submitted a pull request for updating the dependency version.

I manually replaced forever's watch with the latest and --watch still doesn't do anything. I can create another separate issue for that.

[mmalecki]

OK, can anyone with such issue provide me SSH access? I can't reproduce it neither on OS X nor Linux.

[geddski]

all is working now with [email protected]. This issue may remain closed.

[mmalecki]

Yay! <3