Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Checksum check to ensure the file has actually changed. #77

Open
tanema opened this issue Jul 31, 2019 · 0 comments
Open

Checksum check to ensure the file has actually changed. #77

tanema opened this issue Jul 31, 2019 · 0 comments

Comments

@tanema
Copy link

tanema commented Jul 31, 2019

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant