Skip to content

[v6] 🐛 multi-hub standby relay rejects donated work: hub is not the active polling slot #16422

Closed

Description

@onkar717

A relay subscribed to more than one hub rejects donated standby work from any hub that isn't its active polling slot. Standby dispatch fails on the relay side, even though the hub has already accepted the relay's standby declaration.

What I did

  • Relay from upstream/v6 1a0363a, local mode, subscribed to two hubs: the hosted hive, which doesn't advertise standby_v1, and my self-hosted kind hive, which does.
HIVE_STANDBY=1 HIVE_STANDBY_LANES=guide AGENT_MODEL=claude-sonnet-5-5 AGENT_REASONING_EFFORT=medium just contribute-hive claude local

The relay logged Standby acknowledged by ws://127.0.0.1:13002/api/contribute/ws: 1 accepted, 0 rejected. As owner, I dispatched one item:

POST /api/contribute/standby/dispatch {"lane":"guide","key":"onkar717/hive-playground#22"}
200 {"ok":true,"standby_lane":"guide","standby_tier":"T2","task_id":"ct-onkar717/hive-playground-22-1793706192"}

What happened

The hub records the task as failed within a second (/api/contribute/runs):

"outcome":"failed","reason":"Hub is not the active polling slot","duration_s":0.77

Why

bin/contributor-relay.js, task_assign:

if (!currentTask && hub !== hubs[activeHubIndex]) {
  console.log(`Rejecting task ... — hub is not the active polling slot`);
  sendTo(hub, { type: 'task_failed', ..., reason: 'Hub is not the active polling slot' });

That guard makes sense for work the relay asked for with ready. A standby assignment is pushed by the hub the relay declared standby to, though, and that hub is never the active polling slot here: the relay doesn't poll in standby mode, and activeHubIndex points at the hosted hub.

Expected

An assignment with standby_lane set, from a hub that acknowledged this relay's standby, is accepted whatever the active polling slot is. Or the active slot follows the hub that has an acknowledged standby. A single-hub relay never hits this, so the keyless stub CI tier that runs one hub won't catch it.

Activity

  1. added
    needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.
    on Nov 3, 2026
  2. hivecommons-hive commented on Nov 3, 2026

    @hivecommons-hive
    Contributor

    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.

  3. added
    help wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
    on Nov 3, 2026
  4. added
    stage/015-triage-neededActionable but no maintainer has looked at it yet (hive-filed, or awaiting the triage label)
    triage/acceptedIndicates an issue or PR is ready to be actively worked on.
    stage/020-claimedClaimed by the scanner or a relay contributor
    and removed
    needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.
    stage/015-triage-neededActionable but no maintainer has looked at it yet (hive-filed, or awaiting the triage label)
    stage/020-claimedClaimed by the scanner or a relay contributor
    on Nov 3, 2026
  5. hivecommons-hive commented on Nov 3, 2026

    @hivecommons-hive
    Contributor

    🔓 Claim by agent scanner released (holding agent relaunched).

    Claim history
    • 2026-11-03 19:56 UTC — claimed by scanner (agent on hive hosted-available-oke-11-placeholder-r05x)
    • 2026-11-03 20:14 UTC — released by scanner (agent; holding agent relaunched)
  6. added
    stage/010-actionableTriaged; eligible for the hive to pick up
    stage/020-claimedClaimed by the scanner or a relay contributor
    and removed
    stage/010-actionableTriaged; eligible for the hive to pick up
    stage/020-claimedClaimed by the scanner or a relay contributor
    on Nov 3, 2026
  7. hivecommons-hive commented on Nov 3, 2026

    @hivecommons-hive
    Contributor

    Fixed by #16462 (merged 8dcf9f8). Closing. Reply /reopen if the problem persists.

  8. github-actions commented on Nov 3, 2026

    @github-actions
    Contributor

    @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.

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.triage/acceptedIndicates an issue or PR is ready to be actively worked on.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions