You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Observed (hive's hive dashboard, v5 rev 794d97e, 2026-10-28 13:09Z): hovering the nested PR sub-row for #14787 ("dco: re-home unsigned commits on adopted PRs so the gate can clear", stage Needs a human decision, flag needs-human) the tooltip ends with:
Root cause: stageTrackerTooltip in src/pkg/dashboard/static/index.html builds the trail with String(h.stage).padStart(3, '0'), but the server's StageTrackerHop (src/pkg/dashboard/stage_tracker.go) emits {number, slug, at, reason, from, regressed} — there is no stage field, so every hop stringifies to undefined. Live payload for #14787:
The Go UI test fixtures used history: [{stage:50},...], so they matched the SPA rather than the wire shape and never caught it.
Fix: read number/slug, render stage names ("CI / Review → Needs author → CI / Review → Needs human decision"), skip hops that cannot be named instead of printing undefined, omit the "Trail:" clause when fewer than two hops can be named; test the hop shape on both sides.
@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.
Activity
github-actions commentedon Oct 28, 2026
@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
/reopenand 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.