Use symmetric spawn-then-run() pattern in multi-task examples
Switch every example to ``await runner.spawn(task)`` followed by ``await runner.run()`` (no task argument), and ``await runner.cancel()`` on client-disconnected instead of ``await task.cancel()``. This makes the main pipeline task look the same as the worker / proxy tasks spawned alongside it, and lets ``runner.cancel()`` drive a uniform shutdown across every root task on the bus.
This commit is contained in:
@@ -104,8 +104,10 @@ async def websocket_endpoint(websocket: WebSocket):
|
||||
assistant = AcmeAssistant()
|
||||
|
||||
await runner.spawn(proxy)
|
||||
await runner.spawn(assistant)
|
||||
|
||||
logger.info("Assistant server ready, waiting for activation")
|
||||
await runner.run(assistant)
|
||||
await runner.run()
|
||||
logger.info("Assistant server session ended")
|
||||
|
||||
|
||||
|
||||
@@ -116,7 +116,6 @@ async def run_bot(transport: BaseTransport, runner_args: RunnerArguments):
|
||||
remote_task_name="assistant",
|
||||
forward_messages=(BusFrameMessage,),
|
||||
)
|
||||
await runner.spawn(proxy)
|
||||
|
||||
async def on_assistant_ready(_data: TaskReadyData) -> None:
|
||||
logger.info("Remote assistant ready, activating")
|
||||
@@ -145,9 +144,12 @@ async def run_bot(transport: BaseTransport, runner_args: RunnerArguments):
|
||||
@transport.event_handler("on_client_disconnected")
|
||||
async def on_client_disconnected(transport, client):
|
||||
logger.info("Client disconnected")
|
||||
await task.cancel()
|
||||
await runner.cancel()
|
||||
|
||||
await runner.run(task)
|
||||
await runner.spawn(proxy)
|
||||
await runner.spawn(task)
|
||||
|
||||
await runner.run()
|
||||
|
||||
|
||||
async def bot(runner_args: RunnerArguments):
|
||||
|
||||
Reference in New Issue
Block a user