Improve token shape unit coverage#786
Conversation
|
Warning You have reached your daily quota limit. Please wait up to 24 hours and I will start processing your requests again! |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ 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: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ 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 |
Motivation
expchanges for expired claims) so downstream parsers/validators see realistic, localized failures.Description
crates/uselesskey-token/src/srp/shape.rsthat assert expired OAuth negative tokens preserve header/signature context and only replace theexpclaim.BadIssuerandBadAudiencenegative variants preserve unrelated claims such assuband the remaining expected claims.NearMissApiKeythat verifies the near-miss prefix is used and the deterministic suffix matches the valid API-key suffix acrossApiKey,Bearer, andOAuthAccessTokenshapes.Testing
cargo test -p uselesskey-token srp::shape::testsand all tests passed (22 passed; 0 failed).22 passed; 0 failed).Codex Task