"upload" command sends progress to stdErr unnecessarily
Metadata
Current evaluation
`upload` remains available, but current code uses Craft CLI progress output and no longer shows the cited legacy `Pushing`/`Processing...` messages; a current reproduction is needed.
Suggested action: needs triage
Reason: The report has no labels, comments, maintainer response, or other triage. Current `snapcraft/commands/upload.py` still implements `upload`, but it now uses `emit.progress_bar("Uploading...", ...)` and `emit.message(...)`; the cited legacy `Pushing ...` and `Processing...` messages were not found, so stream capture under current versions and TTY modes is needed to confirm the bug.
Evaluated by: mr-cal-bot
Impact:
32
Quick Win:
9
Complexity:
28
Confidence:
64
Actionability:
38
Issue body
When integrating a release process within a Continuous Integration (CI) automation routine, it's useful to get some deprecation/warnings messages in the stdErr when invoking "snapcraft upload". For example this: https://snapcraft.io/docs/deprecation-notices/dn11
However, other messages that are not warnings or errors are also sent to stdErr (instead of just stdOut), which forces me to have to ignore them in the process that uploads a release under my CI setup.
Examples of these kind of messages:
Pushing 'gwallet_0.3.332.0_amd64.snap' [=== ] 12%
Processing...-
Having them being sent to stdOut instead of stdErr would allow me to fail CI whenever any important message gets sent to stdErr; allowing me to pay attention to deprecation notices or other important stuff happens.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
32
Quick Win:
9
Complexity:
28
Confidence:
64
Actionability:
38
|
needs triage | `upload` remains available, but current code uses Craft CLI progress output and no longer shows the cited legacy `Pushing`/`Processing...` messages; a current reproduction is needed. | |
| stealth/space-bunny-alpha |
Impact:
42
Quick Win:
17
Complexity:
37
Confidence:
87
Actionability:
64
|
needs triage | Reported `snapcraft upload` sends normal progress to stderr, obscuring CI warnings; no triage or updates for 1426 days, and the quoted legacy messages are absent from current source. | |
| qwen3.6-35b-a3b-mtp-q6 |
Impact:
45
Quick Win:
34
Staleness:
95
Complexity:
25
Confidence:
65
Support Request:
25
|
needs triage | Report that snapcraft upload sends progress messages to stderr instead of stdout, breaking CI automation that relies on stderr for important warnings. Untriaged, 1405 days old, no maintainer response. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
15
Confidence:
85
Support Request:
10
|
close stale | Request to route "snapcraft upload" progress messages to stdout instead of stderr for CI error handling. Unlabelled, 0 comments, inactive for over 3.5 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
20
Confidence:
85
Support Request:
5
|
close stale | snapcraft upload sends progress messages to stderr instead of stdout, interfering with CI automation that relies on stderr for warnings. Unlabeled and inactive for over 3 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
15
Confidence:
85
Support Request:
10
|
close stale | The snapcraft upload command sends progress messages to stderr instead of stdout, interfering with CI automation that relies on stderr for warnings. Untriaged and inactive for over 3.5 years. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
No related issues found above the similarity threshold.