You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I'm trying to run the docker but it fails because i reched the OpenAI API limit for my plan.
openai.RateLimitError: Error code: 429 - {'error': {'message': 'You exceeded your current quota, please check your plan and billing details. For more information on this error, read the docs: https://platform.openai.com/docs/guides/error-codes/api-errors.', 'type': 'insufficient_quota', 'param': None, 'code': 'insufficient_quota'}}
ERROR: Application startup failed. Exiting.
To Reproduce
Steps to reproduce the behavior (as exampple`):
Reach the OpenAI limit for your plan
Use the docker compose down command
Use the docker compose up command
See error
Expected behavior
I expect to see a warning that says that i reached the limit but non an error in the startup of the docker.
The text was updated successfully, but these errors were encountered:
Sorry I closed because I did not understand the question
Sounds right to give a warning and not a crash
Well, I pay for OpenAI's APIs, but I've run out of available tokens. I set up the APIs within the graphical interface after starting Docker, but how can I change the APIs if Docker doesn't start? Isn't it possible that instead of crashing, Docker could notify me in the interface that I've run out of tokens? Or do I have to wait until tomorrow to start Docker?
Until we have a fix, I suggest you to delete the metadata.json so you can reset the llm and embedder settings and start again the container.
pieroit
changed the title
[BUG] Docker doesn't start when OpenAI API limit is reached
[BUG] Cat crashes when something goes wrong during bootstrap (LLM+embedder)
Oct 21, 2024
Describe the bug
I'm trying to run the docker but it fails because i reched the OpenAI API limit for my plan.
To Reproduce
Steps to reproduce the behavior (as exampple`):
docker compose down
commanddocker compose up
commandExpected behavior
I expect to see a warning that says that i reached the limit but non an error in the startup of the docker.
The text was updated successfully, but these errors were encountered: