Confirm rate limit comment matches burst value (60)#38
Closed
Copilot wants to merge 1 commit into
Closed
Conversation
Copilot
AI
force-pushed
the
copilot/adjust-limit-comment-in-rate-limit
branch
from
June 1, 2026 23:58
2572df4 to
6637840
Compare
Copilot
AI
changed the title
[WIP] Fix comment mismatch in rate limit burst value
Confirm rate limit comment matches burst value (60)
Jun 1, 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
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.
The comment added in PR #20 read
// 60 requests/minute per key with a burst of 30while the actual burst argument passed toratelimit.Newwas60— a clear mismatch.The comment has since been corrected on
mainto accurately reflect the configured values:All other references (
README.md,internal/docs/openapi.yaml) already consistently state burst of 60.