Skip to content

feat: add rankweave-hourly-review-repair.yml caller - #1289

Open
seonghobae wants to merge 1 commit into
mainfrom
ci/add-rankweave-hourly-review-repair
Open

feat: add rankweave-hourly-review-repair.yml caller#1289
seonghobae wants to merge 1 commit into
mainfrom
ci/add-rankweave-hourly-review-repair

Conversation

@seonghobae

@seonghobae seonghobae commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

Summary

  • RankWeave's own hourly-commercialization-loop.yml previously called pr-review-fix-scheduler.yml cross-repository at a pinned commit SHA (ContextualWisdomLab/.github/.github/workflows/pr-review-fix-scheduler.yml@21397126d708d2d536ccc1d68b0d333653ce9315).
  • pr-review-fix-scheduler.yml's current main hardens a same-repository trusted-source check (github.repository == ContextualWisdomLab/.github, see docs/doctoring comments already in the file). A cross-repository caller can never satisfy that check, so every RankWeave hourly run has failed with zero jobs scheduled ("workflow file issue") for as long as the hardening has been in place -- 19+ consecutive failures observed over 18+ hours in RankWeave's own Actions history.
  • Adds .github/workflows/rankweave-hourly-review-repair.yml, matching the pattern already proven for fast-mlsirm, DiskSage, and every other product repository: a same-repo uses: ./.github/workflows/pr-review-fix-scheduler.yml reference on a dedicated hourly cron (minute 33, unused by any existing caller), targeting ContextualWisdomLab/RankWeave, with a two-hour same-head retry floor matching the dominant convention across callers.
  • Registers the new caller/doctoring/test triple in hourly-nvidia-nim-review-repair.yml's exact-head focused quality gate (2/2/3 reference counts, matching every existing caller).
  • A companion RankWeave PR removes the now-dead repair-review-feedback job from RankWeave's own hourly loop.

Test plan

  • actionlint clean on both the new caller and the modified quality-gate workflow
  • New tests/test_rankweave_hourly_review_caller.py passes (4 tests)
  • python -m pytest -q on the full related test set (53 tests across caller/doctoring/runtime-budget/scheduler-contract files) passes
  • python -m compileall and git diff --check (the quality gate's own commands) pass clean

Generated with Claude Code

https://claude.ai/code/session_01K8VWdPkLwNYHGAKWowfueJ


Open in Devin Review

RankWeave's own hourly loop previously called pr-review-fix-scheduler.yml
cross-repository at a pinned commit SHA. That reusable workflow's
same-repository trusted-source hardening (github.repository ==
ContextualWisdomLab/.github) rejects any such caller, so RankWeave's
review-feedback repair job has failed with zero jobs scheduled
("workflow file issue") for as long as the hardening has been in place.

Add a central caller matching the pattern already proven for
fast-mlsirm, DiskSage, and every other product repository: a same-repo
`uses: ./.github/workflows/pr-review-fix-scheduler.yml` reference on a
dedicated hourly cron, targeting ContextualWisdomLab/RankWeave. A
companion RankWeave PR removes the now-dead local job.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01K8VWdPkLwNYHGAKWowfueJ
@coderabbitai

coderabbitai Bot commented Aug 24, 2026

Copy link
Copy Markdown

Warning

Review limit reached

Next included review available in 44 minutes.

View limit details

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: fa2f7849-748a-43e3-ab46-4d461ed7107d

📥 Commits

Reviewing files that changed from the base of the PR and between 0c6b9a6 and 7684f88.

📒 Files selected for processing (4)
  • .github/workflows/hourly-nvidia-nim-review-repair.yml
  • .github/workflows/rankweave-hourly-review-repair.yml
  • docs/doctoring/rankweave-hourly-review-caller.md
  • tests/test_rankweave_hourly_review_caller.py

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Open in Devin Review

@seonghobae
seonghobae enabled auto-merge (squash) August 24, 2026 05:27
@seonghobae

Copy link
Copy Markdown
Contributor Author

Exact-head formal review request for 7684f88. Please inspect the complete changed-file diff, with emphasis on hourly caller scope, credentials, schedule/concurrency, and exact-head repair boundary. Publish a substantive Reviews API verdict tied only to this exact SHA, including security/control-plane impact, test gaps, and residual uncertainty. Do not reuse predecessor-head evidence or failed provider checks as source findings. @opencode-agent

@seonghobae

Copy link
Copy Markdown
Contributor Author

Exact-head Strix RCA — 7684f88

The failed required Strix run was inspected from its job log. It did not report a source vulnerability: the run failed closed because the provider/runtime path was unavailable.

  • first attempt: Strix Caido bootstrap could not connect to 127.0.0.1:48080 after 10 attempts;
  • NVIDIA NIM attempts returned HTTP 429 Too Many Requests;
  • the configured openai-direct/gpt-5.6-luna fallback returned HTTP 404;
  • no structured vulnerability artifact was produced, so zero findings are not accepted as clean evidence.

This is provider/runner infrastructure evidence for the current head, not a source finding in the RankWeave caller. The PR remains WAIT_AND_REMEDIATE until the current Strix run and pending OpenCode review are terminal; no bypass or fake status is used.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant