Uh oh!
There was an error while loading. Please reload this page.
fix(S3): Use original folder size during copy - #52242
Conversation
artonge
commented
Apr 17, 2025
/backport to stable31 |
artonge
commented
Apr 17, 2025
/backport to stable30 |
artonge
commented
Apr 17, 2025
/backport to stable29 |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
icewind1991
commented
Apr 30, 2025
The least-invasive change would probably be to pass the needed metadata to Alternatively you can first do the recursive cache copy, and then do the object copy recursively without changing the cache. (care has to be taken than to not have the db and object store desync if the object copy fails then) |
DaphneMuller
commented
May 14, 2025
@artonge anything that we should be doing here to follow up on it? |
artonge
commented
May 14, 2025
No, just prioritizing :) |
❌ Unsupported file format
|
4fb8346 to
104b0c3Compare104b0c3 to
5305b24Comparef0a41af to
45e7407Compareartonge
commented
May 19, 2025
@icewind1991 I ended up keeping the |
45e7407 to
fa2ed6bCompareDaphneMuller
commented
May 27, 2025
@artonge@icewind1991 any chance this can be merged soon? |
icewind1991
commented
May 27, 2025
Pushed a change to do the size in the Also pushed a test to ensure this doesn't regress. |
This prevent having copied folders with a wrongly set size of 0KB. - Fix#51916 Signed-off-by: Louis Chemineau <louis@chmn.me>
Signed-off-by: Robin Appelman <robin@icewind.nl>
Signed-off-by: Robin Appelman <robin@icewind.nl>
d4378de to
e21ce79Compare
This prevents having copied folders with a wrongly set size of 0KB.
Not sure about theValidated.handleCopiesAsOwnedpart, but I kept it fromcopyFileto preserve the same behaviour. It was introduced in #41565. Maybe @susnux you can judge whether it makes sense or not.