-
Notifications
You must be signed in to change notification settings - Fork 250
fix: INotifyWatcher may raise events with no paths #700
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
Conversation
INotifyWatcher hold inotify watch descriptors map `wd -> path` and after an `unwatch` call the descriptor is deleted from the map. In some cases, if a lot of events are raised, it may cause race condition when the descriptor has been deleted, but event with this descriptor has already been queued. In that case INotifyWatcher doesn't know the path and just ignore the event fixes notify-rs#678
|
In this PR I also have moved |
|
Thanks, @riberk. This looks very good. I can merge it now, or you can fix the typo first. Your call. |
Done, thanks for the fix |
|
Fantastic. Thanks again! |
|
@riberk I think this would be a good time to make a new release - unless you are working on something else. |
|
@dfaust it'd be good, but I don't know how I can help |
|
I will make the release. Just wanted to make sure I don't release while you are still working on something. I'll wait with the release until my latest MR is merged as well, though. |
|
Ah, now I see it. Right now I'm not working on anything |
INotifyWatcher hold inotify watch descriptors map
wd -> pathand after anunwatchcall the descriptor is deleted from the map. In some cases, if a lot of events are raised, it may cause race condition when the descriptor has been deleted, but event with this descriptor has already been queued. In that case INotifyWatcher doesn't know the path and just ignore the eventfixes #678