Skip to content

[deep-report] Audit and wrap upstream YAML errors in the parser import pipeline (%w) #46265

Description

@github-actions

Description

The [repository-quality] report (discussion #46253) found 788 non-wrapping fmt.Errorf calls (37% of all fmt.Errorf), concentrated in pkg/workflow (375), pkg/cli (286), pkg/parser (93). In the parser import pipeline, a structured upstream error (e.g. YAML/ImportError) often exists but is swallowed by a fresh fmt.Errorf, so errors.Is/errors.As cannot inspect the real cause. Audit the parser import path and convert applicable non-wrapping fmt.Errorf calls to use %w on the genuine upstream cause.

Expected Impact

User-visible import errors retain their cause chain; programmatic classification and stacktraces stop going opaque.

Suggested Agent

Copilot SWE Agent (Go refactor specialist) or Duplicate/Compiler Quality agent.

Estimated Effort

Medium (1-4 hours).

Data Source

DeepReport 2026-07-17 - [repository-quality] discussion #46253 Task 2. Dedup-checked: no open issue covers parser-pipeline error wrapping.

Generated by 🔬 Deep Report · 208.7 AIC · ⌖ 11.4 AIC · ⊞ 10K ·

  • expires on Jul 19, 2026, 7:16 AM UTC-08:00

Metadata

Metadata

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions