Skip to content

fix: end run Setup at a bare count - #1148

Merged
small-angel merged 1 commit into
mainfrom
clo/setup-bare-count
Nov 20, 2026
Merged

small-angel merged 1 commit into
mainfrom
clo/setup-bare-count

Conversation

@small-angel

Copy link
Copy Markdown
Contributor

A run that only prints a bare counter like ::orx:: {"step":10,"of":100} (no named stage, no charted metric) stayed in "Setup · Step 10 of 100" for its whole life. The first bare count now ends Setup on the run line, card, run page, orx exp status and the watcher, the same way a named stage's count does since #1123.

Before After
Run line before Run line after

Assisted-by: gpt-6.2-sol
Assisted-by: claude-opus-5.5

Treat an explicit step as the start of work even without a stage name.
Remember the count when its stage ages out of the checkpoint so the
dashboard, status command and watcher share the same Setup boundary.

Assisted-by: gpt-6.2-sol
Assisted-by: claude-opus-5.5
@greptile-apps

greptile-apps Bot commented Nov 20, 2026 •

Copy link
Copy Markdown
Contributor

RetriggerView in GreptileConfidence Score: 5/5

[Medium impact] The PR appears safe to merge; no actionable issues were found.

Summary

Bare declared step counts now end Setup through the shared monitor.

  • Runs with bare step counts now leave Setup.

Review was based on source inspection. Tests and visual checks were not run.

Reviews (1) · Last reviewed commit: "fix: end run Setup at a bare count" · Reviewed by Greptile

@small-angel
small-angel merged commit ebb1539 into main Nov 20, 2026
28 checks passed
@small-angel
small-angel deleted the clo/setup-bare-count branch November 20, 2026 02:42
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