Skip to content

Initialize the E2B state directory - #589

Merged
SaladDay merged 1 commit into
aos/cutoverfrom
aos/initialize-e2b-state-directory
Oct 8, 2026
Merged

SaladDay merged 1 commit into
aos/cutoverfrom
aos/initialize-e2b-state-directory

Conversation

@SaladDay

@SaladDay SaladDay commented Oct 8, 2026 •

Copy link
Copy Markdown
Collaborator

A fresh installation provides the private Provider state root, but E2B rejected setup because its own subdirectory did not exist. Create that single subdirectory in the existing E2B adapter constructor, then retain the existing validation of directory type and permissions. Existing state and receipts are never replaced or repaired; receipt-loss checks and Core’s one-shot allocation behavior are unchanged.

Exercise omitted-resource setup from a fresh state root and verify private creation, retained receipt bytes, unsafe-path rejection, and rejection of a missing installation root. Update configuration documentation and its Chinese translation, and remove the obsolete state-directory environment variable from the helper guide.

Validation: Go tests with race detection and go vet for E2B and execution; all 185 E2B Python tests; naming, docs and CI checks; all three website translation checks. E2B builds for Darwin and Windows, and execution builds for Darwin. The existing Windows execution build remains blocked by Linux syscall references in microsandbox/process.go.


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

@SaladDay
SaladDay merged commit f3c8dd6 into aos/cutover Oct 8, 2026
17 checks passed
@SaladDay
SaladDay deleted the aos/initialize-e2b-state-directory branch October 8, 2026 17:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant