We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
rustc --version
rustc 1.75.0-nightly (0f44eb32f 2023-11-09)
I have a directory structure similar to the following:
- root | - common | | - file.json | - tests | | - test_1 | | | - common -> ../../common
We put a recursive watch on root, and then modify root/common/file.json.
root
root/common/file.json
Either one of:
root/tests/test_1/common/file.json
Only a notify event is fired for root/tests/test_1/common/file.json.
The text was updated successfully, but these errors were encountered:
Relates to #255, #291, and #381, but seems distinct.
Reading https://docs.rs/inotify/latest/inotify/struct.Watches.html#attention-updating-watches-and-hardlinks, possibly the easiest way to solve this behavior is to keep a list of paths for each WatchDescriptor and add to that list at- https://github.com/notify-rs/notify/blob/main/notify/src/inotify.rs#L454.
WatchDescriptor
Sorry, something went wrong.
Support watching the same inode through multiple paths.
8a74886
As a single change event can now refer to multiple paths, use "path groups" for renames to differentiate sources and destinations. Fixes notify-rs#572.
Successfully merging a pull request may close this issue.
System details
rustc --version
:rustc 1.75.0-nightly (0f44eb32f 2023-11-09)
What you did (as detailed as you can)
I have a directory structure similar to the following:
We put a recursive watch on
root
, and then modifyroot/common/file.json
.What you expected
Either one of:
root/common/file.json
androot/tests/test_1/common/file.json
.root/common/file.json
What happened
Only a notify event is fired for
root/tests/test_1/common/file.json
.The text was updated successfully, but these errors were encountered: