Skip to content

Show failed pipeline stages after their active solver is cleared - #34

Open
ugin-man wants to merge 1 commit into
tscircuit:mainfrom
ugin-man:codex/fix-failed-stage-status
Open

ugin-man wants to merge 1 commit into
tscircuit:mainfrom
ugin-man:codex/fix-failed-stage-status

Conversation

@ugin-man

@ugin-man ugin-man commented Sep 7, 2026

Copy link
Copy Markdown

When a stage reports failure, BasePipelineSolver sets its own failed flag and clears activeSubSolver. The stage table then classifies the current stage as “Not Started”, hiding the failure. A stage constructor that throws has the same result because no active solver is assigned.

Check the pipeline's failure flag for the current stage before inspecting the active solver. Later stages remain “Not Started”, and normal initialization still transitions to “In Progress”.

Validation: two regressions using actual pipeline execution fail before the fix. All 25 tests (96 assertions), tsc --noEmit, and bun run build pass after the change.

Prepared with Codex (Astra) assistance and verified locally.

@vercel

vercel Bot commented Sep 7, 2026

Copy link
Copy Markdown

@ugin-man is attempting to deploy a commit to the tscircuit Team on Vercel.

A member of the Team first needs to authorize it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant