Repository navigation
Initialize every hosted Environment - #873
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Every
openai_hostedEnvironment now starts initializationpending, so the Worker claims and completes it and journalsagent.session.environment.pendingandreadyonce, including when there are no files or setup.self_hostedkeeps its rule.An empty initialization sends no Runtime operation and uses no preparation cache. It adds the Harness availability check and two short transactions (claim and complete) per Session, and the first Turn waits for completion, up to one scan tick (250 ms) after the Runtime connects.
The ledger records that
connectedusually precedespendingandready; the Environment contract states when each event is emitted.Need help on this PR? Tag
@codesmith-botwith what you need.