-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
Fix a bug with smb notify having leading slash when it should not #14456
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
Conversation
Signed-off-by: Ari Selseng <[email protected]>
|
/backport to stable15 |
|
/backport to stable14 |
|
Thanks for your first pull request and welcome to the community! Feel free to keep them coming! If you are looking for issues to tackle then have a look at this selection: https://github.com/nextcloud/server/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22 |
|
backport to stable15 in #14462 |
|
/backport to stable14 |
|
@rullzer Did the bot just died? |
|
/backport to stable14 |
|
I found the branch of the bot, but there was no PR - so here it is: #14866 (stable14 back port) |
@icewind1991
My SMB server with occ files_external:notify 1 -vvv reported paths like
The path for the entry in the oc_filecache table had no leading slash ("Temp/test/test123.txt") and its parent too. Which means that the parent never got updated with size = -1. This should fix some (all?) smb notify issues.