You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
fix(minimald): let a task box with its own address and activate hooks run its task #3077
min task run cannot run the task of a box that has its own network address and activate hooks. BoxActor::ensure_host (crates/minimald/src/box_actor/host.rs) refuses with EntrypointBehindHookShell: the shell that ran the project's activate hooks holds the box's host-side row, that shell never ends (BOX-015), and replacing it would end the row. The refusal fails closed by design and arch accepted it on #2999. The old exec path ran such tasks, so this is a regression for that configuration.
The code comment on EntrypointBehindHookShell links #3042 as the tracking issue. #3042 covers only the [vars] ignore staging seam, so this issue tracks the hook-shell gap instead.
Scope:
Let a task box with its own network address and activate hooks start its entrypoint, for example by handing the host-side row from the hook shell to the entrypoint launch, or by running the hooks in a process that ends.
Add a test where such a box runs its task and returns the task's exit code.
Point the EntrypointBehindHookShell doc comment at this issue.
Activity