mirror of
https://github.com/fabro-sh/fabro.git
synced 2026-09-19 00:03:30 +00:00
981253f990
RunSandbox grew its lifecycle methods one adopter at a time and ended up with several names for each step. Reconnecting from a run record had four entry points (reconnect, reconnect_for_run, reconnect_for_run_with_events, reconnect_driver_for_run) that all forwarded to the last one. Bringing a sandbox back had two (start and activate) over the same make_ready, and releasing it had two (delete and cleanup) over the same release. Two more methods had no callers at all: set_autostop_interval, which nothing set after the driver took over lifecycle timers, and resume_setup_commands, which resume stopped using when checkout moved to the git facet. There is now one of each. reconnect_for_run takes the record, the provider access, an optional run id, and an optional event context; callers that need none pass None. activate is the single "make usable" step: a running sandbox only learns its platform when it has not yet, a stopped or paused one is started and its Bash verified, and resume calls it like every access-time caller. delete is the single release; for a designated host directory it frees the handle and leaves the directory in place, as cleanup did. The tests and server call sites follow the renames; behavior is unchanged except that resuming an already running sandbox no longer re-runs the Bash probe. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| fabro-acp | ||
| fabro-agent | ||
| fabro-automation | ||
| fabro-checkpoint | ||
| fabro-dump | ||
| fabro-environment | ||
| fabro-github | ||
| fabro-graphviz | ||
| fabro-hooks | ||
| fabro-install | ||
| fabro-interview | ||
| fabro-llm | ||
| fabro-manifest | ||
| fabro-mcp | ||
| fabro-mcp-store | ||
| fabro-sandbox | ||
| fabro-slack | ||
| fabro-store | ||
| fabro-tool | ||
| fabro-tracker | ||
| fabro-validate | ||
| fabro-variable | ||
| fabro-workflow | ||
| fabro-workflow-version | ||