Repository navigation
Allow model rate limits to select request classes - #91
Merged
Merged
Conversation
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
1 participant
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.
Rate limits on a model or alias can name the request classes they apply to (for example, throttle background cloud traffic without slowing foreground chat). This commit already runs on ennspark03 (deployed as 525bd1e on 8a9682d); this PR rebases it onto main so 03 stops running unmerged code.
Tests:
node --test test/rate-limit.test.mjs test/request-scheduler.test.mjs test/adaptive-priority.test.mjs test/federated-priority.test.mjs: 101 pass.🤖 Generated with Claude Code