fix(user): invalidate folder ETag when quota changes#59398
Open
fix(user): invalidate folder ETag when quota changes#59398
Conversation
solracsf
changed the title
solracsf
force-pushed
the
invalidateRootETag
branch
from
979c4ed to
eb5bc3e
Compare
solracsf
requested review from
Altahrim,
ArtificialOwl,
icewind1991 and
leftybournes
and removed request for
a team
This was referenced Apr 2, 2026
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
solracsf
force-pushed
the
invalidateRootETag
branch
2 times, most recently
from
ce17b6a to
5662683
Compare
solracsf
changed the title
Signed-off-by: Git'Fellow <12234510+solracsf@users.noreply.github.com>
solracsf
force-pushed
the
invalidateRootETag
branch
from
5662683 to
3aea2ac
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
2 participants
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.
Summary
When an admin changes a user's quota (via the admin UI, provisioning API, or CLI), desktop sync clients continue using the stale
quota-available-bytesvalue from their last PROPFIND until the etag of the user's home folder changes.This PR invalidates the etag entry whenever
setQuota()persists a new quota value, forcing clients to re-fetch on their next sync cycle.Checklist
3. to review, feature component)stable32)AI (if applicable)