+1 on this (Workflow log)

It seems like this particular issue was solved with the bot's update

Reopening this issue, still facing the issue on main

Sample workflow log

To note, this looks like a version conflict:

• this was merged after 0.16.1 release Use more specific action types for openhands-aci commands #5508
  • it does indeed introduce two new attributes, which don't exist in the 0.16.1 version of the event
• the workflow uses the 0.16.1 version

Ah gotcha, how about this workflow log? It's using main but faced the same error

It looks like this is not main, it's 0.16.1... 🤔

I mean line 139 there

Ah I see the confusion - the previous step in the workflow checks for the latest version

However for the step that installs the package, I forced it to install from main

When I use the released version 0.16.1, this issue doesn't occur (another workflow log
)

It seems like this is an issue only on main

EDIT: we can confirm this by running fix-me vs fix-me-experimental on an issue; I believe fix-me-experimental will fail

Hmm, how about the sandbox? This code above is running in the sandbox 🤔

I believe the resolver runs on eventstream instead of sandbox runtime; am I interpreting this correctly?

EDIT: yeah its running on a sandbox

The "eventstream runtime" is a docker sandbox, which communicates using an API sending/receiving events from the sandbox. It's not local, it's in docker.

EDIT: we can confirm this by running fix-me vs fix-me-experimental on an issue; I believe fix-me-experimental will fail

I ran fix-me-experimental here last night, it worked. The difference might be that your test repo is an external repo, while the successful workflow worked on this repo?

OpenHands started fixing the issue! You can monitor the progress here.

Possibly! Did a quick test, was able to reproduce the error again on this repo; there may be a PR that caused a regression in the last day or so

Oh, it failed with the same error. 🫣

Line 36: https://github.com/All-Hands-AI/OpenHands/actions/runs/12455745077/job/34768492590#step:10:37

I think the issue is due to the resolver using a specified runtime image, which skipped the runtime image build process:

One way to address might be to not specify this runtime image at all, similar to the dev workflow, which can add some build time overhead to the resolver, but can keep it up to date with all the changes in main. What do you guys think?

I'm running into the same issue running openhands locally using the development flow. My repo was synced to ee5f49a

+1

I'll revert to the last known stable commit as i'm just getting familiar with the project :)

I think the issue is due to the resolver using a specified runtime image, which skipped the runtime image build process:

OpenHands/openhands/resolver/resolve_issue.py

Lines 593 to 596 in 4a8bf3d

	if runtime_container_image is None:
	runtime_container_image = (
	f'ghcr.io/all-hands-ai/runtime:{openhands.__version__}-nikolaik'
	)

One way to address might be to not specify this runtime image at all, similar to the dev workflow, which can add some build time overhead to the resolver, but can keep it up to date with all the changes in main. What do you guys think?

Aha, that was the code. I agree! I think we should fix it as you suggest: let it build the runtime it needs.

Because we now use main in our fairly regularly used workflow, and also, importantly, other repos also build on top of our main workflow. Conflicts like this between the sandbox image and main can be pretty bad and they're almost blocking for external workflows.

Please note that this isn't always: this is for fix-me-experimental and equivalent macro (at openhands-agent-exp), which run on main. For the rest, the regular fix-me workflow (and equivalent macro), we can keep the released runtime, so there are no build times concerns there. Those run on the pypi version.

@glgh @gordicaleksa If you encounter this without running the resolver, can you please remove all openhands-related images from docker, and let it re-download?

@enyst Yeah, let me have a closer look and try a PR for that. This is a good opportunity for me to learn more about the resolver! 😅