Repository navigation
fix(OMN-13701): update kafka boundary registry — intent-classified consumer moved to omnimarket - #3324
fix(OMN-13701): update kafka boundary registry — intent-classified consumer moved to omnimarket#3324jonahgabriel wants to merge 2 commits into
Conversation
|
Warning Review limit reached
More reviews will be available in 10 minutes and 15 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?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 credits. 🚦 How do rate 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 see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
The intent-classified.v1 Kafka boundary consumer moved from omnimemory to omnimarket (OMN-13701). Update the boundary-parity CI repos list to include omnimarket so it gets cloned during the check — required once onex_change_control@main is updated to reflect the new consumer location. Companion PR: OmniNode-ai/onex_change_control#3324
… omnimarket omnimemory removed node_intent_event_consumer_effect/contract.yaml in OMN-13701 (PR #386). The consumer for onex.evt.omniintelligence.intent-classified.v1 moved to omnimarket (where node_intent_event_consumer_effect/contract.yaml exists). Update kafka_boundaries.yaml to reflect the live consumer location. Add omnimarket to the validate-boundaries action default repos list so CI can clone it when checking this boundary. This unblocks Cross-Repo Boundary Parity CI check across all omniclaude PRs.
f1b43ce to
f83469a
Compare
OCC preflight requires a PASS receipt binding to the current PR number or one of its commit SHAs. The existing dod-001 and dod-boundary-registry receipts bound to PRs #3285 and #3312 (the initial OCC and dev-side fix). Rebind both receipts to PR #3324 (cherry-pick of #3312 fix onto dev HEAD) so the OCC preflight eligibility check passes. Evidence-Ticket: OMN-13701 Evidence-Source: omnimemory#386
|
Closing in favor of a new PR from the correctly-named branch (jonah/omn-13701-fix-intent-boundary-registry) — Receipt Gate identity binding requires the branch to contain OMN-13701. New PR will replace this one. |
1 participant
Summary
kafka_boundaries.yamlonmaindeclaredconsumer_repo: omnimemoryforonex.evt.omniintelligence.intent-classified.v1.omnimemory/src/omnimemory/nodes/node_intent_event_consumer_effect/contract.yaml.omnimarket/src/omnimarket/nodes/node_intent_event_consumer_effect/contract.yamlexists and references the topic.Impact: This stale entry causes
Cross-Repo Boundary Parityto fail for ALL omniclaude PRs. Systemic CI blocker.Changes
kafka_boundaries.yaml: consumeromnimemory→omnimarket, update consumer_file path.action.yml: addomnimarketto default repos list.Evidence-Ticket: OMN-13701
Evidence-Source: omnimemory#386