Push issue with bad internet connection
Metadata
Current evaluation
Upload/push on a flaky connection fails with a bad gateway after the file reached the store; retrying then fails with 'binary_sha3_384: A file with this exact same content has already been uploaded'. Reporter asks for resumable uploads (returning an upload_id) and a workaround. No maintainer response or labels.
Suggested action: needs triage
Reason: The report is unlabelled, has zero comments and no maintainer response after ~8.8 years, so it has never been triaged. The failure mode is still visible in the current code: snapcraft/commands/upload.py calls upload_file then notify_upload, and notify_upload in snapcraft/store/client.py:655-663 raises a generic SnapcraftError on any store error (no 'binary_sha3_384' handling exists anywhere in the repo, confirmed by grep), so the orphan upload is never reconciled. However the fix is not a simple client-side patch: the dedup verdict comes from the store backend, and the reporter's own proposal ('server should return upload_id') needs store-side work, so root cause and ownership are unconfirmed.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
42
Quick Win:
7
Complexity:
68
Confidence:
62
Actionability:
52
|
needs triage | Upload/push on a flaky connection fails with a bad gateway after the file reached the store; retrying then fails with 'binary_sha3_384: A file with this exact same content has already been uploaded'. Reporter asks for resumable uploads (returning an upload_id) and a workaround. No maintainer response or labels. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
7
Complexity:
60
Confidence:
70
Actionability:
60
|
needs triage | Upload fails on bad internet connection; retrying causes 'file already uploaded' error. User requests resumable upload support. | |
| qwen/qwen3.8-27b |
Impact:
15
Quick Win:
7
Staleness:
98
Complexity:
55
Confidence:
72
Support Request:
35
|
close stale | Snapcraft push fails with binary_sha3_384 duplicate error after interrupted upload on slow connection; requests server return upload_id for resume. 8+ years old, zero comments, no labels, push command since removed. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
40
Confidence:
90
Support Request:
60
|
close stale | Upload fails with bad gateway on slow connection, retry causes duplicate content error. No maintainer response in 8+ years. Suggests resumable upload support. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
20
Confidence:
90
Support Request:
60
|
close stale | User reports upload failure and duplicate content error during push with poor connectivity. Suggests server should return an upload ID for resumption. Unaddressed for over 8 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
45
Confidence:
90
Support Request:
30
|
close stale | User reports upload failure and duplicate content error due to slow internet, suggesting server-side resumability or upload IDs. Unaddressed for over 8 years. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Duplicate Of:
snapcraft (launchpad)#1683536
(confidence 60%)
Explicitly cited by the reporter as the 'related issue' whose classification as a wish they are disputing; that number did not resolve in the local issue corpus so the overlap could not be confirmed.
Related issues
No related issues found above the similarity threshold.