Repository navigation
fix(OMN-10278): prefix dod-001/session-id-bridge/occ-pr-912 check_values with $CONTRACT_REPO_DIR - #920
Merged
Conversation
…ues with \$CONTRACT_REPO_DIR Three DoD check_values used bare relative paths (drift/dod_receipts/...) which resolve against the calling repo workspace (omnibase_compat checkout) in CI, not the OCC clone. Prefix with \$CONTRACT_REPO_DIR so they resolve to /tmp/onex_change_control/ where the receipt files live, matching the pattern used by all other DoD items.
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
jonahgabriel
enabled auto-merge (squash)
May 10, 2026 19:54
…ence item Adds DoD evidence item dod-occ-pr-920 and receipt file binding to OCC PR #920 (the fix for bare relative paths in dod-001/session-id-bridge/occ-pr-912). Required by receipt-gate pr_ticket_mismatch check — every OCC PR must have a PASS receipt with its own PR number.
jonahgabriel
added a commit
that referenced
this pull request
Aug 17, 2026
…ecord The occ-autobind rebind for OmniNode-ai/omninode_infra#920 modified the already-merged drift/dod_receipts/OMN-16027/dod-occ-evidence-admissibility-validator/command.yaml in place instead of adding a net-new correction, tripping the OCC Append-Only Gate on occ#6570. Restores the file to its exact merged (origin/dev) bytes and adds a net-new command.supersede.0001.yaml re-binding the evidence item to PR #920, same remedy shape as the OMN-15800/PR-858 precedent. Evidence-Ticket: OMN-16027
jonahgabriel
added a commit
that referenced
this pull request
Aug 17, 2026
…inode_infra#920 (#6570) * evidence(OMN-16027): author OCC companion for OmniNode-ai/omninode_infra#920 OCC companion by node_pr_lifecycle_fix_effect (OMN-13317 F1 / OMN-13990 / OMN-14285). Product PR head bb58c1ea34a3b4343575951801a276f549916b45. * evidence(OMN-16027): self-bind OCC#6570 + rebind contract_sha256 * fix(OMN-16027): restore append-only-violated receipt, add supersede record The occ-autobind rebind for OmniNode-ai/omninode_infra#920 modified the already-merged drift/dod_receipts/OMN-16027/dod-occ-evidence-admissibility-validator/command.yaml in place instead of adding a net-new correction, tripping the OCC Append-Only Gate on occ#6570. Restores the file to its exact merged (origin/dev) bytes and adds a net-new command.supersede.0001.yaml re-binding the evidence item to PR #920, same remedy shape as the OMN-15800/PR-858 precedent. Evidence-Ticket: OMN-16027 * fix(OMN-16027): yamlfmt-canonicalize command.supersede.0001.yaml Pre-commit Pre-commit hook flagged this net-new receipt as not yamlfmt-canonical (files were modified by this hook). Ran yamlfmt v0.21.0 with the repo's .yamlfmt config over the file; the only change is folded-scalar line-wrap position in the `reason` field. Verified the parsed YAML value is byte-identical before/after and the yamlfmt contamination gate (OMN-15479) passes on the result. --------- Co-authored-by: omnimarket-bot <bot@omninode.ai> Co-authored-by: jonahgabriel <jonah.gabriel@gmail.com> Co-authored-by: Jonah Gray <jonah@omninode.ai>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
dod-001,dod-session-id-bridge, anddod-occ-pr-912useddrift/dod_receipts/...which resolves against the calling repo workspace (omnibase_compat) in CI, not the OCC clone at/tmp/onex_change_control$CONTRACT_REPO_DIR/to match the pattern used by all other 9 DoD items in the same contractRoot Cause
The CI script (
run_contract_compliance_check.py) runssh -c <check_value>withcwd=workspace(the calling repo checkout).$CONTRACT_REPO_DIRis exported as/tmp/onex_change_control. Bare relative paths resolve into the calling repo, not OCC where the receipt files live.Test Plan
uv run validate-yaml contracts/OMN-10278.yaml— passespre-commit run --files contracts/OMN-10278.yaml— all hooks passOMN-10278
Evidence-Ticket: OMN-10278
Evidence-Source: OCC#918