Skip to content

Conversation

@williamlardier
Copy link
Contributor

This is, especially on the PUT case, consuming CPU for no reason.

Issue: CLDSRV-742

This is, especially on the PUT case, consuming CPU for no reason.

Issue: CLDSRV-742
@bert-e
Copy link
Contributor

bert-e commented Sep 8, 2025

Hello williamlardier,

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 Sep 8, 2025

Incorrect fix version

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

  • None

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

  • 9.1.1

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

@bert-e
Copy link
Contributor

bert-e commented Sep 8, 2025

Waiting for approval

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

  • the author

  • 2 peers

@codecov
Copy link

codecov bot commented Sep 8, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.58%. Comparing base (0a69d1a) to head (36af4db).
⚠️ Report is 5 commits behind head on development/9.1.

Additional details and impacted files

Impacted file tree graph

Files with missing lines Coverage Δ
lib/api/apiUtils/object/objectRestore.js 88.88% <100.00%> (+6.94%) ⬆️
lib/api/objectPut.js 94.59% <100.00%> (ø)
@@                 Coverage Diff                 @@
##           development/9.1    #5937      +/-   ##
===================================================
+ Coverage            83.54%   83.58%   +0.04%     
===================================================
  Files                  190      190              
  Lines                12175    12175              
===================================================
+ Hits                 10171    10176       +5     
+ Misses                2004     1999       -5     
Flag Coverage Δ
ceph-backend-test 64.32% <50.00%> (ø)
file-ft-tests 66.18% <50.00%> (ø)
kmip-ft-tests 26.98% <50.00%> (ø)
mongo-v0-ft-tests 67.99% <50.00%> (ø)
mongo-v1-ft-tests 67.99% <50.00%> (ø)
multiple-backend 34.02% <50.00%> (ø)
sur-tests 34.52% <50.00%> (-0.86%) ⬇️
sur-tests-inflights 36.46% <50.00%> (ø)
unit 68.07% <100.00%> (+0.04%) ⬆️
utapi-v2-tests 33.34% <50.00%> (ø)

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.

@williamlardier williamlardier changed the title Improvement/cldsrv 742 Optimize the error creation for happy paths Sep 8, 2025
@williamlardier
Copy link
Contributor Author

/approve

@bert-e
Copy link
Contributor

bert-e commented Sep 9, 2025

In the queue

The changeset has received all authorizations and has been added to the
relevant queue(s). The queue(s) will be merged in the target development
branch(es) as soon as builds have passed.

The changeset will be merged in:

  • ✔️ development/9.1

The following branches will NOT be impacted:

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

There is no action required on your side. You will be notified here once
the changeset has been merged. In the unlikely event that the changeset
fails permanently on the queue, a member of the admin team will
contact you to help resolve the matter.

IMPORTANT

Please do not attempt to modify this pull request.

  • Any commit you add on the source branch will trigger a new cycle after the
    current queue is merged.
  • Any commit you add on one of the integration branches will be lost.

If you need this pull request to be removed from the queue, please contact a
member of the admin team now.

The following options are set: approve

@bert-e
Copy link
Contributor

bert-e commented Sep 9, 2025

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

  • ✔️ development/9.1

The following branches have NOT changed:

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

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

Goodbye williamlardier.

@bert-e bert-e merged commit 4738e0d into development/9.1 Sep 9, 2025
30 checks passed
@bert-e bert-e deleted the improvement/CLDSRV-742 branch September 9, 2025 08:59
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.

5 participants