fix: rate-limit stale oracle alert to once per 5 minutes (N8)#106
fix: rate-limit stale oracle alert to once per 5 minutes (N8)#1060x-SquidSol wants to merge 1 commit intodcccrypto:mainfrom
Conversation
The stale oracle alert fired sendCriticalAlert every 60 seconds with no cooldown as long as any market had a stale oracle. A 30-minute stale oracle produced ~25 duplicate Discord alerts, causing alert fatigue. Add _lastOracleStaleAlertTime with a 5-minute cooldown, matching the pattern already used by the liquidation stale alert (_lastLiqStaleAlertTime at line 101). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
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 6 minutes and 43 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. ✨ 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 |
1 participant
Summary
sendCriticalAlertevery 60s with no cooldown_lastLiqStaleAlertTime) — this was simply omitted for the oracle alertFix
Add
_lastOracleStaleAlertTimewith identical 5-minute cooldown pattern. Alert fires at most once per 5 minutes while any oracle is stale.Test plan
🤖 Generated with Claude Code