fix: apply configured leaky bucket throughput - #167
Merged
Merged
Conversation
knakul853
marked this pull request as ready for review
September 13, 2026 17:38
Ice3man543
approved these changes
Sep 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
max / durationinstead of one token per durationReproduction
NewLeakyBucket(ctx, 50, time.Second)previously exposed an underlying rate of 1 token/second; it now exposes 50 tokens/secondTakepreviously remained blocked after context cancellation; it now returnsTesting
go test -race -run "TestRateLimit/LeakyBucket" -count=1 -vgo test ./... -count=1Open in Codex: codex://threads/01a07d91-20ab-7a33-81ae-cfd2520595f4
Resume from CLI: codex resume 01a07d91-20ab-7a33-81ae-cfd2520595f4