Repository navigation
fs.watch() listener called with null filename argument #61520
Description
Activity
- addedsmartosIssues and PRs related to the SmartOS platform.Issues and PRs related to the SmartOS platform.
on Jan 25, 2026 - changed the title
[-]`fs.watch()` listener called with null filename[/-][+]`fs.watch()` listener called with `null` `filename` argument[/+]on Jan 25, 2026 - addedfsIssues and PRs related to file-system APIs and the fs module.Issues and PRs related to file-system APIs and the fs module.
on Jan 25, 2026 Luigi, I know SunOS and FreeBSD are cousins. But I'm not fully sure if they share the same kernel bug. At least FreeBSD has the exact same issue, and it is due to the kernel.
I think the same test passes on FreeBSD? I've opened this as tracking issue for #61494 (comment) and I see no failure on FreeBSD.
I think the same test passes on FreeBSD? I've opened this as tracking issue for #61494 (comment) and I see no failure on FreeBSD.
Don't trust me that much, but is that job actually doing something? https://ci.nodejs.org/job/node-test-commit-freebsd/63310/ I mean, ~5secs... and nothing under "Tests" section".@lpinca See nodejs/build@0cb941b and #54576, FreeBSD is pretty much disabled.
Reacted by Luigi Pinca- addedfreebsdIssues and PRs related to the FreeBSD platform.Issues and PRs related to the FreeBSD platform.
on Jan 26, 2026 github-actions commented
on Jul 20, 2026 on Jul 20, 2026 – with GitHub ActionsContributorMore actionsThis issue has been marked as stale due to 90 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.- addedstaleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.
on Jul 20, 2026 github-actions commented
on Aug 20, 2026 on Aug 20, 2026 – with GitHub ActionsContributorMore actionsThis issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 120 days).
If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.
Version
main (commit 159ae48)
Platform
Subsystem
fs
What steps will reproduce the bug?
How often does it reproduce? Is there a required condition?
Always.
What is the expected behavior? Why is that the expected behavior?
change file.txtis written to the standard output and the process exits. This is what happens when therecursiveoption is set totrue.What do you see instead?
change nullis written to the standard output and the process does not exit.Additional information
No response