Content interface parsing too lenient
Metadata
Current evaluation
Current models partially validate content plugs but still accept arbitrary interface data; maintainers acknowledged the UX gap without settling on an implementation or owner.
Suggested action: keep open
Reason: The report is valid and triaged: the reporter provided exact YAML, and a maintainer explicitly agreed it needs fixing while saying no suitable solution had been found. Current code requires content-plug targets but still represents arbitrary plugs and slots as Any, leaving broader snapd-interface validation and cross-project ownership unresolved.
Evaluated by: mr-cal-bot
Impact:
42
Quick Win:
6
Complexity:
78
Confidence:
87
Actionability:
61
Issue body
The following is accepted by snapcraft without error:
client-libs:
interface: content
content: client-libs
read: $SNAP/lib/client
When installing the snap, I get the message:
... bad plugs or slots client-libs (read or write path must be set)
The above should be instead:
client-libs:
interface: content
content: client-libs
read: [$SNAP/lib/client]
Or:
client-libs:
interface: content
content: client-libs
read:
- $SNAP/lib/client
snapcraft should tell me that my yaml is invalid instead of silently failing to set the attribute.
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
42
Quick Win:
6
Complexity:
78
Confidence:
87
Actionability:
61
|
keep open | Current models partially validate content plugs but still accept arbitrary interface data; maintainers acknowledged the UX gap without settling on an implementation or owner. | |
| stealth/space-bunny-alpha |
Impact:
42
Quick Win:
7
Complexity:
70
Confidence:
91
Actionability:
58
|
keep open | Malformed app content-interface read values are accepted during the build but rejected by snapd at install; maintainers agree validation is needed, with no implementation documented. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
17
Complexity:
30
Confidence:
70
Actionability:
80
|
needs triage | Content interface YAML validation accepts invalid string paths instead of lists, causing runtime installation errors. Issue is open, unlabelled, and has no comments. | |
| qwen/qwen3.8-27b |
Impact:
30
Quick Win:
21
Staleness:
95
Complexity:
30
Confidence:
55
Support Request:
10
|
close stale | Snapcraft silently accepts a string for the content interface read/write path instead of requiring a list, deferring the error to snapd install time. Reporter wants snapcraft to reject the invalid YAML. Unlabelled, no maintainer activity in ~9.5 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
30
Confidence:
88
Support Request:
10
|
close stale | Snapcraft accepts invalid YAML for content interface read paths, failing silently until install time. Untriaged, zero comments, ~9 years old with no maintainer engagement. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
25
Confidence:
85
Support Request:
5
|
close stale | Unvalidated content interface YAML configuration causes silent failures during snap installation. Reported over 9 years ago with no maintainer response. Likely resolved in modern snapcraft versions. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
25
Confidence:
75
Support Request:
5
|
close stale | Snapcraft accepts invalid YAML for content interface read paths, failing only at install time. Reporter requests strict YAML validation. Issue is over 9 years old with no maintainer response. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
No related issues found above the similarity threshold.