feat(runtime): Add prototype Runloop runtime impl #4598
Conversation
| plugins, | ||
| env_vars, | ||
| status_message_callback, | ||
| attach_to_existing, |
There was a problem hiding this comment.
We'll need to make better use of this var--we use it pretty aggressively now. We create several Runtime objects within a session, and they all need to get access to the same runtime.
Can we track the runtime on runloop by sid, so that we can retrieve it if available?
There was a problem hiding this comment.
ah yes - so essentially, if attach_to_existing, we should look up by sid and first try to use the existing sandbox. is that the correct understanding? if so, I will get that in
There was a problem hiding this comment.
great - do you know if any tests cover this flow? i didn't see at first glance
There was a problem hiding this comment.
Hmm no I don't think we actually have integration tests here! We definitely should...
End-user friendly description of the problem this fixes or functionality that this introduces
Add Runloop runtime implementation on top of
EventStreamRuntimeGive a summary of what the PR does, explaining any non-trivial design decisions
This PR adds a Runloop runtime implementation, primarily utilizing
EventStreamRuntimeand its associated communication mechanismsThis runtime:
Devboxwill use a pre-built openhands sandbox image built againstdockerfile.j2run_action) toEventStreamRuntimeAlso included is a polling based
LogBufferLink of any specific issues this addresses