Skip to content

Activity Monitor: row lights two stage chevrons (CI + Review) after a push, with jargon detail line and opaque "stage ↓" pill #17335

Closed

Description

@clubanderson

What happened

Operator dashboard, Activity Monitor, 2026-11-09 01:50Z: issue #17292 with PR #17308, right after @Karibhou pushed c15a343.

The row lit two chevrons in the active amber style at once — "CI 7/11 · 4 running" and "Review 5/5 · adjudicating" — with a pill "@Karibhou pushed c15a343 · re-review pending · 3m", a pill "stage ↓", and an expander detail line:

push seen 3m ago → CI/re-review queued · Recorded preparation owner · unverified · Head changed; current preparation unverified · ticket age 4m · shown under issue #17292

A minute earlier the same row lit only "Review 5/5 · ci-maintainer…". Operator: "this is confusing".

Root cause

stageTrackerActivityTrackHtml decided lit = running || stageTrack || stalled per track independently, and the chevron rules (#16599 / #16643) allowed "1 ≤ active ≤ 2" with CI + Review as the permitted pair. At stage 050 after a push, CI is running and Review is the stage's own track (verdict unsettled → adjudicating), so both lit. The server legitimately carries both sub-states; the client never picked a lead.

The detail line concatenates the scheduler's internal preparation-ticket vocabulary (Recorded preparation owner · unverified, server Detail "Head changed; current preparation unverified", "ticket age") verbatim — "unverified" twice. The stage ↓ pill is the hive-handled regression marker; the glyph reads like a sort control.

Fix

  1. Exactly one lit stage per row: derive one lead track (CI before Review); the other renders dim with a muted note ("re-review queued" after a push, "review in progress", "review queued"), words in the tooltip.
  2. Detail line in operator words: "New push c15a343 by @Karibhou 3m ago → CI running, review will rerun · previous review no longer applies · Recorded first for the base refresh · ticket issued for an earlier head · re-checked on c15a343 · ticket issued 4m ago" — no "preparation"/"unverified".
  3. Pill reads "stage reset" / "stage reset by push".
  4. Chevron semantics doc: "exactly one lit stage per row; later stages shown dim with a queued note".

Activity

  1. added
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    on Nov 9, 2026
  2. hivecommons-hive commented on Nov 9, 2026

    @hivecommons-hive
    Contributor

    🔒 Claimed by @Karibhou (contributor on hive hosted-available-oke-11-placeholder-r05x). The claim lasts 30m0s without activity and renews while the work continues. Reply /unclaim to release, or /claim to take it over if you outrank the holder.

    Claim history
    • 2026-11-09 02:09 UTC — claimed by Karibhou (contributor on hive hosted-available-oke-11-placeholder-r05x)
  3. Karibhou commented on Nov 9, 2026

    @Karibhou
    Contributor

    Covered by open PR #17337 (fix/one-lit-stage → v5, ready for review, mergeable, body carries Fixes #17335). It implements all four items from the issue: a single lead track per row (CI before Review, other track dim with a queued note), a plain-language detail line in tracker-preparation.js with no preparation/unverified/ticket age wording, the stage ↓ pill renamed to stage reset / stage reset by push, and updated chevron docs, with Go and JS tests. I'm not opening a duplicate PR.

    — hive: backend=omp model=anthropic/claude-opus-5-5


    🐝 Hive Agent: contributor | SHA: 68f8dd297

  4. github-actions commented on Nov 9, 2026

    @github-actions
    Contributor

    @clubanderson this issue was closed by @hivecommons-hive[bot] as completed.

    If this was closed by a merged PR, the fix only takes effect once it ships in a tagged release and your deployment updates to it — check your running version against the fix before concluding the fix failed.

    If you are still seeing the problem, comment /reopen and it will be reopened for you — you do not need write access. Please add what you are still observing (running version, logs, steps) so it is not closed the same way again.

  5. added a commit that references this issue on Nov 9, 2026
    c4abd0f
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workinghas-open-prhelp wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions