Error message displays name of first application when a secondary application fails name validation
Metadata
Current evaluation
Snapcraft schema validation names the first app instead of the actually invalid app when a secondary app name fails validation. Open ~6.8 years, no labels, zero maintainer interaction, no fix; a similar report (LP 1996525) is also open.
Suggested action: needs triage
Reason: The issue has no labels, no assignee, and zero comments across 2495 days, so it has never been assessed by a maintainer; a well-formed bug report with a clear reproducer still needs triage. It cannot be closed as stale because there is no evidence the current (pydantic-based) validation no longer produces this misleading message, and a related open report (LP 1996525) shows the same symptom persisted into snapcraft 7.2.7. A maintainer should verify whether the error still misreports the app name in the current codebase before deciding to fix or close.
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
20
Quick Win:
12.0
Staleness:
92
Complexity:
40
Confidence:
60
Support Request:
10
|
needs triage | Snapcraft schema validation names the first app instead of the actually invalid app when a secondary app name fails validation. Open ~6.8 years, no labels, zero maintainer interaction, no fix; a similar report (LP 1996525) is also open. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
25
Confidence:
85
Support Request:
5
|
close stale | Snapcraft validation incorrectly reports the first app name instead of the actual invalid app in multi-app configurations. Issue remains unaddressed for over six years with zero maintainer interaction. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
15
Confidence:
85
Support Request:
0
|
close stale | Bug report detailing incorrect error messaging during snapcraft.yaml validation, incorrectly flagging the first app instead of the invalid one. Issue remains unlabelled and inactive for over 6 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
25
Confidence:
75
Support Request:
5
|
needs triage | Bug report showing snapcraft validation incorrectly flags the first app name instead of the invalid secondary app. Unlabelled and inactive for over 6 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
20
Confidence:
85
Support Request:
5
|
close stale | Bug in snapcraft where validation errors incorrectly report the first app name instead of the actual invalid app name. Issue is over six years old with no maintainer interaction or updates. |
Update history
No update history recorded yet.
Related work
-
Duplicate Of:
snapcraft (launchpad)#1996525
(confidence 75%)
LP bug 1996525 reports the identical symptom (misformatted app name flags the first app instead of the offending entry) in snapcraft 7.2.7; it is a later duplicate of this older report and is also open and untriaged.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1996525 inaccurate error for a misformatted app name | snapcraft (launchpad) | open | Snapcraft reports error on wrong app when a misformatted app name uses underscore instead of hyphen. Issue is 1389 days old with no maintainer engagement or labels. | |
| #1798205 Underscores in app names not reported properly | snapcraft (launchpad) | open | Snapcraft reports the wrong app name in validation errors when an app name contains an underscore: with apps 'one' and 'two_three', the error blames the valid app 'one' instead of 'two_three'. Open since 2014, no labels, comments, or maintainer activity. | |
| #1986624 snapcraft points to wrong entry in apps as being invalid. | snapcraft (launchpad) | open | Snapcraft 6.1 validation error misreports the first app ('runtests') as invalid when the actual offending app name ('get_cache_info', with an underscore) is the real problem. No maintainer interaction; zero comments; ~4 years old. |