https://docs.all-hands.dev/ logo
Join Slack
Powered by
Looks like the LLM of the QA Agent ran out of cred...
# proj-agent
c
Looks like the LLM of the QA Agent ran out of credit:
Copy code
"filename": "agent_script.py", "lineno": 401, "message": "QA validation failed: Conversation run failed for id=59820508-6d75-4f3d-b9cb-77d226a2cf0b: litellm.BadRequestError: Litellm_proxyException - {\"error\":{\"message\":\"Budget has been exceeded! Team=ce3d0ff3-81b4-48a2-b300-1b5cbf450369 Current cost: 6000.583633640066, Max budget: 6000.0\",\"type\":\"budget_exceeded\",\"param\":null,\"code\":\"400\"}}"}
m
How can we bump the budget? Because all the examples in release are failing because of that. @millions-crayon-32880 @limited-student-10747
l
We’ll need to find the user associated with this in the llm proxy I guess
👍 1
m
hey, looking into this
🙏 1
Workflow failed here github.com/OpenHands/…/86338012671 Proxy used is llm-proxy.app.all-hands.dev see github.com/OpenHands/software-agent-sdk/blob/…/qa-changes-by-openhands.yml#… There is a user BYOR Key - user ce3d0ff3-81b4-48a2-b300-1b5cbf450369 with a single key that spent 7,428 but has no budget limit. Also does not match 6000 spent.
Digging a bit deeper
c
spent 7,428 but has no budget limit. Also does not match 6000 spent.
🫠
m
Thanks to looking into it. The release branch is ready. If we can run the test-examples than i think we can merge/release
m
@modern-fireman-99755 if it is urgent, I'll create a PR to use LLM_API_KEY_EVAL same as integration-runner as Engel suggested
l
No, we don’t need to do that
Let me take a look
So @millions-crayon-32880 and @modern-fireman-99755 if you look at the error message, you’ll see that it says that team “ce3d0ff3-81b4-48a2-b300-1b5cbf450369” is out of credits. So you go to the “teams” section of the litellm UI and copy-paste that into “search teams by name” and find the members. We can then see the user email associated with it (
<mailto:opendevin@all-hands.dev|opendevin@all-hands.dev>
) and bump the credits for that user using our standard method of bumping API credits.
I’ll do that now and see if it works.
Yep, looks like it’s fixed. I think we should be back in action.
gratitude thank you 2
ty 2
c
Thank you! Yes, examples are passing. On a side note, that’s a pretty cool email - I guess the key might be very old ❤️
l
Yep 🙂 It’s probably the github user account that is old, not sure about the key itself
m
thank you!
Oh, I see, I was looking at the key belonging to the team, which has no budget set, not the team itself
👍 1
6 Views
Open in Slack
PreviousNext
Powered by