fix: address auth map growth, quota rollback, body close, and CSI shutdown#380
fix: address auth map growth, quota rollback, body close, and CSI shutdown#380
Conversation
…ceful shutdown - auth.go (#280): add hard size limits (maxFailedAttemptsMap=1000, maxLockoutsMap=10000) for deterministic eviction when maps grow beyond threshold, supplementing the existing probabilistic purge - instance.go (#297): rollback vCPU and memory quota when enqueue fails after IncrementUsage (previously leaked quota on enqueue error) - gateway_e2e_test.go (#307): use defer to close response body for all code paths, not just on HTTP 200 - csi-driver/main.go (#283): wait for d.Stop() completion with 5s timeout before exiting main, preventing signal handler goroutine leak
|
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 (4)
✨ 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. Review rate limit: 0/1 reviews remaining, refill in 56 minutes and 12 seconds.Comment |
Summary
Test plan
Fixes #280, #297, #307, #283