trying to upload a snap without signing the agreement prints the error twice
Metadata
Current evaluation
Unsigned-account upload errors were printed twice; the legacy messages are absent from the current tree after the snap-push endpoint refactor in 7de1a0b7f.
Suggested action: close resolved
Reason: The report provides a precise unsigned-account upload scenario and identifies both duplicate messages. Neither message remains in the current tree, and pickaxe history identifies commit 7de1a0b7f (snapcraft#632), which refactored and updated the snap-push endpoint logic.
Evaluated by: mr-cal-bot
Impact:
25
Quick Win:
14
Complexity:
28
Confidence:
88
Actionability:
78
Issue body
If I try to upload a snap with a user that has not signed the user agreement, an error is returned.
This error prints in red:
There was an error uploading the application.
Reason: Forbidden
Text: Developer has not signed agreement.
Then it prints in green:
Upload did not complete.
Some errors were detected:
Developer has not signed agreement.
This error should be cleaned up. The Reason and Text maybe should be printed only if -d is passed, and with a text preceding it to make it clear that it's the response from the store.
The other error should be printed in red.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
25
Quick Win:
14
Complexity:
28
Confidence:
88
Actionability:
78
|
close resolved | Unsigned-account upload errors were printed twice; the legacy messages are absent from the current tree after the snap-push endpoint refactor in 7de1a0b7f. | |
| qwen/qwen3.6-35b-a3b |
Impact:
20
Quick Win:
5
Complexity:
10
Confidence:
50
Actionability:
30
|
close resolved | Duplicate error messages when uploading a snap without signed user agreement. Issue is 10 years old with no activity. | |
| qwen/qwen3.8-27b |
Impact:
20
Quick Win:
17
Staleness:
95
Complexity:
15
Confidence:
55
Support Request:
5
|
needs triage | Snapcraft upload command prints the 'Developer has not signed agreement' error twice (once in red, once in green) when a user has not signed the store agreement. Suggests cleaning up output so Reason/Text only show with -d flag. Open since 2016 with no comments or maintainer response. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
15
Confidence:
95
Support Request:
5
|
close stale | Duplicate error output when uploading a snap without a signed agreement. Suggests suppressing verbose details unless debug flag is used. Issue has been inactive for over 9 years with no maintainer response. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
15
Confidence:
90
Support Request:
0
|
close stale | Minor CLI UX issue where uploading a snap without a signed agreement prints duplicate error messages. Issue is over 9 years old with no maintainer interaction or updates. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
15
Confidence:
85
Support Request:
5
|
close stale | CLI prints duplicate error messages when uploading a snap without a signed agreement. Issue is over 10 years old with no activity or maintainer response. |
Update history
| Date | Change |
|---|---|
| created |
Related work
-
Likely Fixed By:
snapcraft#632
(confidence 88%)
Commit 7de1a0b7f refactored snap-push endpoint logic; the duplicated legacy diagnostics are absent from the current code.
Related issues
No related issues found above the similarity threshold.