We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cloudpathlib expects all s3 objects to have a content type, however this is not always the case as content-type is not a required field and is part of the objects optional metadata. Please review https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingMetadata.html#object-metadata
content-type
Please review the below code: https://github.com/drivendataorg/cloudpathlib/blob/28b2eb5dbba3ba5477284e1b432ac723f1a87f1b/cloudpathlib/s3/s3client.py#LL145C9-L145C49
This will result in a KeyError on that specific line.
KeyError
From what I have seen, the content type is not even used by cloudpathlib, so my vote would be to ditch it.
The text was updated successfully, but these errors were encountered:
Allow empty content type for s3 objects
ec0cf5d
Fixes drivendataorg#331
Allow empty content type for s3 objects (#332)
557456e
* Allow empty content type for s3 objects Fixes #331 * Update s3client.py
Successfully merging a pull request may close this issue.
Cloudpathlib expects all s3 objects to have a content type, however this is not always the case as
content-type
is not a required field and is part of the objects optional metadata. Please review https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingMetadata.html#object-metadataPlease review the below code:
https://github.com/drivendataorg/cloudpathlib/blob/28b2eb5dbba3ba5477284e1b432ac723f1a87f1b/cloudpathlib/s3/s3client.py#LL145C9-L145C49
This will result in a
KeyError
on that specific line.From what I have seen, the content type is not even used by cloudpathlib, so my vote would be to ditch it.
The text was updated successfully, but these errors were encountered: