← Back to issue list

plugs: plugs can have no element

View original Github issue

Metadata

Project
snapcraft
Number
#2840
Type
pull request
State
merged
Author
aiqs4
Labels
—
Created
Updated
Closed

Current evaluation

Merged in snapcraft#2840 via commit 971424d0c, fixing null plug and slot definitions to use their names as implicit interfaces instead of crashing.

Resolution: closed resolved

Reason: PR #2840 was merged as commit 971424d0c. The fix makes plugs and slots without an explicit interface fall back to their own names, restoring valid implicit-interface behavior.

Evaluated by: mr-cal-bot

No scores available.

Issue body

if plug has no subelement, then the interface changes crash this

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Merged in snapcraft#2840 via commit 971424d0c, fixing null plug and slot definitions to use their names as implicit interfaces instead of crashing.
stealth/space-bunny-alpha — closed resolved Merged in snapcraft#2840 via 971424d0c, fixing null plug/slot definitions to use their names as implicit interfaces instead of crashing.
qwen/qwen3.6-35b-a3b — — Merged a fix for a crash when plugs lack an explicit interface element. The update adds a None check and test, enabling implicit interface naming via the plug name to resolve a snap.yaml generation regression.
qwen3.6-35b-a3b-mtp-q6 — — Merged fix resolving a crash when plugs or slots omit the interface field. The implementation now handles None values by defaulting to the plug or slot name as the interface, correcting a regression in snapcraft 3.8.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#2884 plugs/slots: match output format read in snapcraft.yaml snapcraft merged Merged PR #2884 (commit 70e7789a7, cjp256) reverted the long-form plug/slot emission from #2840, restoring 3.8 output so snap.yaml matches the syntax used in snapcraft.yaml (no implied `interface`).
78%
#1581166 unused and potentially confusing support for plugs/slots at a part level in the snapcraft.yaml schema snapcraft (launchpad) closed Snapcraft 2.9 now rejects plugs and slots declared at the part level via merged PR canonical/snapcraft#514 (6fabd20bc); the fix passed SRU verification.
74%
#3874 meta: fix content plug detection snapcraft merged Merged PR #3874 in commit b962783c1, allowing empty content plug/slot definitions and deferring type validation until snap packaging.
73%
#3657 meta: support plugs snapcraft merged Merged PR #3657 into snapcraft/7.0 via b28e65257, adding metadata support for plugs and ContentPlugs (implementation 6512b7cdd; CRAFT-816).
72%
#1617302 Specifying a nonexistent plug does cause any errors snapcraft (launchpad) open Unknown plug typos once built silently; snapd now validates interfaces and Snapcraft has used that validation since before June 2020, leaving no Snapcraft-side fix.
71%