Skip to content

Conversation

@leif-scality
Copy link
Contributor

No description provided.

@bert-e
Copy link
Contributor

bert-e commented Feb 9, 2026

Hello leif-scality,

My role is to assist you with the merge of this
pull request. Please type @bert-e help to get information
on this process, or consult the user documentation.

Available options
name description privileged authored
/after_pull_request Wait for the given pull request id to be merged before continuing with the current one.
/bypass_author_approval Bypass the pull request author's approval
/bypass_build_status Bypass the build and test status
/bypass_commit_size Bypass the check on the size of the changeset TBA
/bypass_incompatible_branch Bypass the check on the source branch prefix
/bypass_jira_check Bypass the Jira issue check
/bypass_peer_approval Bypass the pull request peers' approval
/bypass_leader_approval Bypass the pull request leaders' approval
/approve Instruct Bert-E that the author has approved the pull request. ✍️
/create_pull_requests Allow the creation of integration pull requests.
/create_integration_branches Allow the creation of integration branches.
/no_octopus Prevent Wall-E from doing any octopus merge and use multiple consecutive merge instead
/unanimity Change review acceptance criteria from one reviewer at least to all reviewers
/wait Instruct Bert-E not to run until further notice.
Available commands
name description privileged
/help Print Bert-E's manual in the pull request.
/status Print Bert-E's current status in the pull request TBA
/clear Remove all comments from Bert-E from the history TBA
/retry Re-start a fresh build TBA
/build Re-start a fresh build TBA
/force_reset Delete integration branches & pull requests, and restart merge process from the beginning.
/reset Try to remove integration branches unless there are commits on them which do not appear on the source branch.

Status report is not available.

@bert-e
Copy link
Contributor

bert-e commented Feb 9, 2026

Incorrect fix version

The Fix Version/s in issue CLDSRV-847 contains:

  • None

Considering where you are trying to merge, I ignored possible hotfix versions and I expected to find:

  • 9.2.26

  • 9.3.2

Please check the Fix Version/s of CLDSRV-847, or the target
branch of this pull request.

@codecov
Copy link

codecov bot commented Feb 9, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.17%. Comparing base (ed693c7) to head (795f089).
⚠️ Report is 3 commits behind head on development/9.2.
✅ All tests successful. No failed tests found.

Additional details and impacted files

Impacted file tree graph
see 3 files with indirect coverage changes

@@                 Coverage Diff                 @@
##           development/9.2    #6078      +/-   ##
===================================================
- Coverage            84.18%   84.17%   -0.01%     
===================================================
  Files                  204      204              
  Lines                13124    13124              
===================================================
- Hits                 11048    11047       -1     
- Misses                2076     2077       +1     
Flag Coverage Δ
file-ft-tests 67.62% <ø> (ø)
kmip-ft-tests 28.19% <ø> (ø)
mongo-v0-ft-tests 68.86% <ø> (+0.02%) ⬆️
mongo-v1-ft-tests 68.85% <ø> (ø)
multiple-backend 35.24% <ø> (ø)
sur-tests 35.78% <ø> (-0.81%) ⬇️
sur-tests-inflights 37.63% <ø> (ø)
unit 69.71% <ø> (ø)
utapi-v2-tests 34.50% <ø> (-0.04%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@leif-scality leif-scality force-pushed the bugfix/CLDSRV-847-dont-require-x-amz-content-sha256-to-be-signed branch 2 times, most recently from 424c235 to 1fd2321 Compare February 10, 2026 12:22
@leif-scality leif-scality changed the title CLDSRV-847: bump arsenal version CLDSRV-847: don't require x-amz-content-sha256 to be signed Feb 10, 2026
@leif-scality leif-scality force-pushed the bugfix/CLDSRV-847-dont-require-x-amz-content-sha256-to-be-signed branch from 1fd2321 to 795f089 Compare February 11, 2026 11:23
@leif-scality
Copy link
Contributor Author

ping

@bert-e
Copy link
Contributor

bert-e commented Feb 11, 2026

Request integration branches

Waiting for integration branch creation to be requested by the user.

To request integration branches, please comment on this pull request with the following command:

/create_integration_branches

Alternatively, the /approve and /create_pull_requests commands will automatically
create the integration branches.

@leif-scality
Copy link
Contributor Author

/create_integration_branches

@bert-e
Copy link
Contributor

bert-e commented Feb 11, 2026

Conflict

A conflict has been raised during the creation of
integration branch w/9.3/bugfix/CLDSRV-847-dont-require-x-amz-content-sha256-to-be-signed with contents from bugfix/CLDSRV-847-dont-require-x-amz-content-sha256-to-be-signed
and development/9.3.

I have not created the integration branch.

Here are the steps to resolve this conflict:

 git fetch
 git checkout -B w/9.3/bugfix/CLDSRV-847-dont-require-x-amz-content-sha256-to-be-signed origin/development/9.3
 git merge origin/bugfix/CLDSRV-847-dont-require-x-amz-content-sha256-to-be-signed
 # <intense conflict resolution>
 git commit
 git push -u origin w/9.3/bugfix/CLDSRV-847-dont-require-x-amz-content-sha256-to-be-signed

The following options are set: create_integration_branches

@leif-scality
Copy link
Contributor Author

ping

@bert-e
Copy link
Contributor

bert-e commented Feb 11, 2026

Waiting for approval

The following approvals are needed before I can proceed with the merge:

  • the author

  • 2 peers

The following options are set: create_integration_branches

@leif-scality
Copy link
Contributor Author

/approve

@bert-e
Copy link
Contributor

bert-e commented Feb 11, 2026

I have successfully merged the changeset of this pull request
into targetted development branches:

  • ✔️ development/9.2

  • ✔️ development/9.3

The following branches have NOT changed:

  • development/7.10
  • development/7.4
  • development/7.70
  • development/8.8
  • development/9.0
  • development/9.1

Please check the status of the associated issue CLDSRV-847.

Goodbye leif-scality.

The following options are set: approve, create_integration_branches

@bert-e bert-e merged commit 795f089 into development/9.2 Feb 11, 2026
29 checks passed
@bert-e bert-e deleted the bugfix/CLDSRV-847-dont-require-x-amz-content-sha256-to-be-signed branch February 11, 2026 15:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants