Conversation
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 21 minutes and 3 seconds. ⌛ 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: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (14)
✨ 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 |
Safety layer for function I/O. 3 functions: - guardrails::check_input — PII, injection, length violations - guardrails::check_output — PII, leaked secrets, length violations - guardrails::classify — lightweight risk classification Default PII patterns: email, phone, SSN, credit card, IP address. Secret detection: Bearer tokens, OpenAI keys, GitHub PATs, AWS keys, private keys. All regex patterns pre-compiled at startup. Uses iii primitives: State (audit trail), Queue (async batch), HTTP triggers. 30 tests, 0 warnings.
7409e76 to
5ef8718
Compare
Summary
Functions
guardrails::check_inputguardrails::check_outputguardrails::classifyTest plan
cargo test— 30 tests passingcargo check— 0 warnings