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
🐝 Governor opens a Hive Advisory Report in every monitored repo instead of only the primary #18568
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.
Effective config checked: project.primary_repo: hive. The code never falls back to all repos when the primary is unset; PrimaryRepo uses repos[0].
Closed 10 duplicates as not planned: crux#156, dibs#676, docs#732, hivecommons.github.io#392, homebrew-hive#334, hotshot#379, pluk#516, promptargs#477, quorum#28, rationguard#536. 🐝 Hive Advisory Report #2364 and the older spektacular#30 were left alone. [governor] 🐝 Hive Advisory Report torch-spyre/torch-spyre#6381, opened by a standalone hive on 645f107, is still open; its owner will close it.
Affected builds: 5b5921e, 645f107 and the current candidate 69120c5 contain 8f0a2f6. Current stable e963c42 and the next eligible stable b0c5d1c do not.
Risk until a candidate with the fix ships: a restart or candidate roll on a buggy build reopens the closed duplicates, because a closed advisory issue is reused (🐛 certus: advisory digest stale since 2026-08-13 (not refreshing) #4167). Any hive auto-upgrading onto candidate 69120c5 gets the bug.
@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
clubanderson commentedon Nov 17, 2026
Claimed: an operator-dispatched agent is working on this now. Hive agents, please do not pick it up.
🐛 Keep exactly one advisory report per hive, in the primary repo
clubanderson commentedon Nov 17, 2026
Status update.
project.primary_repois ever ensured.project.primary_repo: hive. The code never falls back to all repos when the primary is unset;PrimaryRepousesrepos[0].645f107, is still open; its owner will close it.5b5921e,645f107and the current candidate69120c5contain 8f0a2f6. Current stablee963c42and the next eligible stableb0c5d1cdo not.69120c5gets the bug.github-actions commentedon Nov 17, 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.✨ Governor: opt-in advisory report in every repo (default off) (#18583)