Conversation
c440368 to
b17f1e8
Compare
b17f1e8 to
2e1669b
Compare
This comment was marked as resolved.
This comment was marked as resolved.
|
/backport to stable33 |
|
/backport to stable32 |
|
/backport to stable31 |
|
Make sense to me |
|
@solracsf I was investigating this issue as well, and what you did makes a lot of sense to me. Unfortunately, when testing the Toast (feedback): Request: Response: Does this happen for you as well? Other than that, adding/removing files from within a shared folder correctly updated the folder etag in my tests. I verified this using curl as suggested in issue #57973, and running the command before and after the file operation confirmed the etag updated and matched the value in the curl -X PROPFIND -u "{user}:{pass}" \
-H "Depth: 0" \
"https://{server}/remote.php/dav/files/{user}/{team_shared_folder}/" \
--data '<?xml version="1.0"?><d:propfind xmlns:d="DAV:"><d:prop><d:getetag/></d:prop></d:propfind>' |
|
@cristianscheid try latest commit a7baf35 on your patched instance Tested locally, rename works as expected. |
@solracsf Thanks for the adjustment! I tested locally again using curl before and after renaming a file, and it worked as expected. |
|
Thanks for testing. |
|
btw the red psalm ci is fixed by #2356 in case anyone wants to review ;) |
|
@solracsf please rebase |
Signed-off-by: Git'Fellow <12234510+solracsf@users.noreply.github.com>
a7baf35 to
1cdb52d
Compare
Signed-off-by: Git'Fellow <12234510+solracsf@users.noreply.github.com>
|
@provokateurin rebased and all green 🟢 |
|
/backport 1cdb52d to stable33 |
|
/backport 1cdb52d to stable32 |
|
/backport 1cdb52d to stable31 |
Problem
Context: nextcloud/server#57973 and nextcloud/server#49126
Files shared with teams were not syncing properly on desktop clients. When files were added, modified, or deleted in team-shared directories, the ETag was correctly updated in the database but clients received stale ETags from the distributed cache, preventing synchronization.
Root causes:
clearCache()method inShareWrapperServicewas broken - it usedsingleIdas the cache key but actual keys follow the formatsingleId#nodeId#probeSum, causing cache invalidation to silently failFix nextcloud/server#57973
Note
While testing, please enable
debugmode to print debug messages.