Fix the ScanFiles job to not trigger scans of root directory for every single user #61511
Conversation
2efa616 to
9592cdb
Compare
|
/backport to stable34 |
|
/backport to stable33 |
|
/backport to stable32 |
Signed-off-by: Akhil <akhil@e.email>
9592cdb to
72f63dd
Compare
|
@akhil1508 please don't update the branch, unless there are actual conflicts. This requires us to re-approve and restart CI, resulting in delays for merging the PR. |
@provokateurin got it, apologies! |
|
Hello there, We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process. Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6 Thank you for contributing to Nextcloud and we hope to hear from you soon! (If you believe you should not receive this message, you can add yourself to the blocklist.) |
Summary
''is passedgetMountsreturnshome::usernameandlocal:/var/www/datamounts and both of these get scannedocc files:scan username --unscannedand there the path resolves to/usernameand not''TODO
Checklist
3. to review, feature component)stable32)AI (if applicable)