-
Notifications
You must be signed in to change notification settings - Fork 21
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
Connection refused: An issue that was on track to be resolved (looking at the logs) #306
Comments
Hey @ryx2 , sorry about this! My guess is that maybe the docker runtime ran out of resources while installing bun. |
I see this sometime when there's not enough resource (e.g., CPU, RAM) -- @ryx2 is the agent running something that consume a lot of resource? |
OpenHands started fixing the issue! You can monitor the progress here. |
An attempt was made to automatically fix this issue, but it was unsuccessful. A branch named 'openhands-fix-issue-306' has been created with the attempted changes. You can view the branch here. Manual intervention may be required. |
@xingyaoww it has this connection refused issue after it installs bun. I was only able to fix it by installing bun in the .yml in my fork |
OpenHands started fixing the issue! You can monitor the progress here. |
An attempt was made to automatically fix this issue, but it was unsuccessful. A branch named 'openhands-fix-issue-306-try2' has been created with the attempted changes. You can view the branch here. Manual intervention may be required. |
here's a bit more detail of how this error goes, I'll take a look as well
|
Did you simply add ?
|
I actually just made this work by adding the binary bun linux executable directly to my repo and instructing it in the .openhands_instructions to run with ./bun |
Might the runtime container have had an issue during the bun installation?
The text was updated successfully, but these errors were encountered: