feat: handle rate limits in batch evaluations #1207
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
geclos
force-pushed
the
feat/defend_against_provider_rate_limits
branch
2 times, most recently
from
ec4faa3 to
2868626
Compare
packages/core/src/lib/chainStreamManager/ChainStreamConsumer/consumeStream.ts
Outdated
Show resolved
Hide resolved
geclos
force-pushed
the
feat/defend_against_provider_rate_limits
branch
3 times, most recently
from
ffad6dc to
a3a9161
Compare
geclos
force-pushed
the
feat/defend_against_provider_rate_limits
branch
from
a3a9161 to
f17393f
Compare
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.
I will do evals v2 in another PR because they require a bigger refactor