← Back to issue list

Push issue with bad internet connection

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1735004
Type
issue
State
open
Author
~hatari
Labels
—
Created
Updated
Closed
—

Current evaluation

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.

Suggested action: close stale

Reason: Issue is 3198 days old with zero comments, zero labels, and no maintainer interaction. The referenced Launchpad bug 1683536 summary confirms 'The push command was later removed from snapcraft,' making this issue no longer applicable to the current codebase. The upload flow has been restructured since then.

Impact: 15 Quick Win: 6.75 Staleness: 98 Complexity: 55 Confidence: 72 Support Request: 35

Issue body

I found related issue https://bugs.launchpad.net/snapcraft/+bug/1683536, but I think this should rather be a bug than a wish: 1) I was trying to upload snap to the store, but I had slow internet connection and it took much time, so I faced bad gateway error (actually there is another question why, but nvm) and push was failed 2) I tried to retry push - then it went successful at first sight, but then I faced binary_sha3_384 error on processing stage ``The store was unable to accept this snap. - binary_sha3_384: A file with this exact same content has already been uploaded`` So it looked like firstly snap was actually downloaded well to the store, but smth happened. There were no updates in dashboard, snap was just downloaded to the server and that's all. As a result, I wasn't able to upload this particular snap. Is there any workarounds from here? I think in this case server should return upload_id or something of this snap and proceed pushing.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 15
Quick Win: 6.75
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.
qwen3.6-35b-moe-q4
Staleness: 98
Complexity: 45
Confidence: 90
Support Request: 30
close stale Reports snap upload failure and duplicate content error after slow internet interruption. Suggests server should return an upload_id for retries. Inactive for over 8 years with no maintainer response.

Update history

No update history recorded yet.

Related work

  • Duplicate Of: snapcraft#1683536 (confidence 75%)

    Issue body explicitly references this Launchpad bug as the related issue; both describe the same binary_sha3_384 duplicate-content error after an interrupted/retried push.

Related issues

No related issues found above the similarity threshold.