mirror of
https://github.com/bytedance/deer-flow.git
synced 2026-08-01 19:06:01 +00:00
a328af2917
The outer ring: SQL repositories, the run launcher, the thread lookup, and the run-completion listener implementing the ports the domain declared, plus the HTTP router and the poller driving them. All of it is instantiated in one composition root, so no route or lifespan hook builds an adapter of its own. With the ports filled, the pre-hexagonal implementation is deleted rather than left alongside: `app/scheduler/service.py` and its router mixed policy, persistence, and HTTP into one class, which is why its rules were only reachable through a live database. Two bugs that shape hid are fixed here: a completion hook that replayed a stale snapshot and rolled the launch write back, and a corrupt stored row surfacing to the client as a 4xx. The concurrency invariants are pinned by contract suites that run each port against both the fake and real sqlite, plus dedicated dispatch-race tests. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
21 lines
896 B
Python
21 lines
896 B
Python
"""Adapters of the schedule context.
|
|
|
|
Mostly secondary (driven) adapters -- implementations of the output ports the
|
|
domain declares, which the service calls out to:
|
|
|
|
scheduled_task_repository.py owned persistence
|
|
scheduled_run_repository.py owned persistence
|
|
run_launcher.py anti-corruption layer over the run runtime
|
|
thread_lookup.py anti-corruption layer over the thread store
|
|
|
|
One exception, and the name says so:
|
|
|
|
run_completion.py PRIMARY (inbound) -- the run runtime calls it
|
|
|
|
It lives here so the context stays in one place rather than beside the other
|
|
two primary adapters, which sit next to whatever drives them (the router under
|
|
`gateway/routers/schedule/`, the poller under `scheduler/`). Direction is
|
|
stated by each module's own first line; a file added here without one is a
|
|
file whose direction nobody decided.
|
|
"""
|