-
-
Notifications
You must be signed in to change notification settings - Fork 564
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Change event is not emitted on Windows when continuously appending to an initially existing file #1297
Comments
Two more notes:
This is not supposed to mean that |
I experienced something similiar. I've got a dockerized environment running on windows, that uses chokidar to watch for file changes. The events don't trigger on the dockerized environment, causing updates not to flow through. Using |
I see the same thing as #999 on Windows. Essentially, I get only one or two (initial/final) change events for a file despite continuously appending to it. I see the same kind of issues in real life, e.g., VS Code auto-updates of output from https://github.com/pkolaczk/fclones on Windows are stalled until re-focusing VS Code (compare microsoft/vscode#93277).
To reproduce, I used the same code for
index.js
as #999 (comment), andContinuously append to an existing file
(Without the
ping
, which emulates asleep
on Windows, it works sometimes, and sometimes not.)Interestingly, the problem is resolved by Ctrl-C'ing
node
and restarting the aboveindex.js
- so events seem to be generated, butchokidar
seems to choke on them somehow.Also, the issue does not reproduce with either of the following variants:
Continuously append to an initially missing file (hence creating it first)
Continuously write to a new file
Create a new file in each loop iteration
Append to a file in each loop iteration
[email protected], node v20.8.0, Windows 10 22H2,
cmd.exe
The text was updated successfully, but these errors were encountered: