Add watch filters to prevent action being invoked twice about fswatch HOT 2 CLOSED

Definitely seeing the same issue for the same use-case (as @fatuhoku described above) and it's definitely undesirable. Any thoughts on whether this will be addressed in the upcoming bug fixes, @alandipert? Thanks again for the nice work. This has been very helpful in my workflow.

UPDATE: After some thinking, I believe that when my (Python) unittests are executed, new *.pyc files are also compiled, thus producing another "change" event for the directory-this results in action being invoked twice. A little more digging around, I think eventPaths are actually only directories and not files. This will be difficult to filter for files (in my case, it would be nice to filter out *.pyc in the directory). At the moment, I'm thinking that perhaps this hack will be able to fix my issue: write timestamp to temporary file, rescan for any __.py* file changed after that time-if exist continue with callback if not bail. Will update with results once done.

from fswatch.

Hi @fatuhoku and @VuongN,

You can try the upcoming fswatch v. 1.0.0 release: you should not receive a change event for the containing directory when a contained file is changed.

Let us know your feedback.

Cheers,
-- Enrico M. Crisostomo

from fswatch.