Skip to content

CLDSRV-863: Checksums for PutObject and UploadPart#6112

Open
leif-scality wants to merge 7 commits intodevelopment/9.4from
improvement/CLDSRV-863-checksums-put-object-part
Open

CLDSRV-863: Checksums for PutObject and UploadPart#6112
leif-scality wants to merge 7 commits intodevelopment/9.4from
improvement/CLDSRV-863-checksums-put-object-part

Conversation

@leif-scality
Copy link
Contributor

No description provided.

@bert-e
Copy link
Contributor

bert-e commented Mar 16, 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 Mar 16, 2026

Incorrect fix version

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

  • None

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

  • 9.4.0

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

@codecov
Copy link

codecov bot commented Mar 16, 2026

❌ 2 Tests Failed:

Tests completed Failed Passed Skipped
8444 2 8442 0
View the full list of 2 ❄️ flaky test(s)
"after each" hook for "should batch delete 1000 objects quietly"::Multi-Object Versioning Delete Success With default signature "after each" hook for "should batch delete 1000 objects quietly"

Flake rate in main: 100.00% (Passed 0 times, Failed 90 times)

Stack Traces | 0.092s run time
The bucket you tried to delete is not empty.
"before each" hook for "should batch delete 1000 objects quietly"::Multi-Object Versioning Delete Success With default signature "before each" hook for "should batch delete 1000 objects quietly"

Flake rate in main: 100.00% (Passed 0 times, Failed 90 times)

Stack Traces | 0.022s run time
read ECONNRESET

To view more test analytics, go to the Test Analytics Dashboard
📋 Got 3 mins? Take this short survey to help us improve Test Analytics.

@claude
Copy link

claude bot commented Mar 16, 2026

LGTM

The checksum pipeline (prepareStream → ChecksumTransform → storeObject validation) is well-structured. The mutable errCb + jsutil.once pattern in storeObject correctly prevents double callbacks across the finish/error race. The defensive err.is && guards in services.js fix a real crash path. Arsenal pinned to tag 8.3.6. Tests cover the key edge cases (chunk boundary splits, trailer parsing, double-callback prevention, batchDelete failures).

Review by Claude Code

_flush(callback) {
Promise.resolve(this.algo.digestFromHash(this.hash))
.then(digest => { this.digest = digest; })
.then(() => callback(), err => {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

prefer using catch for error handling

return callback();
} else if (!this.streamClosed && this.readingTrailer && this.trailerBuffer.length !== 0) {
this.log.error('stream ended without trailer "\r\n"');
return callback(errors.IncompleteBody.customizeDescription(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you could use errorInstances when using customizeDescription to avoid instantiating twice an error

crc64nvme: 'AAAAAAAAAAA=', // 12 chars
};

it('no headers: returns crc64nvme with isTrailer=false and expected=undefined', () => {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

prefer starting tests with should

error: ChecksumError.XAmzMismatch,
details: { algorithm: 'crc32', calculated: 'a', expected: 'b' },
});
assert(result.is.BadDigest);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't like that is helper is tests because if test fails you compare booleans (false != true) instead of names (InternalError != BadDigest), so you don't have much details.

Can we compre on error name with strings ?

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.

3 participants