← Back to issue list

Some valid `spread.yaml` files don't get parsed correctly.

View original Github issue

Metadata

Project
craft-application
Number
#698
Type
issue
State
open
Author
lengau
Labels
—
Created
Updated
Closed
—

Current evaluation

Valid spread backends with bare system-name strings are now accepted; this report was resolved by merged PR #737, commit 2f11fe33.

Suggested action: close resolved

Reason: PR #737, resolving commit 2f11fe33, explicitly made SpreadBackend accept string system models, matching the reported bare string in the systems list. The current model also defines systems as a union of strings and mappings, confirming the fix is present.

Evaluated by: mr-cal-bot

Impact: 44 Quick Win: 34 Complexity: 18 Confidence: 99 Actionability: 94

Issue body

### Bug Description Some `spread.yaml` files that spread accepts don't get parsed correctly. ### To Reproduce Include the example spread snippet below, then run the `test` subcommand. ### part yaml ```shell backends: google: key: '$(HOST: echo "$SPREAD_GOOGLE_KEY")' location: snapd-spread/us-east1-b halt-timeout: 3h systems: - ubuntu-18.04-64 # String rather than mapping key ``` ### Relevant log output ```shell n/a ```

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 44
Quick Win: 34
Complexity: 18
Confidence: 99
Actionability: 94
close resolved Valid spread backends with bare system-name strings are now accepted; this report was resolved by merged PR #737, commit 2f11fe33.
qwen/qwen3.6-35b-a3b
Impact: 30
Quick Win: 4
Complexity: 60
Confidence: 60
Actionability: 30
needs triage Vague report that some spread.yaml files don't parse correctly, with no error output or specific reproduction details
qwen/qwen3.8-27b
Impact: 50
Quick Win: 35
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.

Update history

No update history recorded yet.

Related work

  • Likely Fixed By: canonical/craft-application#737 (confidence 99%)

    The merged PR is titled “fix(SpreadBackend): accept string system models” and directly addresses the supplied reproducer.

Related issues

No related issues found above the similarity threshold.