node-inotify needs to use another way to save the callbacks other than the watch file descriptor as key
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- cpp, linux, node.js
- Domain
- operating-systems
Research direction
Trace the watch bookkeeping used by removeWatch and addWatch, focusing on how callbacks are keyed by the inotify watch descriptor. Reproduce the remove-then-add sequence and inspect the handling of a late event from the removed watch. Done means the late event cannot remove or invoke the callback belonging to the replacement watch.
Written by the indexing model from the issue text.
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 !
- Dominant language
- C++
- Stars
- 242
- Forks
- 39
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from c4milo/node-inotify
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
c4milo/node-inotify#80 · 1 reaction ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
c4milo/node-inotify#79 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
c4milo/node-inotify#78 · 4 comments · 5 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
c4milo/node-inotify#75 · 21 comments · 3 reactions ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
c4milo/node-inotify#74 · 1 reaction ·
All issues in c4milo/node-inotify
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
ros2/message_filters#338 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
subsurface/subsurface#4984 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
flutter-webrtc/flutter-webrtc#2206 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
google-ai-edge/LiteRT-LM#3739 ·