Specifying a nonexistent plug does cause any errors
Metadata
Current evaluation
Feature request from 2016: snapcraft should error or warn when a nonexistent plug name is specified in snapcraft.yaml (e.g. misspelling network-bind). No labels, no comments, no maintainer interaction in 10 years.
Suggested action: needs triage
Reason: The issue has zero comments, no labels, and no maintainer response in 10 years (last activity 2260 days ago). It is a legitimate feature request for build-time validation of plug names against known snap interfaces, but it cannot be closed as stale without confirming whether current snapcraft already validates plug names or whether the approach has changed. A maintainer needs to assess current relevance before any action.
Impact:
35
Quick Win:
19.25
Staleness:
92
Complexity:
45
Confidence:
45
Support Request:
35
Issue body
If for example I misspell network-bind
apps:
foo:
command: foo
plugs: [network-bin]
The snap still builds, but I get errors at runtime because no plug has been applied, it would be much better to error or at least warn that the plug I specified doesn't exist
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
35
Quick Win:
19.25
Staleness:
92
Complexity:
45
Confidence:
45
Support Request:
35
|
needs triage | Feature request from 2016: snapcraft should error or warn when a nonexistent plug name is specified in snapcraft.yaml (e.g. misspelling network-bind). No labels, no comments, no maintainer interaction in 10 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
30
Confidence:
85
Support Request:
10
|
close stale | Feature request to warn or error when a nonexistent plug is specified in snapcraft.yaml. Builds succeed but fail at runtime. Issue is over 9 years old with no maintainer activity. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
35
Confidence:
80
Support Request:
5
|
needs triage | Missing build-time validation for non-existent plugs in snapcraft.yaml, causing silent runtime failures. Untriaged, inactive for over 9 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
25
Confidence:
85
Support Request:
5
|
close stale | Snapcraft builds successfully despite misspelled or nonexistent plug names in snapcraft.yaml, causing runtime failures. The report requests build-time validation or warnings. The issue has been inactive for nearly 10 years with no maintainer response. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
25
Confidence:
85
Support Request:
10
|
close stale | Snapcraft accepts misspelled or nonexistent plug names without build errors, causing runtime failures. Requests adding build-time validation. Currently open, untriaged, inactive, and unassigned. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #1697468 snapcraft doesn't validate plugs: values | snapcraft (launchpad) | open | Request to add whitespace validation for plugs values in snapcraft.yaml (e.g. 'home x11' instead of 'home, x11'). Filed ~2015 during the build.snapcraft.io era, zero comments, no labels, no maintainer interaction in 9+ years. |