Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix : Groq TPM Limit Handling #602

Closed

Conversation

jiveshkalra
Copy link

Description

Fixes #601 ,

  • Feature : Added TPM(Token Per Minute) Limit handling to Groq , so if it hits the TPM , it doesnt stop ,instead it wait and retry in the given time

Explain what existing problem does the pull request solve?
Currently if Groq's TPM limit is reached then the agent just pops an error in the backend console and stops the task it was given and it has to start from start again, this is fixed in this PR, if the Groq TPM limit is reached , then devika will just wait for the time to pass and then try again in a few seconds.

Test plan (required)

image
image

Closing issues (optional)

Fixes #601

@jiveshkalra
Copy link
Author

jiveshkalra commented Jun 14, 2024

closes #601

@darrassi1
Copy link
Contributor

Unresolved attribute reference 'response' for class 'Exception'
use this
import requests

try:
....
except requests.exceptions.HTTPError as e:
if e.response.status_code == 429:

Fixed Unresolved attribute reference 'response' for class 'Exception'
@jiveshkalra jiveshkalra closed this by deleting the head repository Aug 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Issue : Groq API Rate Limit Error Handling
2 participants