-
Notifications
You must be signed in to change notification settings - Fork 183
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
fatal error: sync: unlock of unlocked mutex #121
Comments
Found a solution. Triggered the bug with this
I found another occation created a slightly different error message which helped to identify the real issue:
And this is the fix:
I'm not sure what this code does exactly and if my fix is correct but at least for me the watcher is now working according to specification! |
qknight
added a commit
to qknight/watcher
that referenced
this issue
Jul 12, 2023
qknight
added a commit
to qknight/watcher
that referenced
this issue
Jul 12, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
A clear and concise description of what the bug is.
I changed a file which was observed by fsNotify and then the error occured:
https://github.com/nixcloud/pankat/blob/future/cmd/pankat-server/fsNotify.go#L63
To Reproduce
Expected behavior
No crash, fsNotify just pointing out what files changed. This works very often, but sometimes crashes.
Which operating system and version are you using?
https://github.com/radovskyb/watcher#example
The text was updated successfully, but these errors were encountered: