You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix(s3frontend): conformance-align multipart validation; abort in-flight uploads on DeleteBucket
Three upstream conformance cases return to the pass tables with
behavior fixes instead of xfail rows:
- CompleteMultipartUpload: a part entry missing PartNumber or ETag is
MalformedXML, and a part number below 1 is InvalidArgument
(PartNumber), mirroring versitygw's posix backend; the ETag match is
now mandatory and the >10000 special case folds into the membership
check (InvalidPart).
- ListMultipartUploads: upload-id-marker validation mirrors upstream's
MultipartUploadLister — the marker must be a valid UUID naming an
upload of the first key group at/after the key marker (else
InvalidArgument, upload-id-marker), and listing resumes past it.
DeleteBucket now implicitly aborts the bucket's open multipart sessions
(upstream's teardown never aborts them and expects the delete to
succeed), releasing their parked part blobs before the hilt space
delete. CompleteMultipartUpload_conditional_writes stays xfail: its
conditional matrix passes, but the implicit abort's /blob/abort goes
out proofless — hilt's per-operation grants carry blob.Abort for the
S3 Abort operation only. Promote once hilt's s3perm map grants
blob.Abort on bucket delete.
Validated: full local TestForgeVersity, 219 pass / 0 fail.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
0 commit comments