Skip to content

tracker: chevron says "Merge queued · 1st" while caption says CI still running / verdict pending #15580

Closed

Description

@clubanderson

What happened

Activity Monitor tracker row for #15575 → PR #15577 (human-authored, base v5), owner screenshot 20:01 EDT:

  • Chevron (lit segment): 🕓 Merge queued · 1st
  • Caption: Covered by PR #15577 — Review swarm requested; waiting for a verdict on the current head — check build-and-test still running

Owner: "which is correct?"

Which one was correct

The caption. Live tracker item: stage: 50 (review pending), reason: required-check-pending:build-and-test; gh pr view 15577 showed build-and-test IN_PROGRESS, no reviews, mergeStateStatus: BLOCKED. The PR was not mergeable; it was merely ordered first in a 2-PR merge train (overlapping file tracker-words.js).

Root cause

stageTrackerMergeTrainPostPass marks the front of a train from sibling records at any stage < 110, setting merge_gate.state = front, reason "1st in the merge queue; merges next". The SPA (stageTrackerMergeGateInfoFor, stageTrackerTrainWord) paints the train word over the stage word whenever merge_train is present. So the chevron shows a future queue slot while the caption shows the current blocker — a model conflict, not stale data.

Expected

Headline on the active chevron always describes the current blocker (stage-first). A train position for a PR below merge-ready (stage < 080) is a trailing muted suffix (… · queued 1st once ready), the gate reason says "merges first once it is ready", and the server flags such entries merge_train.provisional: true. Chevron and caption must never contradict.

Activity

  1. added
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    on Oct 30, 2026
  2. github-actions commented on Oct 30, 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.

  3. added a commit that references this issue on Oct 30, 2026
    b689da1
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

    help 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