Uh oh!
There was an error while loading. Please reload this page.
chore(lint): fix ruff violations in RAG scripts unblocking main CI - #324
Conversation
main's CI (Backend job) has been red since the RAG pipeline scripts landed (~Jul 3): 8 un-baselined ruff errors caused ruff check . to exit 1, skipping pytest. Because main isn't a protected branch, merges proceeded through the red and it went unnoticed — and every open PR's Backend job inherited the failure via the pull_request merge check. Fixes (behavior-preserving): - benchmark_rag.py: drop unused import os; noqa: E402 on the two intentional post-sys.path imports; drop unused chunk_results binding (keeps the side-effecting run_chunk_tests call). - ingest_catalog.py: noqa: E402 on the post-sys.path import; drop stray f-prefix on a placeholder-less string. - scrape_bu_catalog.py: drop unused import sys; drop unused school_courses binding (keeps the side-effecting scrape_school call). Verified locally: ruff 0.15.20 check . -> All checks passed. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Warning Review limit reached
Next review available in:24 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?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 reviews. How do review 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 refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Deploying with |
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs | frontend-staging | 9fcfb9e | Commit Preview URL Branch Preview URL | Jul 08 2026, 06:28 AM |
Uh oh!
There was an error while loading. Please reload this page.
main’s CI Backend (pytest) job has been red since the RAG pipeline scripts landed (~Jul 3): 8 un-baselined ruff errors made
ruff check .exit 1, which skips pytest entirely. Becausemainisn’t a protected branch, merges kept going through the red and it went unnoticed — and every open PR inherits the failure via thepull_requestmerge check.Violations fixed (all pre-existing on
main, behavior-preserving)scripts/benchmark_rag.pyimport os# noqa: E402on the two intentional post-sys.pathimportschunk_resultsbinding (keeps the side-effectingrun_chunk_tests(cases)call)scripts/ingest_catalog.py# noqa: E402on the post-sys.pathimportfprefix on a placeholder-less stringscripts/scrape_bu_catalog.pyimport sysschool_coursesbinding (keeps the side-effectingscrape_school(...)call)No behavior change — only unused bindings/imports removed and intentional bootstrap imports annotated.
Verification
ruff 0.15.20 check .(same version +ruff.tomlas CI) → All checks passed. This PR’s own CI should now run pytest (previously skipped) and go green, un-reding the whole PR backlog’s Backend job.@Darkest-Teddy heads-up — these are your RAG scripts; open PRs (#318/#323) may need a trivial rebase after this lands.
🤖 Generated with Claude Code