-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
BugFix - Use eTag for Thumbnail Generation #14513
base: master
Are you sure you want to change the base?
Conversation
/backport to stable-3.31 |
I think we need to discuss this approach.
|
Exactly. In that case, it will regenerate the thumbnail. We can evaluate the pros and cons of this approach. If the advantages outweigh the disadvantages, we can proceed with this method. Alternatively, we can try to find a more distinct and reliable solution, maybe using a combination of |
Signed-off-by: alperozturk <[email protected]>
Signed-off-by: alperozturk <[email protected]>
Signed-off-by: alperozturk <[email protected]>
Signed-off-by: alperozturk <[email protected]>
2756f39
to
6fb4f57
Compare
APK file: https://www.kaminsky.me/nc-dev/android-artifacts/14513.apk |
blue-Light-Screenshot test failed: https://www.kaminsky.me/nc-dev/android-integrationTests/14513-Screenshot-blue-Light-12-56 |
The
OCFile
remoteId
is currently being used as theimageKey
for thumbnail generation. This approach prevents the correct regeneration of thumbnails when a user uploads a different file with the same filename and extension.Example:
remoteId
remains unchanged, even though theeTag
has been updated.Proposed Solution:
To ensure proper thumbnail generation, the
eTag
should be used as theimageKey
instead of theremoteId
.Known Issues:
The
ConflictResolveDialog
is currently unable to display thumbnails correctly in both the master branch and this PR. This issue will be addressed separately in a future PR.Before
befd.mp4
After
after_generation.mp4