Repository navigation
fix(OMN-9058): align product receipt contract check - #1166
Merged
jonahgabriel merged 2 commits intoMay 19, 2026
Merged
Conversation
|
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 19, 2026 17:08
This was referenced Jun 11, 2026
jonahgabriel
added a commit
that referenced
this pull request
Sep 5, 2026
…ed the contract hash The dev merge appended the OMN-17809 entries from the #1165 companion, which moved sha256(contracts/OMN-17809.yaml) from de5f57ea to 33e19d6f. This receipt is the only changed one still binding by whole-file contract_sha256 (the other five carry a per-entry contract_entry_sha256 and were unaffected), so receipt hardening reported it as the single violation. Probe re-run, not re-stamped: $ gh pr view 1166 --repo OmniNode-ai/omninode_infra --json number,state,headRefName {"headRefName":"jonah/omn-17809-composition-probe-digest-crossfield","number":1166,"state":"OPEN"} contract_entry_sha256 is NOT minted here because contracts/OMN-17809.yaml carries no dod_evidence item with id dod-OmniNode-ai-omninode_infra-pr-1166 -- the companion emitter wrote the receipt without the matching contract entry. Recorded on OMN-16859.
jonahgabriel
added a commit
that referenced
this pull request
Sep 5, 2026
#8309) * evidence: OCC companion pass 1 for OmniNode-ai/omninode_infra#1166 * evidence: OCC companion self-bind for #8309 * evidence(OMN-17809): rebind the #1166 receipt after the dev merge moved the contract hash The dev merge appended the OMN-17809 entries from the #1165 companion, which moved sha256(contracts/OMN-17809.yaml) from de5f57ea to 33e19d6f. This receipt is the only changed one still binding by whole-file contract_sha256 (the other five carry a per-entry contract_entry_sha256 and were unaffected), so receipt hardening reported it as the single violation. Probe re-run, not re-stamped: $ gh pr view 1166 --repo OmniNode-ai/omninode_infra --json number,state,headRefName {"headRefName":"jonah/omn-17809-composition-probe-digest-crossfield","number":1166,"state":"OPEN"} contract_entry_sha256 is NOT minted here because contracts/OMN-17809.yaml carries no dod_evidence item with id dod-OmniNode-ai-omninode_infra-pr-1166 -- the companion emitter wrote the receipt without the matching contract entry. Recorded on OMN-16859. --------- Co-authored-by: node-occ-companion-effect <occ-companion-effect@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
Verification
Evidence-Ticket: OMN-9058