Cargohold v2.88.0 won't upload objects to s3 because of BadDigest error
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
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.
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}),
- Dominant language
- Haskell
- Stars
- 2.8k
- Forks
- 332
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 49
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
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.
More from wireapp/wire-server
-
Difficulty 1/5 Under an hour Newbie friendliness 83/100
wireapp/wire-server#5632 ·
Maintainers usually reply within 2 days
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
wireapp/wire-server#5443 · 1 comment ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
wireapp/wire-server#5315 · 4 comments · 1 reaction ·
Maintainers usually reply within 2 days
-
Dependency DashboardOpen
Difficulty 5/5 Over a week Newbie friendliness 20/100
wireapp/wire-server#4754 ·
Maintainers usually reply within 2 days
-
Difficulty 5/5 Over a week Newbie friendliness 20/100
wireapp/wire-server#4613 ·
Maintainers usually reply within 2 days
All issues in wireapp/wire-server
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
MorphRule, DataizeRule and ContextualizeRule silently accept unknown YAML keys, unlike rewrite `Rule`Possibly taken @renyamamoto2026-cmyk claimed this 2 days ago. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
objectionary/phino#2107 ·
Maintainers usually reply within 1 day
-
30-minutes algorithm any-language codewars dart easy elixir hackerrank hacktoberfest haskell help wanted interview-prep julia leetcode lua open-source r scala students zig
Difficulty 2/5 Under an hour Newbie friendliness 88/100
Huerte/algo-solutions-python#124 ·