Issue-fixer pipeline should auto-file infrastructure bugs on novel pipeline errors instead of silently blocking #61

New issue

Closed

opened 2026-05-13 04:44:45 +00:00 by Mark · 1 comment

Mark commented

2026-05-13 04:44:45 +00:00

Owner

Description

When the GSD pipeline hits a novel infrastructure error (commit gate fails due to pre-commit hook / gitignore / auth / etc.), it records the issue as BLOCKED and moves on. It does NOT file a bug report documenting the error, so:

The blocked issue languishes until someone notices and manually investigates
No tracking issue exists for the underlying infrastructure bug
The pipeline can hit the same failure on subsequent issues without escalation

Example

devforge#3 hit commit: fail because the GSD pipeline writes to .gsd/gate-state.json which is tracked by git, causing pre-commit's end-of-file-fixer to conflict with stashed changes. The pipeline knew:

Which gate failed (commit)
Why (pre-commit hook modified tracked gate-state.json)
What was affected (devforge#3)

But it only recorded BLOCKED with a descriptive reason. It should have also filed Mark/infrastructure#N documenting the root cause and linked the affected issue.

Required Behavior

On the first occurrence of a novel pipeline error type:

Detect novelty — check infrastructure repo for existing issues matching the error signature (title prefix "GSD pipeline..." or known error_type)
Auto-file — if not found, create a new infrastructure issue with:
- Title describing the failure
- The pipeline log showing the symptom
- Which issue(s) were affected
- Suggested fix or what's known
Label — apply bug label
Link — comment on the blocked Forgejo issue referencing the infrastructure bug

This prevents silent blocking and ensures infrastructure problems are tracked without manual discovery.

Error Type

auto-file-infra-bugs

Suggested Implementation

Add a function to gsd-issue-executor.py (or the orchestrator) that:

On commit gate failure, extracts the failure reason from the git/commit output
Searches infrastructure issues for a matching open bug
If none exists, files one using the Forgejo API (token already available in the script)
Records the infra issue number in the state file for correlation

## Description When the GSD pipeline hits a novel infrastructure error (commit gate fails due to pre-commit hook / gitignore / auth / etc.), it records the issue as `BLOCKED` and moves on. It does NOT file a bug report documenting the error, so: - The blocked issue languishes until someone notices and manually investigates - No tracking issue exists for the underlying infrastructure bug - The pipeline can hit the same failure on subsequent issues without escalation ## Example devforge#3 hit `commit: fail` because the GSD pipeline writes to `.gsd/gate-state.json` which is tracked by git, causing pre-commit's `end-of-file-fixer` to conflict with stashed changes. The pipeline knew: - Which gate failed (commit) - Why (pre-commit hook modified tracked gate-state.json) - What was affected (devforge#3) But it only recorded `BLOCKED` with a descriptive reason. It should have also filed `Mark/infrastructure#N` documenting the root cause and linked the affected issue. ## Required Behavior On the first occurrence of a novel pipeline error type: 1. **Detect novelty** — check infrastructure repo for existing issues matching the error signature (title prefix "GSD pipeline..." or known error_type) 2. **Auto-file** — if not found, create a new infrastructure issue with: - Title describing the failure - The pipeline log showing the symptom - Which issue(s) were affected - Suggested fix or what's known 3. **Label** — apply `bug` label 4. **Link** — comment on the blocked Forgejo issue referencing the infrastructure bug This prevents silent blocking and ensures infrastructure problems are tracked without manual discovery. ## Error Type `auto-file-infra-bugs` ## Suggested Implementation Add a function to `gsd-issue-executor.py` (or the orchestrator) that: - On commit gate failure, extracts the failure reason from the git/commit output - Searches infrastructure issues for a matching open bug - If none exists, files one using the Forgejo API (token already available in the script) - Records the infra issue number in the state file for correlation