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

Not triggered for git checkout #72

Open
michalrus opened this issue Dec 30, 2017 · 1 comment
Open

Not triggered for git checkout #72

michalrus opened this issue Dec 30, 2017 · 1 comment
Labels

Comments

@michalrus
Copy link

This issue probably belongs to this repo:

schell/steeloverseer#28

We have an automated /bin/sh test case there, which you can run.

What could be the reason for this behavior?

Thanks a lot!

@typesanitizer
Copy link

typesanitizer commented Feb 10, 2019

Think I'm encountering a bug where setting a debouncing interval manually leads to only the very first event being detected, and everything else in the future is discarded. You might be seeing the same issue because you're also setting the debounce time to a custom value here

    config = FSNotify.defaultConfig
      { FSNotify.confDebounce = FSNotify.Debounce 0.1 }

EDIT: Never mind, false alarm.

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

No branches or pull requests

3 participants