Error message displays name of first application when a secondary application fails name validation
Metadata
Current evaluation
App-name validation reports the first valid app instead of the offending secondary app; no fix or maintainer triage is evident.
Suggested action: needs triage
Reason: The report provides a complete YAML reproducer and exact mismatch: hash_password is invalid, but the error names matrix-synapse. However, the issue has no labels, assignee, or maintainer comments, and the current checkout contains neither the reported message nor evidence of a resolving change, so current reproducibility needs confirmation.
Evaluated by: mr-cal-bot
Impact:
28
Quick Win:
16
Complexity:
35
Confidence:
74
Actionability:
88
Issue body
When specifying multiple apps in a snapcraft.yaml file, per below example, where one of the names fails naming rule validation, the first application is listed as the problematic application entry:
apps:
matrix-synapse:
command: synctl --no-daemonize start $SNAP_COMMON/homeserver.yaml
stop-command: synctl -c $SNAP_COMMON stop
plugs: [network-bind, network]
daemon: simple
hash_password:
command: hash_password
aliases:
- hash_password
The 'hash_password' name is invalid given the underscore, however the error produced is per below:
Issues while validating snapcraft.yaml: The 'apps' property does not match the required schema: 'matrix-synapse' is not a valid app name. App names consist of upper- and lower-case alphanumeric characters and hyphens. They cannot start or end with a hyphen.
This should indicate the problematic application (hash_password) rather than the first and valid application (matrix-synapse).
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
28
Quick Win:
16
Complexity:
35
Confidence:
74
Actionability:
88
|
needs triage | App-name validation reports the first valid app instead of the offending secondary app; no fix or maintainer triage is evident. | |
| stealth/space-bunny-alpha |
Impact:
24
Quick Win:
15
Complexity:
30
Confidence:
87
Actionability:
91
|
needs triage | Schema validation reports the first app name when a later app has an invalid name; remains open, untriaged, and unresolved. | |
| qwen/qwen3.8-27b |
Impact:
20
Quick Win:
12
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. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
No related issues found above the similarity threshold.