Repository navigation
fix(bot): Phase 2.5 bounded trackNowPlaying state - #675
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
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 59 minutes and 48 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 (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 |
|
Superseded by consolidated #676 (Phase 2 memory hygiene bundle). |
Pull request was closed
|



Summary
songInfoMessagesLRU cache: max 500 → 5000, TTL 4h → 30 minlastFmTrackStartTimeLRU cache: max 500 → 5000, TTL 4h → 30 minPattern (Option A: LRU+TTL)
Increases per-guild state limits to 5000 entries (from 500) with aggressive 30-minute expiration. Both caches store transient metadata:
songInfoMessages: now-playing message ID/channel (expires if guild leaves or message is deleted)lastFmTrackStartTime: scrobble timestamp (expires after track completes)30-minute TTL is conservative since typical tracks last 3-5 minutes.
Tests
✅ All 2660 tests passed
✅ Type checking: no errors
✅ Linting: no errors