Underscores in app names not reported properly
Metadata
Current evaluation
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.
Suggested action: needs triage
Reason: The issue has zero labels, zero comments, and no maintainer interaction in ~8 years (2876 days), so it has never been triaged. It is a genuine bug (misleading validation error), not a support request, and the exact error string from the report is no longer found in the current codebase, so a maintainer needs to confirm whether it still reproduces before any close decision.
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
35
Quick Win:
21.0
Staleness:
95
Complexity:
40
Confidence:
60
Support Request:
5
|
needs triage | 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. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
20
Confidence:
85
Support Request:
10
|
close stale | Snapcraft validation incorrectly rejects underscores in app names, reporting a schema error for valid names. Currently unlabelled, with no maintainer interaction and inactive for over 7 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
30
Confidence:
90
Support Request:
10
|
close stale | Snapcraft validation incorrectly rejects app names containing underscores, reporting a schema error for the first app. The issue has been inactive for over seven years with no maintainer response or labels. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
20
Confidence:
75
Support Request:
10
|
close stale | Snapcraft validation incorrectly flags valid app names with underscores, reporting errors only for the first app. The issue is nearly 8 years old with zero maintainer engagement. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
100
Complexity:
30
Confidence:
85
Support Request:
10
|
close stale | Snapcraft validation incorrectly flags underscores in app names with confusing schema errors. The report has been inactive for over seven years with no maintainer response or labels. |
Update history
No update history recorded yet.
Related work
-
Related To:
snapcraft (launchpad)#1616507
(confidence 80%)
Explicitly cross-referenced in the issue body; covers the underlying underscore-in-app-name rejection.
-
Duplicate Of:
snapcraft (launchpad)#1851003
(confidence 75%)
Same symptom: validation error names the first app instead of the actually invalid app in multi-app snaps.
-
Duplicate Of:
snapcraft (launchpad)#1996525
(confidence 70%)
Same symptom reported for snapcraft 7.2.7: misformatted app name flags the first app instead of the offending entry.
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. | |
| #1606890 Underscores in app names cause inscrutable error | snapcraft (launchpad) | closed | Closed without resolution. The confusing validation error for underscores in app names remains unaddressed, with the report abandoned due to zero comments and extended inactivity. | |
| #1616507 app names cannot contain underscores | snapcraft (launchpad) | closed | Abandoned without resolution due to inactivity. The validation schema still rejects underscores in snapcraft.yaml app names, leaving the request unaddressed. | |
| #1851003 Error message displays name of first application when a secondary application fails name validation | snapcraft (launchpad) | open | 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. |