Repository navigation
ci(hypatia): move the oracle pin to 51539ab, which has the PinSites fix - #21
Conversation
|
Caution Review failedThe pull request is closed. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. |
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
Dependency note. The red checks on this PR (DEED line 228, estate-rules root allowlist, openssf placeholders, Proven suite) are inherited from main: main d5e5111 fails the same four. They clear only when the other slices merge. This PR changes only the Hypatia pin (3 lines) and does not touch those files. Generated by Claude Code |
|
🟢 clean · commit Advisory: 11 row(s), worst 🔴 high (0 critical, 9 high in grid scope) — reported, never grading the change. Unique graded findings across gating and advisory rows: 19 (19 reporter observations; 19 without sufficient identity to corroborate). Row counts remain per reporter; unique totals do not change gating.
Hypatia scan: 4 finding(s)
panic-attack assail: 18 finding(s)
pons asinorum: 9 finding(s)
echidnabot: not_applicable — template default: enrol once the repository carries proofs and an ECHIDNA engine is configured
rhodibot (RSR compliance): 11 finding(s)
panicbot: not_applicable — panic-attack is already graded by the verdict grid's own panic-attack row, from static-analysis-gate.yml evidence; enrolling panicbot would report one scanner twice and give two rows that can disagree
sustainabot: not_applicable — reserved fleet slot; no adapter exists (gitbot-fleet bots/sustainabot/README.adoc)
glambot (presentation quality): 88 finding(s)
seambot: not_applicable — template default: enrol once a seam register exists at spec/seams/seam-register.json
finishingbot (release readiness): 177 finding(s)
cipherbot: not_applicable — template default: enrol once the repository implements cryptography
accessibilitybot: not_applicable — template default: enrol once the repository serves HTML
Scope: static findings reported by each row's tool at the named commit. The table grades only findings in files this change touches, so the colour answers "does this change introduce anything?", not "what does the whole repository still carry?". Standing findings are counted in each accordion and in report.json; the baseline filter remains the place where acknowledged debt is recorded. The lane state is the worst GATING row; advisory rows are listed and counted but never set it. Purple, red, yellow and blue grade the worst GRADED finding present; orange is evidence missing, malformed or a scanner that did not run; grey is an explicit scope exclusion with its reason. No row is a security certification. report.json, badge.json and the raw findings are in the verdict-grid artifact on the linked run. |
dogfood-gate.yml pinned Hypatia to be98f74, 112 commits before hypatia#1062 (37b8d01, the OTP segfault in the RSR oracle). The template moved to 51539ab in rsr-template-repo#369; this is the same three-line change (ref, comment, cache key). OTP 27.3.4.19 is already in the file. scripts/check-lock-sync.sh passes before and after (rc=0), so actions.lock needs no change: the ref is a checkout ref, not a uses: entry. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0136P7Zm6f3TYUpUuzGd5KAQ
d383564 to
3e1d88a
Compare
|



dogfood-gate.ymlpins Hypatia (the RSR oracle'srsr-score-selfjob) tobe98f74, which is 112 commits before hypatia#1062 (37b8d01, "Stop the OTP 28 segfault in scans and the RSR oracle (PinSites miscompile)"). With that pin the oracle exits 139. The template moved to51539abin rsr-template-repo#369;37b8d01is an ancestor of51539ab.This is the same three-line change as the template: the
ref, the comment, and the cache key. OTP 27.3.4.19 is already in the file, so it is unchanged.scripts/check-lock-sync.shpasses before and after (rc=0), soactions.lockneeds no regeneration: the ref is a checkout ref, not auses:entry.One concern, one signed commit (d383564). The push to this new branch name was a single push; its output has no "Bypassed" (the guard for the name lists
code_coverage, which is why I say so). No open bactrian PR (#11 #13 #14 #15 #16 #17 #19) touchesdogfood-gate.yml, so this does not duplicate any of them. Not yet seen: the CI result, in particular the RSR oracle step.https://claude.ai/code/session_0136P7Zm6f3TYUpUuzGd5KAQ
Generated by Claude Code