-
-
Couldn't load subscription status.
- Fork 4.6k
fix(S3): Use original folder size during copy #52242
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
Conversation
|
/backport to stable31 |
|
/backport to stable30 |
|
/backport to stable29 |
|
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) |
|
@artonge anything that we should be doing here to follow up on it? |
No, just prioritizing :) |
❌ Unsupported file format
|
4fb8346 to
104b0c3
Compare
104b0c3 to
5305b24
Compare
f0a41af to
45e7407
Compare
@icewind1991 I ended up keeping the |
45e7407 to
fa2ed6b
Compare
|
@artonge @icewind1991 any chance this can be merged soon? |
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
e21ce79
Compare
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.