Repository navigation
evidence(OMN-15349): OCC companion for OmniNode-ai/omninode_infra#818 - #6124
jonahgabriel wants to merge 2 commits into
Conversation
Manual net-new-file evidence companion — the automated node_occ_companion_effect path fired (GHA publish succeeded, event_id=dcc3e902 at 2026-08-05T21:24:06Z, consumed on .201 omninode-runtime-effects) but the mint dispatcher failed (SupersessionCheckBindingError, preceded by "Secret resolution failed (configuration issue): GITHUB_TOKEN"), boundary-swallowed with dlq_routed=false — a live, ongoing outage confirmed hitting every node_occ_companion_effect attempt on .201 across 21:31Z/21:41Z/21:55Z (100% failure in that window), not specific to this PR. Binds OmniNode-ai/omninode_infra#818 (OMN-15349 follow-up to #817: rebuilds + re-pins k8s/migrations/omnibase-infra-migrate.yaml to omnibase_infra dev@a853500a, the first migrate image built from a commit carrying docker/migrations/forward/fenced-node-migrations.yaml) to the existing OMN-15349 contract, appending three dod_evidence entries plus their receipts. Self-bind entry to follow once this PR's number is known. OMN-15349
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 22 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (5)
Comment |
Manual net-new-file evidence companion for OmniNode-ai/omninode_infra#818 (OMN-15349).
The automated node_occ_companion_effect path fired for this PR (GHA
call-occ-companion-effect / occ-companion-effectjob 31048451864 succeeded, publishingonex.cmd.omnimarket.occ-companion-effect-requested.v1event_id=dcc3e902 at 2026-08-05T21:24:06Z; the .201 dev-lane effects runtime consumed it immediately) but the mint dispatcher failed downstream:dispatcher.auto.node_occ_companion_effect.HandlerOccCompanionEffect...raisedSupersessionCheckBindingErrorat 21:24:10Z, immediately preceded bySecret resolution failed (configuration issue): GITHUB_TOKEN, and was boundary-swallowed (metric_name=boundary_swallow_observed dlq_routed=false dlq_enabled=False) — no completed/failed event, nothing stamped back onto #818.Live-verified this is a currently-active, cross-PR outage, not specific to #818: every
node_occ_companion_effectattempt observed onomninode-runtime-effectsin the 21:31Z/21:41Z/21:55Z window (OCC#6122, omninode_infra#819, omnibase_infra#2663) hit the sameGITHUB_TOKENsecret-resolution failure — 100% failure rate in that window. Automated retrigger was not attempted given that live evidence.Evidence-Source: OmniNode-ai/omninode_infra#818 @ cb0208badf7a81f4ca97a2995d88b90f06440900
OMN-15349