You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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), and
(Without the ping, which emulates a sleep on Windows, it works sometimes, and sometimes not.)
Interestingly, the problem is resolved by Ctrl-C'ing node and restarting the above index.js - so events seem to be generated, but chokidar 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)
ifexist output.log del output.log
(for /l %f in () do@echo 1) >> output.log
Continuously write to a new file
(for /l %f in () do@echo 1) > output.log
Create a new file in each loop iteration
for /l %f in () do@echo1> output.log
Append to a file in each loop iteration
for /l %f in () do@echo1>> output.log
chokidar@3.5.3, node v20.8.0, Windows 10 22H2, cmd.exe
The text was updated successfully, but these errors were encountered:
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.
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
chokidar@3.5.3, node v20.8.0, Windows 10 22H2,
cmd.exe
The text was updated successfully, but these errors were encountered: