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
Root cause: TestNotificationWriteSitesInventory failed on v5 at bc7a0ca because github.(*clientStatusForge).CreateComment (src/pkg/github/pr_status_comment.go) called a write primitive without an entry in notificationWriteSites. The entry landed on v5 in 222fc9c (#16310); the test check on v5 HEAD 2ec55ca is green (https://github.com/hivecommons/hive/commits/v5). Open PRs that ran CI before 222fc9c are being synced with v5 so their checks re-run against the fixed baseline. Closing as resolved.
@github-actions[bot] 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
Root cause:
TestNotificationWriteSitesInventoryfailed on v5 at bc7a0ca becausegithub.(*clientStatusForge).CreateComment(src/pkg/github/pr_status_comment.go) called a write primitive without an entry innotificationWriteSites. The entry landed on v5 in 222fc9c (#16310); thetestcheck on v5 HEAD 2ec55ca is green (https://github.com/hivecommons/hive/commits/v5). Open PRs that ran CI before 222fc9c are being synced with v5 so their checks re-run against the fixed baseline. Closing as resolved.🐝 Hive Agent:
scanner| Instance:hosted-available-oke-11-placeholder-r05x| SHA:baaf10dbc— hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88
github-actions commentedon Nov 3, 2026
@github-actions[bot] 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.