Conversation
|
Warning Rate limit exceeded
To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing. ⌛ 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 (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
Review rate limit: 0/5 reviews remaining, refill in 1 minute and 50 seconds. Comment |
f0ecfec to
397a12e
Compare
397a12e to
d10d313
Compare
|
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |



Summary (AI generated)
anonreads frompublic.audit_logs.Motivation (AI generated)
Unauthenticated PostgREST reads against
audit_logscould force expensive RLS planning/evaluation and degrade database availability. Blockinganonat the table grant layer makes the public anon-key path fail before the vulnerable RLS path.Business Impact (AI generated)
This reduces unauthenticated resource-exhaustion risk on the Supabase REST API while preserving authenticated audit-log reads and internal audit-log creation for CLI/API-key operations.
Test Plan (AI generated)
sqlfluff lint --dialect postgres supabase/migrations/20260502134045_fix_audit_logs_anon_dos.sql supabase/tests/40_test_audit_log_apikey.sqlbun run supabase:db:resetbun scripts/supabase-worktree.ts test db supabase/tests/40_test_audit_log_apikey.sql401 permission deniedfor anonaudit_logsread200Generated with AI