-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Include option to allow scanner to reuse etags only for files #37218
Conversation
This option will be used by the watcher, in case it detects a change in a folder, so the etag of the folder will always change (not just depending on mtime) but the contents might retain its current etag.
Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes. |
Codecov Report
@@ Coverage Diff @@
## master #37218 +/- ##
=========================================
Coverage 64.87% 64.88%
- Complexity 19146 19151 +5
=========================================
Files 1269 1269
Lines 74947 74950 +3
Branches 1331 1331
=========================================
+ Hits 48625 48628 +3
Misses 25930 25930
Partials 392 392
Continue to review full report at Codecov.
|
@pmaier1 I'll need confirmation whether this PR will be in 10.4.1 or 10.5.0. Changelog entry to be added after confirmation. |
#37170 should be fixed with this PR. The target use case is the same. |
@jvillafanez @mmattel I have doubts for 10.4.1. It touches a central part of core (etag propagation) I would like to avoid the testing effort now. 10.4.1 should be out 1-2 days. This would delay other important fixes. IMO waiting for a fix of Gdrive external storage compared to a very urgent bugfix of password_policy is an easy decision. @pmaier1 @HanaGemela open for your input. |
I wouldn't delay 10.4.1 |
10.4.1 is closed and should not be delayed by this. THX! |
@jvillafanez I think we might have similar issue with fed shares. I noticed that browsing in UI also mixes etag propagation. Try to verify this scenario:
|
@mrow4a it would be a good idea to create a new issue so we can track it. |
@mmattel ignore it for now, external storages are working a bit differently than shared external storages. if we get similar issue, maybe this would be good hint for someone. |
The scanner's update method will reuse the size if possible. REUSE_ONLY_FOR_FILES flag will only be applicable to etag, not size Links to #37218
The scanner's update method will reuse the size if possible. REUSE_ONLY_FOR_FILES flag will only be applicable to etag, not size Links to #37218
The scanner's update method will reuse the size if possible. REUSE_ONLY_FOR_FILES flag will only be applicable to etag, not size Links to #37218
This option will be used by the watcher, in case it detects a change in
a folder, so the etag of the folder will always change (not just
depending on mtime) but the contents might retain its current etag.
Description
Changes in gdrive weren't being propagated properly because the mtime of the folder doesn't change when a file is added / removed / modified there.
The etag of the folder didn't change, so the desktop client loses track of where to look for changes once it reaches the modified folder. This means that the new files inside the folder don't appear in the desktop (files aren't removed neither)
Note that the mtime of the folder in ownCloud still be the same as the one reported by gdrive
Related Issue
owncloud/client#7837 (comment)
Motivation and Context
gdrive integration don't behave like other external storages from a desktop client's perspective otherwise.
How Has This Been Tested?
Manually checked:
Screenshots (if appropriate):
Types of changes
Checklist: