Some valid `spread.yaml` files don't get parsed correctly.
Metadata
Current evaluation
Bug report that some valid spread.yaml files accepted by spread fail to parse in craft's test command, e.g. a backend systems list containing a plain string like 'ubuntu-18.04-64'. No maintainer response or labels; only an auto Jira-sync bot comment. Likely already fixed by PR #737 (accept string system models).
Suggested action: needs triage
Reason: No maintainer has acknowledged, labelled, or responded to this issue — the only comment is the auto-generated Jira-sync bot message (CRAFT-4375). The reported case (string entries in backend systems) appears addressed by commit 2f11fe33 'fix(SpreadBackend): accept string system models (#737)', which added str support to the systems list, but the issue title says 'some valid files' so a maintainer should confirm whether the specific repro is covered before closing.
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
50
Quick Win:
35.0
Staleness:
75
Complexity:
30
Confidence:
60
Support Request:
10
|
needs triage | Bug report that some valid spread.yaml files accepted by spread fail to parse in craft's test command, e.g. a backend systems list containing a plain string like 'ubuntu-18.04-64'. No maintainer response or labels; only an auto Jira-sync bot comment. Likely already fixed by PR #737 (accept string system models). | |
| qwen/qwen3.6-35b-a3b |
Staleness:
85
Complexity:
30
Confidence:
80
Support Request:
10
|
needs triage | Valid spread.yaml files fail to parse correctly. Reported over a year ago with no maintainer response, labels, or assignee. Currently untriaged and inactive. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
40
Confidence:
85
Support Request:
10
|
needs triage | Unparsed spread.yaml files containing string keys instead of mappings. Open for 469 days with no maintainer response or labels. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
40
Confidence:
80
Support Request:
10
|
needs triage | Valid spread.yaml files with string keys in system definitions fail to parse. Open, unassigned, and unlabeled. Last activity 389 days ago when an internal Jira ticket was created. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
craft-application#737
(confidence 70%)
Commit 2f11fe33 'fix(SpreadBackend): accept string system models (#737)' added str support to the backend systems list, matching the issue's repro of a plain string system entry.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #703 Bad error message if 'spread.yaml' is missing | craft-application | closed | Closed without resolution. A missing spread.yaml caused an internal error during crafttool test. No fix was implemented or merged. The ticket was closed after a Jira sync comment, indicating it was abandoned. |