Conversation
Hello tcarmet,My role is to assist you with the merge of this Available options
Available commands
Status report is not available. |
Incorrect fix versionThe
Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:
Please check the |
Codecov Report❌ Patch coverage is
Additional details and impacted files
... and 3 files with indirect coverage changes @@ Coverage Diff @@
## development/9.3 #6233 +/- ##
===================================================
+ Coverage 85.28% 85.33% +0.05%
===================================================
Files 206 206
Lines 13435 13442 +7
===================================================
+ Hits 11458 11471 +13
+ Misses 1977 1971 -6
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
|
/create_integration_branches |
ConflictA conflict has been raised during the creation of I have not created the integration branch. Here are the steps to resolve this conflict: git fetch
git checkout -B w/9.4/bugfix/CLDSRV-909-enforce-copyobject-source-size-limit origin/development/9.4
git merge origin/bugfix/CLDSRV-909-enforce-copyobject-source-size-limit
# <intense conflict resolution>
git commit
git push -u origin w/9.4/bugfix/CLDSRV-909-enforce-copyobject-source-size-limitThe following options are set: create_integration_branches |
6ef6cf5 to
654b065
Compare
Incorrect fix versionThe
Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:
Please check the The following options are set: create_integration_branches |
ConflictA conflict has been raised during the creation of I have not created the integration branch. Here are the steps to resolve this conflict: git fetch
git checkout -B w/9.5/bugfix/CLDSRV-909-enforce-copyobject-source-size-limit origin/development/9.5
git merge origin/w/9.4/bugfix/CLDSRV-909-enforce-copyobject-source-size-limit
# <intense conflict resolution>
git commit
git push -u origin w/9.5/bugfix/CLDSRV-909-enforce-copyobject-source-size-limitThe following options are set: create_integration_branches |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
The following options are set: create_integration_branches |
|
/approve |
|
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
This pull request did not target the following hotfix branch(es) so they
Please check the status of the associated issue CLDSRV-909. Goodbye tcarmet. The following options are set: approve, create_integration_branches |
4 participants
Backport of #6177 to
development/9.3.Align cloudserver's CopyObject with the AWS S3 contract by rejecting requests whose source object exceeds 5 GiB. AWS S3 returns HTTP 400
InvalidRequest("The specified copy source is larger than the maximum allowable size for a copy source: 5368709120") and expects clients to use the multipart copy flow instead; cloudserver previously accepted these requests. ThebypassMaxPutObjectSizeflag still overrides the limit, matching the PutObject behavior.The first commit is a prettier-only reformat of the two touched files and can be skipped during review; the actual change lives in the three cherry-picked commits.