-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
500s from the API #201
Comments
i have noticed the same error from yesterday. i thought it was me, Was really enjoying the agent type system. been a long time since i have been impressed. Well done team |
Hey, I am facing same issue and i solved it temporarily by removing the ephemeral cache. In your loop.py, you can make |
Same issue here |
Same |
1 similar comment
Same |
|
Same issue for me I have a DEMO this evening so hopefully this gets resolved ASAP : ) Maybe I'll try Bedrock or VertexAI |
I’m still encountering the issue in both my modified project and this original demo. Setting |
Hello! Like @thaddavis, I am also doing a demo in 1 hour and it is not good when you start getting random 500 errors. I changed my This was because, stupidly, I was following the Anthropic API Quickstart instructions at the top which use a pre-baked Docker container. Once I realized this, I booted it up instead using the Development instructions at the bottom, then it started working again. |
Ah great @pcraig3 let me try that now |
Appreciate it @pcraig3. Building the project locally worked. |
Hey all,
I've been playing with computer use demo and it's been working great for the past couple of days, really awesome product and a demo.
However, it has been failing with 500s all day today since about 2 PM PST.
It always fails after the client attempts to send an image. I think this is similar to the incident listed on
status.anthropic.com:
However, the status page says that it's resolved, where in practice I'm still seeing 500s.
Again, awesome product, I hope you guys fix it soon. Let me know if you need more info from my side.
The text was updated successfully, but these errors were encountered: