-
Notifications
You must be signed in to change notification settings - Fork 229
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
Report which sub-path failed when adding a Recursive watch and a subfolder has a permission (or other) error #353
Labels
Comments
Heyho, yeah I suppose we'll need to fix this in here for inotify, but from my understanding we can't fix this correctly on windows, as recursive flags are handled by the windows API, so we don't have any context what we failed to watch. Will also have to look into the BSD and darwin implementation. |
I've done it for inotify, will PR. Looking into kqueue now. |
Ah that is fast :) |
|
passcod
added a commit
that referenced
this issue
Aug 22, 2021
passcod
added a commit
that referenced
this issue
Aug 22, 2021
passcod
added a commit
that referenced
this issue
Aug 22, 2021
0xpr03
pushed a commit
that referenced
this issue
Aug 22, 2021
0xpr03
pushed a commit
that referenced
this issue
Aug 22, 2021
0xpr03
pushed a commit
that referenced
this issue
Aug 22, 2021
77 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
System details
rustc --version
: 1.54.0What you did (as detailed as you can)
This directory structure:
folder1
(owned by user)folder2
(owned by user)folder3
(owner by root)What you expected
For the second
watch()
to error when recursing forfolder3
and theError
'spaths
field to be["folder2/folder3"]
.What happened
The second
watch()
errors, but the error has an emptypaths
field:Also, very love what you've done with Notify, looking forward to the stable 5.0 release! ❤️
The text was updated successfully, but these errors were encountered: