lisry-1 46ccfab71a

Track DingTalk stream message tasks to avoid dangling tasks (#7429) ...

* Track DingTalk stream message tasks to avoid dangling tasks

The stream loop handed each frame to client.background_task() via a
bare asyncio.create_task(...) whose result was dropped. asyncio only
keeps a weak reference to a task once it awaits, so the task could be
garbage-collected mid-execution (silently dropping a message) and any
exception it raised was never observed.

Keep a strong reference to each handler task and discard it via a done
callback, matching the background-task tracking used elsewhere (e.g.
the subagent executor and the MCP session pool).

* fix(channels): observe DingTalk stream task failures

---------

Co-authored-by: lisry-1 <lisry-1@users.noreply.github.com>
Co-authored-by: Willem Jiang <willem.jiang@gmail.com>

2026-10-25 16:15:15 +08:00

..

channels

Track DingTalk stream message tasks to avoid dangling tasks (#7429)

2026-10-25 16:15:15 +08:00

gateway

fix(threads): reject an assistant_id that names no agent at thread creation (#7445)

2026-10-25 13:21:47 +08:00

mcp_tasks

fix(mcp): retain durable control claims through slow calls and cancellation (#6780)

2026-10-21 22:03:21 +08:00

scheduler

fix(scheduler): reconcile running occurrences from terminal durable runs (#7269)

2026-10-24 20:56:35 +08:00

subagent_batches

feat(subagents): add unified capacity and durable batch execution (#4998)

2026-08-25 07:49:38 +08:00

__init__.py

refactor: split backend into harness (deerflow.*) and app (app.*) (#1131)

2026-03-14 22:55:52 +08:00