fix(quota): Invalidate root ETag on quota change#4539
Open
fix(quota): Invalidate root ETag on quota change#4539
Conversation
362319d to
08a628e
Compare
Signed-off-by: Git'Fellow <12234510+solracsf@users.noreply.github.com>
fda82bd to
9086a48
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When the quota of a team folder changes, desktop clients continued to receive the stale
quota-available-bytesvalue on subsequent PROPFINDs until theetagof the folder root changed. This fix invalidates the root etag immediately after the quota is updated, without requiring a mounted storage or an active user session.This forces every desktop client to issue a fresh PROPFIND on the next sync cycle, at which point the DAV layer computes and returns the updated
quota-available-bytesvalue.Server side: nextcloud/server#59398
Needed for nextcloud/desktop#4580