Repository navigation
receipt(OMN-13693): bind DLQ topic prefix constant fix evidence to omnimarket PR - #3274
Conversation
|
Warning Review limit reached
More reviews will be available in 30 minutes and 6 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 |
…nimarket PR Contract + dod_evidence for OMN-13693 (replace hardcoded "onex.dlq." string literal with DLQ_TOPIC_PREFIX named constant in node_pipeline_audit_orchestrator). dod-001: three regression-guard tests pass — constant importable, DLQ topics excluded from findings, handler source contains no bare literal (7417 non-kafka tests green, mypy --strict clean, all pre-commit hooks pass). dod-occ-self: self-binding receipt for the OCC pairing.
a581a05 to
0e92866
Compare
Summary
OCC pairing for OMN-13693 — replace hardcoded
"onex.dlq."string literal withDLQ_TOPIC_PREFIXnamed constant innode_pipeline_audit_orchestratorhandler.contracts/OMN-13693.yaml— ticket contract withdod_evidenceentriesdrift/dod_receipts/OMN-13693/dod-001/command.yaml— three regression-guard tests PASSdrift/dod_receipts/OMN-13693/dod-occ-self/command.yaml— self-binding receiptEvidence-Source
Evidence-Source: a581a053d5ce1a7e36c4f70eebd22a530add1410Evidence-Ticket: OMN-13693DoD Evidence
dod-001:DLQ_TOPIC_PREFIXimportable, equals"onex.dlq.", handler source has no bare literal, DLQ topics produce zero "no consumer" findings — all 3 new tests PASS; 7417 non-kafka tests green; mypy --strict clean; all pre-commit hooks pass on staged filesdod-occ-self: contract + receipt files present in this PREvidence-Ticket: OMN-13693
Evidence-Source: OCC#3274