node-inotify needs to use another way to save the callbacks other than the watch file descriptor as key
Open
- Dominant language
- C++
- Stars
- 242
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Description
node-inotify needs to use another way to save the callbacks other than the watch file descriptor as key. When you make a removeWatch and a subsequent addWatch, inotify is using the same watch descriptor which is problematic because when the last event of the removed watch arrive, the callback deleted belongs to the new addWatch which is completely wrong !
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.