Wrong watch descriptor inside IN_DELETE_SELF
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- cpp, linux, node.js
- Domain
- operating-systems
Research direction
Start by locating the C++ binding code that translates Linux inotify events, then trace how IN_DELETE_SELF and IN_DELETE expose their watch descriptors. Compare the event data for a deleted directory with its parent-directory watch, and add a regression test if the repository has an existing event-test pattern. Done means IN_DELETE_SELF reports the descriptor for the deleted directory rather than duplicating IN_DELETE.
Written by the indexing model from the issue text.
Description
It looks like this event's object holds the watch descriptor associated with the parent directory, not for the directory that was just deleted. Basically it returns the same data as IN_DELETE
- 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 ·