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
Commit 2306df4
Browse filesBrowse the repository at this point in the historyBrowse files
fix(mothership): stop the workflow runs a stopped chat left running past a call
A synchronous workflows run the worker waits on in slices detaches after its
first --wait-timeout (#9464, mothership#872), and from then on no call's abort
signal reaches it. Stop delivery cancelled only browser workflow runs bound to
open calls, so a Stop mid-slice ended the chat while the draft run went on to
completion. Driven through the real controller and the Stop route (live case
in the next commit), the run was still running a minute after the Stop.
Stop delivery now also cancels the runs this chat run's calls started and left
running: a workflows run the CLI answered still running (exit 4 and its run
record), and a workflow tool answered still running. A run the chat only
waited on (workflows runs wait) is not one, since something else started it.
The cancel is the same in-process abort and durable cancel flag a browser run
gets; a detached run registers its in-process aborter.
Autopsy: the slice tests on both sides covered waits that settle, lapse or
lose an answer, and none stopped the chat mid-slice; the Stop tests seeded only
open browser-run calls. stop-delivery.test.ts and the live declared-stop case
now cover it.
0 commit comments