S3Client: Fix ETag KeyError when HeadObject omits ETag - #583
Merged
pjbull merged 2 commits intoAug 22, 2026
Merged
Conversation
Fix KeyError in S3Client._get_metadata when HeadObject response is missing the optional ETag property. An example S3 server omitting ETag is versitygw when serving existing POSIX backends without metadata.
srstsavage
force-pushed
the
cloudpathlib-582-allow-headobject-missing-etag
branch
from
August 21, 2026 05:47
00787db to
f10ec01
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix KeyError in S3Client._get_metadata when HeadObject response is missing the optional ETag property.
An example S3 server omitting ETag is versitygw when serving existing POSIX backends without metadata.
Closes #582
Contributor checklist:
CONTRIBUTING.mdCloses #issueappears in the PR summary (e.g.,Closes #123).HISTORY.mdwith the issue that is addressed and the PR you are submitting. If the top section is not `## UNRELEASED``, then you need to add a new section to the top of the document for your change.