← Back to issue list

internal errors for `all` platform

View original Github issue

Metadata

Project
craft-application
Number
#692
Type
issue
State
open
Author
mr-cal
Labels
—
Created
Updated
Closed
—

Current evaluation

A null `all` platform reaches Pydantic as a required Platform, causing an internal type error instead of the intended build-on validation message; the issue remains open and untriaged.

Suggested action: needs triage

Reason: The report provides a minimal YAML, exact `pack` command, complete error, and expected message; current `ProjectService._vectorise_platforms` leaves `all` as null before validating it as a required Platform, matching the failure. The bug is valid and narrowly scoped, but the issue has no labels or substantive maintainer response beyond Jira-sync automation.

Evaluated by: mr-cal-bot

Impact: 32 Quick Win: 22 Complexity: 22 Confidence: 94 Actionability: 90

Issue body

```yaml name: testcraft version: "0.1" base: ubuntu@24.04 platforms: all: parts: my-test: plugin: nil ``` ```bash craft-application/testcraft> python3 ./__main__.py pack testcraft internal error: 1 validation error for dict[literal['platforms'],dict[str,Platform]] platforms.all Input should be a valid dictionary or instance of Platform [type=model_type, input_value=None, input_type=NoneType] For further information visit https://errors.pydantic.dev/2.10/v/model_type ``` It's not surprising for a user to attempt to use `all` in `build-on`. Previously, Snapcraft would get to unmarshal the project and produce a user-friendly error like: ``` > snapcraft pack Bad snapcraft.yaml content: - 'all' cannot be used for 'build-on' (in field 'platforms') ``` Similar to #690

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha
Impact: 32
Quick Win: 22
Complexity: 22
Confidence: 94
Actionability: 90
needs triage A null `all` platform reaches Pydantic as a required Platform, causing an internal type error instead of the intended build-on validation message; the issue remains open and untriaged.
qwen/qwen3.6-35b-a3b
Impact: 40
Quick Win: 20
Complexity: 30
Confidence: 70
Actionability: 70
keep open Pydantic validation error when using `platforms: all:` instead of user-friendly error message. Valid bug, open 545 days, appears to be craft-application#692.
qwen/qwen3.8-27b
Impact: 35
Quick Win: 21
Staleness: 75
Complexity: 40
Confidence: 72
Support Request: 10
needs triage Pydantic internal error when using 'all' as a platform name in platforms dict instead of a user-friendly validation message. Code still skips vectorising 'all' platforms, leaving them as None. Open 525 days, unlabelled, no maintainer interaction beyond Jira bot.
qwen/qwen3.6-35b-a3b
Staleness: 90
Complexity: 20
Confidence: 80
Support Request: 10
needs triage Reports an internal Pydantic validation error when using all in the platforms field instead of a user-friendly message. Unlabelled and inactive for over a year.
qwen3.6-35b-a3b-mtp-q6
Staleness: 85
Complexity: 20
Confidence: 80
Support Request: 5
needs triage Maintainer reports an internal Pydantic validation error when using platforms: all: in craft-application. Requests a user-friendly error message instead. Unlabelled and inactive for over a year.

Update history

No update history recorded yet.

Related work

  • Related To: canonical/craft-application#690 (confidence 98%)

    Explicitly referenced as similar; #690 was split, with #692 tracking the remaining all-platform validation and error-handling bug.

Related issues

No related issues found above the similarity threshold.