Can’t distinguish programmatically between snapcraft.yaml errors and other errors
Metadata
Current evaluation
2016 feature request for programmatic error codes distinguishing snapcraft.yaml validation failures from other build errors, so build.snapcraft.io could attach yaml errors to its UI. No labels, no comments, no maintainer activity for ~9.5 years.
Suggested action: close stale
Reason: Filed ~9.5 years ago (3479 days) with zero comments, no labels, and no maintainer interaction whatsoever. The original motivation (build.snapcraft.io's UI, referenced bugs 1578024/1624019) has long been superseded, and the snapcraft codebase has been fully rewritten since 2016 (core 22/24 architecture), so the request no longer maps to the current error-handling design. If machine-readable error classification is still needed, a fresh report against the current codebase is the right path.
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
30
Quick Win:
18.0
Staleness:
95
Complexity:
40
Confidence:
60
Support Request:
15
|
close stale | 2016 feature request for programmatic error codes distinguishing snapcraft.yaml validation failures from other build errors, so build.snapcraft.io could attach yaml errors to its UI. No labels, no comments, no maintainer activity for ~9.5 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
35
Confidence:
90
Support Request:
25
|
close stale | Feature request to add programmatic error codes distinguishing snapcraft.yaml validation errors from other runtime failures. Issue is completely inactive with no maintainer response. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
20
Confidence:
85
Support Request:
10
|
close stale | Feature request from 2015 asking for distinct error codes to differentiate snapcraft.yaml errors from other failures. No maintainer engagement, labels, or activity in over 9 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
20
Confidence:
80
Support Request:
10
|
close stale | Feature request from 9+ years ago asking for distinct error codes to differentiate snapcraft.yaml errors from other failures. Zero maintainer activity since 2021. Project architecture has likely evolved significantly since then. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
30
Confidence:
90
Support Request:
10
|
close stale | Snapcraft lacks error codes to distinguish snapcraft.yaml configuration failures from other runtime errors. This blocks build.snapcraft.io from routing UI-specific messages. Open, inactive, and unassigned, it requires triage and implementation. |
Update history
No update history recorded yet.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #4636 Better error message when we can't find snapcraft.yaml | snapcraft | open | Feature request to improve the error message when snapcraft.yaml is not found in the craft-application branch, adding a helpful message with a documentation link. No labels, no assignee, last activity 536 days ago. |