Conversation
Fixes a known issue where `tokenCache.set` on an existing rate-limit token would implicitly reset its TTL, extending the penalty window. Setting `{ noUpdateTTL: true }` ensures proper expiration intervals. An additional test is included to enforce this.
Co-authored-by: APPLEPIE6969 <242827480+APPLEPIE6969@users.noreply.github.com>
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
1 participant
Modifies
lib/ratelimit.tsto include{ noUpdateTTL: true }when updating token hit counts, preventing the 60-second limit window from extending if requests continue. Tests were expanded to explicitly verify this behavior, resolving the known issue noted in memory.PR created automatically by Jules for task 9786147780763890053 started by @APPLEPIE6969