Handle unquoted multi-arch: no
Metadata
Current evaluation
Unquoted YAML no becomes a boolean and fails multi-arch validation with a generic error; the fix is undecided between clearer guidance and accepting false as an alias.
Suggested action: needs triage
Reason: The model currently restricts DebianMultiArch to four strings, the valid fixture warns users to quote no, and the invalid-value fixture shows the resulting generic enum error. The problem is confirmed, but no labels or comments establish priority, and the body leaves open whether to provide a targeted error or normalize false.
Evaluated by: mr-cal-bot
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
38
Quick Win:
17
Complexity:
28
Confidence:
94
Actionability:
62
|
needs triage | Unquoted YAML no becomes a boolean and fails multi-arch validation with a generic error; the fix is undecided between clearer guidance and accepting false as an alias. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
19
Complexity:
20
Confidence:
70
Actionability:
80
|
needs triage | Unquoted multi-arch: no in YAML is parsed as boolean false instead of string no, causing confusing validation errors. Suggests adding better error messages or accepting false as a synonym. | |
| qwen/qwen3.8-27b |
Impact:
25
Quick Win:
20
Staleness:
55
Complexity:
20
Confidence:
75
Support Request:
10
|
needs triage | YAML parser converts unquoted multi-arch: no to boolean false, producing a confusing generic validation error. Maintainer filed request to add a specific error message or accept false as synonym for "no". Unlabelled, no comments, no activity in 127 days. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
55
Complexity:
15
Confidence:
75
Support Request:
0
|
needs triage | YAML parser interprets unquoted multi-arch: no as false, causing confusion. Suggests adding an error message or allowing false as a synonym. Currently unlabelled and inactive for 86 days. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
55
Complexity:
20
Confidence:
85
Support Request:
0
|
needs triage | YAML parser treats unquoted multi-arch: no as false, causing confusion. Suggests adding an error or alias. Currently unlabelled and inactive for 73 days. |
Update history
No update history recorded yet.
Related work
-
Related To:
debcraft#125
(confidence 98%)
Merged PR #136 introduced the validated multi-arch field and its quote-sensitive tests, making this a follow-up usability issue.
Related issues
No related issues found above the similarity threshold.