← Back to issue list

Improve status report to expose unregistered tracks

View original Github issue

Metadata

Project
charmcraft
Number
#786
Type
issue
State
open
Author
facundobatista
Labels
Created
Updated
Closed

Current evaluation

Status command omits tracks that appear in channel-map but not in package.channels (unregistered tracks). Filed by maintainer facundobatista; no labels, no human response, code still exhibits the behavior.

Suggested action: needs triage

Reason: No labels, no assignee, and the only comment is an automated Jira-sync bot (CRAFT-3251) — no maintainer has categorised or acknowledged it. The StatusCommand code at store.py:1120 still builds the track list solely from package.channels, confirming the described gap persists, so the issue remains applicable but untriaged.

Impact: 35 Quick Win: 19.25 Staleness: 68 Complexity: 45 Confidence: 75 Support Request: 10

Issue body

If a track is unregistered in Charmhub, it will not be exposed by the `status` command. This is because the StatusCommand shows only the tracks that exist in the `package` part of the response. See this excerpt of a real server response where something is released to `test1/candidate` but then `test1` was unregistered: ``` {'channel-map': [{'base': {'architecture': 'amd64', 'channel': '18.04', 'name': 'ubuntu'}, 'channel': 'test1/candidate', 'expiration-date': None, 'progressive': {'paused': None, 'percentage': None}, 'resources': [], 'revision': 13, 'when': '2022-06-15T16:14:09Z'}, ... ], 'package': {'channels': [{'branch': None, 'fallback': None, 'name': 'latest/stable', 'risk': 'stable', 'track': 'latest'}, {'branch': None, 'fallback': 'latest/stable', 'name': 'latest/candidate', 'risk': 'candidate', 'track': 'latest'}, {'branch': None, 'fallback': 'latest/candidate', 'name': 'latest/beta', 'risk': 'beta', 'track': 'latest'}, {'branch': None, 'fallback': 'latest/beta', 'name': 'latest/edge', 'risk': 'edge', 'track': 'latest'}, {'branch': None, 'fallback': None, 'name': 'test-track/stable', 'risk': 'stable', 'track': 'test-track'}, {'branch': None, 'fallback': 'test-track/stable', 'name': 'test-track/candidate', 'risk': 'candidate', 'track': 'test-track'}, {'branch': None, 'fallback': 'test-track/candidate', 'name': 'test-track/beta', 'risk': 'beta', 'track': 'test-track'}, {'branch': None, 'fallback': 'test-track/beta', 'name': 'test-track/edge', 'risk': 'edge', 'track': 'test-track'}]}, 'revisions': [{'bases': [{'architecture': 'all', 'channel': '18.04', 'name': 'ubuntu'}], 'created-at': '2021-03-05T16:19:34.877239', 'errors': None, 'revision': 13, 'sha3-384': '309439e730c451277b32e03739101621d0d64f89a7fa93852bd140a5af022d2e6f41e4861ee27be980bcf2773e6e87a7', 'size': 810689, 'status': 'released', 'version': '7.4a'}, ... ]} ``` The status report should show the unregesitered track, but flagging it properly. For example, adding `(unregistered)` to its name.

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.8-27b
Impact: 35
Quick Win: 19.25
Staleness: 68
Complexity: 45
Confidence: 75
Support Request: 10
needs triage Status command omits tracks that appear in channel-map but not in package.channels (unregistered tracks). Filed by maintainer facundobatista; no labels, no human response, code still exhibits the behavior.
qwen/qwen3.6-35b-a3b
Staleness: 92
Complexity: 20
Confidence: 85
Support Request: 10
needs triage The status command hides releases to unregistered tracks. Suggests displaying them with an (unregistered) flag. Open for ~4 years with no maintainer triage or implementation.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 15
Confidence: 85
Support Request: 10
close stale The status command hides unregistered tracks from Charmhub. The report should display them with an (unregistered) flag. Currently unlabelled and inactive for over a year.
qwen3.6-35b-a3b-mtp-q6
Staleness: 92
Complexity: 20
Confidence: 75
Support Request: 5
close stale The status command currently hides unregistered tracks from Charmhub responses. The issue suggests displaying them with an unregistered flag. It remains unaddressed after over four years, linked only to an internal Jira ticket.
qwen3.6-35b-a3b-mtp-q6
Staleness: 85
Complexity: 30
Confidence: 65
Support Request: 0
needs triage status command omits releases on unregistered tracks by only parsing the package API response. Fix involves exposing these tracks. Internal ticket CRAFT-3251 created. Issue remains open with no recent updates.

Update history

No update history recorded yet.

Related issues

No related issues found above the similarity threshold.