Cargohold v2.88.0 won't upload objects to s3 because of BadDigest error
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 2.8k
- Forks
- 334
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 50
Description
Describe the bug
After updated to v.2.88.0 Cargohold just won't upload any objects to s3 (I'm using Google Storage, and v.2.87.0 did work for me). After brief research it came out what in v,2.88.0 the following PR has been applied, so it may probably be the reason.
To Reproduce
- Use Google Storage (tbc I haven't tested if it works with AWS S3)
- Upgrade to v2.88.0
- See the bug as described above
Expected behavior
Everything just works
Log file cut
_5-UwRn[REDACTED]VWfX9Sw"),("Content-Type","application/xml; charset=UTF-8"),("Content-Length","262"),("Vary","Origin"),("Date","Wed, 09 Sep 2020 11:41:28 GMT"),("Server","UploadServer")], _serviceCode = ErrorCode "BadDigest", _serviceMessage = Just (ErrorMessage "The MD5 you specified in Content-MD5 or x-goog-hash did not match what we computed."), serviceRequestId = Nothing}),
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Reproduce the upload failure in Cargohold against Google Storage on v2.88.0, compare it with v2.87.0, and inspect the changes from PR 1157 alongside the BadDigest log. Done means objects upload successfully to Google Storage without the MD5 mismatch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- google-cloud, haskell
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100