Skip to content

🐝 Governor opens a Hive Advisory Report in every monitored repo instead of only the primary #18568

Closed

Description

@clubanderson

What happened

After the hivecommons hive rolled onto candidate 5b5921e (from 8389f7f) at about 00:10 UTC on 2026-11-17, the governor opened a [governor] 🐝 Hive Advisory Report issue in every non-primary monitored repo: crux#156, dibs#676, docs#732, hivecommons.github.io#392, homebrew-hive#334, hotshot#379, pluk#516, promptargs#477, quorum#28 and rationguard#536. It also tried vexa, where Issues are disabled. The only advisory report should be #2364.

Root cause

Commit 8f0a2f6 (#18534, for #18448) added ensureSecondaryAdvisoryIssues and postAdvisoryDigestToSecondaryRepos in src/cmd/hive/advisory_repo_issues.go. They are wired into runEvalCycle in src/cmd/hive/main_eval_cycle.go, and every eval cycle they ensure, and so create, an advisory issue in every repo in project.repos other than project.primary_repo.

Restarts make the problem worse. findAdvisoryIssueListed reopens a closed advisory issue (#4167). So after a duplicate is closed, the next restart of an affected build reopens it.

Expected

Exactly one advisory report per hive, in project.primary_repo, deduped against the existing open report (title plus label) so a restart never re-creates it. No advisory issue, ensure or digest post in any non-primary repo.

Note

This reverses the per-repo behavior #18448 asked for. The operator ruled that a hive keeps a single advisory report in its primary repo.

Activity

  1. self-assigned this
    on Nov 17, 2026
  2. clubanderson commented on Nov 17, 2026

    @clubanderson
    MemberAuthor

    Claimed: an operator-dispatched agent is working on this now. Hive agents, please do not pick it up.

  3. added a commit that references this issue on Nov 17, 2026
    d0d9f8d
  4. clubanderson commented on Nov 17, 2026

    @clubanderson
    MemberAuthor

    Status update.

  5. github-actions commented on Nov 17, 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

kind/bugCategorizes issue or PR as related to a bug.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