← Back to issue list

Progress shown in snapcraft status output is not accurate

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1932032
Type
issue
State
open
Author
~suligap
Labels
craft-338
Created
Updated
Closed
—

Current evaluation

snapcraft status reports inaccurate progressive-release progress: store channelmap current-percentage not split by architecture, and snapcraft derives the non-progressive release's percentage as 100 minus the progressive one. No maintainer activity in ~5 years.

Suggested action: needs triage

Reason: The issue is a genuine bug report (not support) with zero comments, no labels beyond craft-338, and no maintainer interaction in ~1900 days, so it has never been triaged. It is not safe to close as stale because the underlying code path (snapcraft/store/channel_map.py still parses current-percentage, and status still reports progressive releases per commits #3306/#6189) may still contain the 100-minus-progressive calculation, but I could not confirm via tools whether the store-side fix (LP #1903046) was ever deployed or whether the snapcraft-side calculation was changed, so a maintainer should verify before acting.

Impact: 35 Quick Win: 15.75 Staleness: 90 Complexity: 55 Confidence: 60 Support Request: 5

Issue body

There are two parts here. First one likely won't need any action on the snapcraft side. 1. A Store bug where the current-percentage returned in the channelmap endpoint is not correctly split by architecture, i.e. current-percentage for a release represents current % of installs of a revision in a channel out of all installs in that channel (regardless of architecture), but it should be current % of installs in a channel for the architecture the revision is released for. This is going to be fixed on the store side very likely and it should not require any snapcraft changes. The end result should be that if snapcraft status reports progress of 10% -> 45% for armhf revision 245 released to stable, it should mean that the target is 45% of armhf installs in stable (this is correct currently) and 10% is 10% of all armhf stable installs and not 10% of all installs of any arch in stable. 2. When snapcraft reports a progressive release in `status` it currently calculates the current percentage of the non-progressive active release to be 100 minus $current-percentage-of-the-progressive-counterpart. This is not correct. In reality there will be active installs of revisions different than the current progressive one and current non-progressive one. After the Store fix for https://bugs.launchpad.net/snapcraft/+bug/1903046 is deployed, snapcraft can simply use the current-percentage of the non-progressive release instead (because current-percentage will be returned for all releases in the channelmap endpoint response).

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 35
Quick Win: 15.75
Staleness: 90
Complexity: 55
Confidence: 60
Support Request: 5
needs triage snapcraft status reports inaccurate progressive-release progress: store channelmap current-percentage not split by architecture, and snapcraft derives the non-progressive release's percentage as 100 minus the progressive one. No maintainer activity in ~5 years.
qwen/qwen3.6-35b-a3b
Staleness: 95
Complexity: 60
Confidence: 85
Support Request: 10
needs triage Snapcraft status progress calculation is inaccurate due to store endpoint behavior and internal logic. Requires a code update after a store-side architecture-based percentage fix is deployed. Currently untriaged and inactive.
qwen/qwen3.6-35b-a3b
Staleness: 92
Complexity: 55
Confidence: 75
Support Request: 5
needs triage Technical bug report on inaccurate progress percentages in snapcraft status output, citing architecture-specific calculation errors and progressive release logic. Unassessed by maintainers with zero comments over five years.
qwen3.6-35b-a3b-mtp-q6
Staleness: 98
Complexity: 55
Confidence: 85
Support Request: 10
close stale Reports inaccurate progress percentages in snapcraft status due to architecture-agnostic store metrics and incorrect local calculation. Untriaged, inactive for ~5 years, and explicitly depends on an external store API fix.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 65
Confidence: 90
Support Request: 10
close stale Reports inaccurate progress percentages in snapcraft status due to architecture-agnostic store data and incorrect progressive release calculations. Untriaged and inactive for over 5 years.

Update history

No update history recorded yet.

Related work

  • Related To: snapcraft (launchpad)#1903046 (confidence 70%)

    Issue explicitly references LP bug 1903046 as the store-side fix that would allow snapcraft to use the non-progressive release's current-percentage directly.

  • Related To: canonical/snapcraft#6189 (confidence 55%)

    Merged PR 'feat: show progressive percentage in release output' touches the same progressive-percentage display logic this issue concerns.

Related issues

Issue Project State Summary Similarity
#1903046 Progressive release stops showing metrics when set to 100% target snapcraft (launchpad) open snapcraft status stops showing progressive release metrics once target reaches 100%. Reported 5.8 years ago with zero maintainer interaction, no labels, and no comments. Progressive release feature has since evolved (PR #6189 merged).
72%