Content interface parsing too lenient

Metadata

Project: snapcraft (launchpad)
Number: #1666739
Type: issue
State: open
Author: ~michihenning
Labels: —
Created: 2017-02-22 01:14 AM UTC
Updated: 2017-02-24 04:59 PM UTC
Closed: —

Current evaluation

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.

Suggested action: close stale

Reason: The issue is 3478 days old with zero comments, no labels, and no maintainer interaction, and it targets a pre-rewrite snapcraft whose YAML validation has since been replaced by the Pydantic-based models layer (snapcraft/models), so the affected version is long unsupported and the original silent-acceptance behavior is very unlikely to persist. Confidence is moderate because tooling errors (no pinned SHA) prevented verifying whether modern snapcraft still accepts a scalar read/write value.

Impact: 30 Quick Win: 21.0 Staleness: 95 Complexity: 30 Confidence: 55 Support Request: 10

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
2026-09-01 07:45 AM UTC	qwen/qwen3.8-27b	Impact: 30 Quick Win: 21.0 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.
2026-07-23 11:51 AM UTC	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.
2026-07-22 12:19 PM UTC	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.
2026-07-09 08:45 PM UTC	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.
2026-06-20 11:13 PM UTC	qwen3.6-35b-a3b-mtp-q6	Staleness: 98 Complexity: 25 Confidence: 90 Support Request: 5	close stale	Snapcraft accepts malformed YAML for content interface paths, failing silently at install instead of validating early. Stricter syntax validation is required. The report remains open, unassigned, and inactive with no comments.

Update history

No update history recorded yet.

Related issues

No related issues found above the similarity threshold.