-
Notifications
You must be signed in to change notification settings - Fork 3.1k
[feat] fs.watch #3249
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
[feat] fs.watch #3249
Conversation
8287dcf
to
8496df3
Compare
❌ @cirospaciari 9 files with test failures on linux-x64:
|
❌ @cirospaciari 8 files with test failures on linux-x64-baseline:
|
❌ @cirospaciari 12 files with test failures on bun-darwin-x64-baseline:
|
5947339
to
c11ca54
Compare
❌ @cirospaciari 10 files with test failures on bun-darwin-aarch64:
|
6ad6e80
to
12f8f87
Compare
✅ |
144c9a5
to
879ffc8
Compare
Today once initialized we never deinit this loop, but we can deinit it when no watchers are active bun/src/bun.js/node/fs_events.zig Lines 541 to 563 in a448078
This implementation is also using babylist to keep track of active stuff and we reuse free slots, not the optimal way but should be fine when using 1-100 watchers bun/src/bun.js/node/fs_events.zig Lines 501 to 508 in a448078
This is the main logic bun/src/bun.js/node/fs_events.zig Lines 355 to 406 in a448078
and we use 1 thread for all watchers and just filter by path like uv does, watcher.zig is using 1 thread per watcher and maybe we can refactor it to do the same as fs_events, relative path logic is also much simpler on fs_events loop. |
a448078
to
ad5cb0a
Compare
🎉 |
No description provided.