Watch is triggered twice for files and folders with same name

[mike-suggitt]

If i run a watch for /html/**/* and have a file structure such as this:

html
     folder.html
     folder2.html
     folder
             code.html
             code2.html

When I make changes to code.html then watch is triggered twice, firstly with folder.html then with code.html. If I change the name of "folder" to "folder2" and update folder.html it will only trigger once.

Likewise if I then make changes to code2.html then it will trigger twice, once with folder2.html and then with code2.html

[UltCombo]

Can you try the latest version and check if you can still reproduce the issue? I cannot reproduce it.

[UltCombo]

I didn't manage to reproduce the issue when editing files, but I did manage to trigger a similar issue: when creating a new directory inside folder, it triggered a change event for folder.html and folder2.html. It looks like a Chokidar bug, will investigate and report it tomorrow if I manage to.

[mike-suggitt]

I'll re-check with current and latest version and let you know. The other thing I've thought of which may be an issue is that I'm using WebStorm so that may be doing something funky with the way it saves files (e.g. twice)

[UltCombo]

Seems related to nodejs/node#4351, libuv/libuv#682

[UltCombo]

This may be fixed in Node v7.1.0 as it uses libuv 1.10.0 which likely includes a fix for this issue. Can someone test on a Windows machine to confirm?

[UltCombo]

It seems this specific problem (firing unexpected change events for upper-level files) has been fixed in Node 7.1.0. However, it seems a new problem arises in Node 7.1.0 as well: after the first addDir event fires (e.g. addDir html/folder/a), it seems it will no longer fire further unlinkDir/addDir events for that given path. Will need further investigation, but this is likely a Chokidar or libuv issue.