Spec and prototype omitting the traceback for known user errors
Metadata
Current evaluation
Design mechanism to suppress craft-tool tracebacks in logs/terminal for known user errors such as plugin build failures; open, unlabelled, internal ticket CRAFT-3655 created.
Suggested action: keep open
Reason: Maintainer-authored design task with a clear goal and rationale, and the bot comment confirms internal ticket CRAFT-3655. Code inspection shows runtime errors are still centrally emitted via handle_runtime_error with no traceback-suppression mechanism for known user errors, so the work remains valid.
Evaluated by: mr-cal-bot
Impact:
50
Quick Win:
10
Complexity:
65
Confidence:
60
Actionability:
55
Issue body
### What needs to get done
Design a mechanism to avoid outputting the craft-tool traceback (to the log file and terminal) in case the error happens for a cause that we know for sure isn't a bug (e.g. a plugin build failure).
### Why it needs to get done
The current log is super noisy and makes it hard to find the "true" cause of a failure:
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| ~deepseek/deepseek-pro-latest |
Impact:
50
Quick Win:
10
Complexity:
65
Confidence:
60
Actionability:
55
|
keep open | Design mechanism to suppress craft-tool tracebacks in logs/terminal for known user errors such as plugin build failures; open, unlabelled, internal ticket CRAFT-3655 created. | |
| ~deepseek/deepseek-pro-latest |
Impact:
55
Quick Win:
11
Complexity:
65
Confidence:
60
Actionability:
55
|
keep open | Maintainer spec to suppress craft-tool tracebacks for known user errors such as plugin build failures, since noisy logs obscure the real cause. No implementation yet. | |
| stealth/space-bunny-alpha |
Impact:
35
Quick Win:
7
Complexity:
55
Confidence:
72
Actionability:
45
|
keep open | Enhancement request from a maintainer to design a mechanism suppressing the craft-application traceback for known non-bug errors (e.g. plugin build failure), since noisy logs obscure the real cause. Still open, no implementation. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
7
Complexity:
60
Confidence:
60
Actionability:
60
|
needs triage | Design mechanism to suppress tracebacks for known user errors (e.g., plugin build failures) to reduce log noise. Open, unlabelled, no maintainer response. | |
| qwen/qwen3.8-27b |
Impact:
45
Quick Win:
18
Staleness:
75
Complexity:
60
Confidence:
60
Support Request:
10
|
needs triage | Design a mechanism to suppress craft-tool tracebacks for known user errors (e.g. plugin build failures) to reduce log noise. Open since 2023, tracked as CRAFT-3655, no maintainer response beyond the Jira sync bot. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
85
Complexity:
50
Confidence:
85
Support Request:
10
|
needs triage | Design task to suppress tracebacks for known user errors to reduce log noise. Currently unlabelled, inactive for over a year, and awaiting maintainer assessment. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
85
Complexity:
40
Confidence:
80
Support Request:
10
|
needs triage | Design a mechanism to suppress tracebacks for known user errors to reduce log noise. Currently unlabelled, inactive for over a year, and awaiting maintainer assessment. |
Update history
No update history recorded yet.
Related issues
No related issues found above the similarity threshold.