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 11 minutes and 38 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: Repository YAML (base), Organization UI (inherited) Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
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 |
What
Toasts were vanishing instantly when the cursor hovered during the attention animation phase (the quality-gated bounce/pulse before the hold timer).
Root Cause
In
OnLeave, the fallbackOnToastFinished(self)fired wheneverresumed == false. During the attention phase,_isHoveredis set totrueon enter but nothing is actually paused - LibAnimate keeps running. On leave,ResumeFromHoverHoldreturnsfalse(the_hoverHoldCallbackis only set during the hold phase), soresumedstayedfalseand the toast was force-finished immediately.Fix
Added
and self._phase == nil and not self._isExitingto the fallback guard.OnToastFinishedis now only called fromOnLeaveas a last resort when the lifecycle has genuinely stalled (no active phase, not currently exiting). If_phaseis set, the LibAnimate queue is still running and will callOnToastFinishednaturally via its ownonFinishedcallback.Changes
DragonToast/Display/ToastFrame.lua: Two-predicate guard added toOnLeavefallbackType of change
Closes #171