feat: --from-step retry, pause-on-failure UI, and step log segmentation#37
Merged
feat: --from-step retry, pause-on-failure UI, and step log segmentation#37
Conversation
Allows rewinding to an earlier step when retrying a paused runner: - --from-step <N>: skip steps before N, re-run from step N onwards - --from-start: re-run all run: steps from the beginning Each wrapped step embeds a 1-based index matching the tree UI and checks a from-step signal file on entry. Steps below the target exit 0 (skip), the matching step deletes the signal and continues. Closes #35
When a step pauses on failure, the tree UI now shows: - Last 20 lines of step output below the tree (assertion errors, code context, etc.) matching the end-of-job summary quality - Press Enter to retry directly from the paused terminal - Ctrl+C to abort The step log is resolved via sanitized name with fallback to the most recently modified .log file (the DTU writes logs under feed UUIDs that differ from timeline record IDs).
The runner sends step output via the Job-level feed (Job UUID as recordId), which the DTU couldn't map to a step name. Now the timeline handler tracks the currently in-progress step, and writeStepOutputLines falls back to it when the feed recordId has no direct mapping. This gives failing/paused steps their own properly named log files (e.g. Run-assertion-test.log) instead of an opaque UUID file. Also adds Enter-to-retry: pressing Enter in the terminal while paused triggers a workspace sync and retry signal directly.
peterp
added a commit
that referenced
this pull request
Mar 16, 2026
feat: --from-step retry, pause-on-failure UI, and step log segmentation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #35
Changes
--from-stepand--from-startformachinen retrymachinen retry --from-step 3skips steps 1–2 and re-runs from step 3 onwardsmachinen retry --from-startre-runs from the firstrun:stepPause-on-failure UI improvements
DTU step log segmentation
Run-assertion-test.log) instead of opaque UUID filesTesting
retry-proofworkflow