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
{{ message }}
Repository navigation
[v6] 🐛 standby tile counts an item for a lane that dispatch then refuses (lane split mismatch) #16420
The standby tile and /api/contribute/standby/dispatch don't agree on which lane an item is in. The tile can say a lane has an item that 1 contributor qualifies for, and the dispatch to that lane then refuses it as not dispatchable.
What I did
Self-hosted v6 hive on kind, :edge1a0363a. Standby was on for lane scanner, floor T2, and my relay was standing by on a configuration mapped to T2. One actionable issue, onkar717/hive-playground#22 (label bug).
So the tile reads scanner paused, out of budget, 1 waiting, 1 qualify. Then:
POST /api/contribute/standby/dispatch {"lane":"scanner","key":"onkar717/hive-playground#22"}
400 {"error":"standby item \"onkar717/hive-playground#22\" is not dispatchable","ok":false}
POST /api/contribute/standby/dispatch {"lane":"scanner"}
400 {"error":"no dispatchable standby item in lane \"scanner\"","ok":false}
/api/contribute/queue puts that one issue in "lane":"guide". With standby moved to guide, the same issue qualified and passed the lane check.
Why
On upstream/v6:
buildLaneQueueDepths (src/pkg/dashboard/status_builder.go) counts every actionable issue for scanner. For other lanes it counts issues whose Lane matches or is empty. So the same issue is counted in more than one lane.
standbyLaneItems (contribute_ws.go) mirrors that split, per its comment, so qualified_standbys follows it too.
standbyDispatchItem (contribute_standby_dispatch.go) matches on the admission queue item's Lane exactly, so only the one lane that item is routed to can dispatch it.
Expected
"N waiting, M qualify" should count only the items the lane can dispatch. Or the dispatch should accept the same items the tile counts. Today the tile can show a qualifying contributor for work the operator then can't hand them, on the one surface that's meant to state facts. If counting every issue for scanner is intended for its triage cadence, standby could use the admission queue's lane instead of reusing that depth.
Thanks — this hive only works issues from OWNER, MEMBER, COLLABORATOR automatically. A maintainer can admit this one by adding the label triage/accepted (configured in issue_filter.reporter_trust.untrusted_require_labels). Until then the hive will not claim, label, or open PRs for it. See https://github.com/hivecommons/hive/blob/HEAD/GOVERNANCE.md#reporter-trust-and-escalation for what these terms mean and how to become a trusted reporter.
🔒 Claimed by @mrbobbytables (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.
@onkar717 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
hivecommons-hive commentedon Nov 3, 2026
Thanks — this hive only works issues from OWNER, MEMBER, COLLABORATOR automatically. A maintainer can admit this one by adding the label
triage/accepted(configured inissue_filter.reporter_trust.untrusted_require_labels). Until then the hive will not claim, label, or open PRs for it. See https://github.com/hivecommons/hive/blob/HEAD/GOVERNANCE.md#reporter-trust-and-escalation for what these terms mean and how to become a trusted reporter.hivecommons-hive commentedon Nov 3, 2026
🔒 Claimed by @mrbobbytables (contributor on hive hosted-available-oke-11-placeholder-r05x). The claim lasts 30m0s without activity and renews while the work continues. Reply
/unclaimto release, or/claimto take it over if you outrank the holder.📖 docs: clarify standby tile lane queue
hivecommons-hive commentedon Nov 3, 2026
🔓 Claim by @mrbobbytables released (lease revoked).
🐛 fix: align standby qualification with dispatch queue (#16450)
hivecommons-hive commentedon Nov 3, 2026
Fixed by #16450 (merged 3820712). Closing. Reply /reopen if the problem persists.
github-actions commentedon Nov 3, 2026
@onkar717 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.