René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"fs.watch recursive on Linux emits spurious rename events for sibling files/directories prefixed by related paths on deletion","articleBody":"### Version\n\nv24.2.0 (from archlinux) and v24.1.0 (from nwjs) \n\n### Platform\n\n```text\nLinux ****** 6.15.2-arch1-1 #1 SMP PREEMPT_DYNAMIC Tue, 10 Jun 2025 21:32:33 +0000 x86_64 GNU/Linux\n```\n\n### Subsystem\n\nfs\n\n### What steps will reproduce the bug?\n\n1. open 2 window, prepare test files in the first window:\n```bash\nmkdir -p foo_bar/somedir\ntouch foo_bar/file.txt\nmkdir foo\ntouch foo_\n```\n2. open a node repl in the second window:\n```js\nfs.watch(\".\", { recursive: true }, console.log);\n```\n3. keep the node running, back to the first window:\n```bash\nrmdir foo\n```\nObserved output in the second window:\n```text\nrename foo\nrename foo_\nrename foo_bar\nrename foo_bar/file.txt\nrename foo_bar/somedir\n```\nand then:\n```bash\nrm foo_\n```\nObserved output in the second window:\n```text\nrename foo_\nrename foo_bar\nrename foo_bar/file.txt\nrename foo_bar/somedir\n```\n\n### How often does it reproduce? Is there a required condition?\n\nN/A\n\n### What is the expected behavior? Why is that the expected behavior?\n\nexpected not send the unrelated event(in test case, foo_bar is unchanged, but we got a fake event)\n\n### What do you see instead?\n\n(already attached output in reproduce steps)\n\n![Image](https://github.com/user-attachments/assets/f26d510d-e13f-4db5-9ba6-d5733ecf563f)\n\n### Additional information\n\n_No response_","author":{"url":"https://github.com/Sodium-Aluminate","@type":"Person","name":"Sodium-Aluminate"},"datePublished":"2025-06-27T19:30:27.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/58868/node/issues/58868"}