CLDSRV-872: store checksum in object metadata#6114
CLDSRV-872: store checksum in object metadata#6114leif-scality wants to merge 10 commits intoimprovement/CLDSRV-863-checksums-put-object-partfrom
Conversation
Hello leif-scality,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 |
❌ 2 Tests Failed:
View the top 2 failed test(s) by shortest run time
To view more test analytics, go to the Test Analytics Dashboard |
Review by Claude Code |
5d6c434 to
1b5a063
Compare
|
Review summary: (1) Arsenal dependency pinned to a branch instead of a tag - must update to a released tag. (2) checkHashMatchMD5 JSDoc missing the new checksumStream parameter. (3) dataStore callback returns a 4th checksum arg but objectPutPart and routeBackbeat callers ignore it. -- Review by Claude Code |
1b5a063 to
b80b2ad
Compare
|
|
|
Review by Claude Code |
Review by Claude Code |
Review by Claude Code |
a284c9f to
dade07b
Compare
180d940 to
7d130cc
Compare
|
7d130cc to
8e51413
Compare
|
LGTM |
| await s3.send(new DeleteBucketCommand({ Bucket: bucket })); | ||
| }); | ||
|
|
||
| it('stores sha256 checksum in metadata when x-amz-checksum-sha256 is provided', done => { |
There was a problem hiding this comment.
prefer starting with should
| assert.strictEqual(res.headers['x-amz-checksum-crc64nvme'], crc64nvmeOfTestContent2, | ||
| `expected x-amz-checksum-crc64nvme: ${crc64nvmeOfTestContent2}`); | ||
| } | ||
| done(); |
There was a problem hiding this comment.
Should we fail this test if the checksum header is absent?
| crc32c: 'AAAAAA==', | ||
| sha1: '2jmj7l5rSw0yVb/vlWAYkK/YBwk=', | ||
| sha256: '47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=', | ||
| crc64nvme: null, // filled in before hook (async) |
There was a problem hiding this comment.
nit: Not sure why we're not writing this one down as well
No description provided.