watcher
watcher copied to clipboard
Checksum check to ensure the file has actually changed.
Hi! I was wondering if this was on the roadmap, or actively avoided? I am having issues where it seems like users may have other tools running that would touch timestamps and cause a burst in events for reference. I figured the best way to mitigate this was by checking to make sure the contents actually changed.
We could keep track of checksums at startup and then compare them if timestamps have changed here: https://github.com/radovskyb/watcher/blob/master/watcher.go#L635
I think that would help weed out duplicate/redundant events as well. I can understand if there is a performance concern, however, it is possible that it is a feature we could enable. Let me know your thoughts and I think I can put some time toward implementing it if it is something you would be interested in.