Application: treat CraftError-like exceptions as CraftErrors
Metadata
Current evaluation
Application should treat exceptions following CraftError's message/resolution pattern as CraftErrors instead of converting them to internal errors. Open since 2023, last activity 465 days ago, no labels or maintainer response beyond a Jira sync bot comment.
Suggested action: needs triage
Reason: The issue was filed by a maintainer (lengau) with no labels, no assignee, and no substantive maintainer response beyond the Jira sync bot comment. A related commit deca76bd 'fix(Application): catch all craft-like errors (#695)' exists in the history, suggesting partial or related work was done, but it's unclear if it fully addresses this issue. The issue needs triage to determine if it's already resolved by that commit or still open.
Issue body
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.8-27b |
Impact:
50
Quick Win:
30.0
Staleness:
75
Complexity:
40
Confidence:
70
Support Request:
0
|
needs triage | Application should treat exceptions following CraftError's message/resolution pattern as CraftErrors instead of converting them to internal errors. Open since 2023, last activity 465 days ago, no labels or maintainer response beyond a Jira sync bot comment. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
85
Complexity:
20
Confidence:
80
Support Request:
10
|
needs triage | Exceptions matching CraftError patterns are incorrectly handled as internal errors. Untriaged, inactive for over a year, awaiting maintainer review. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
25
Confidence:
65
Support Request:
10
|
needs triage | Unlabelled issue requesting that CraftError-like exceptions be handled as CraftErrors instead of internal errors. Currently inactive for over a year with only a Jira sync bot comment. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
30
Confidence:
65
Support Request:
10
|
needs triage | Treat CraftError-like exceptions as CraftErrors instead of misclassifying them as internal errors. Currently stale and unassigned. Requires triage and implementation. |
Update history
No update history recorded yet.
Related work
-
Likely Fixed By:
craft-application#695
(confidence 60%)
Commit deca76bd 'fix(Application): catch all craft-like errors (#695)' appears to address catching craft-like errors in the Application, which aligns with this issue's request to treat CraftError-like exceptions as CraftErrors.
Related issues
| Issue | Project | State | Summary | Similarity |
|---|---|---|---|---|
| #695 fix(Application): catch all craft-like errors | craft-application | merged | Merged after resolving #693. Catches craft-like errors during execution, duck-types them, and converts them to CraftError instances instead of internal errors. Approved by two reviewers with passing CI checks. |