github/deer-flow
1
0
Fork 0
mirror of https://github.com/bytedance/deer-flow.git synced 2026-11-15 15:50:35 +00:00
Code Issues Packages Projects Releases Wiki Activity
deer-flow/backend/AGENTS.md
ChengLong GU c263b887b5
fix(scheduler):修复单个定时任务派发异常中断整批执行 (#8047) 
* fix(scheduler): isolate queued run drain failures

* fix(scheduler): isolate queue timeout rows

* fix(scheduler): enforce queue timeout at launch claim

Keep expired queued occurrences ineligible to start when the timeout sweep fails. Cover per-row and whole-scan cleanup failures with SQLite service tests that also verify healthy queued and due work still launches.

* fix(scheduler): exclude expired rows from queue selection

Filter rows past the queue deadline before owner ranking and the fair batch limit so failed timeout cleanup cannot starve healthy waiting work. Keep the atomic claim cutoff as the final launch guard.

---------

Co-authored-by: AochenShen99 <sac1063467113@hotmail.com>
Co-authored-by: Nan Gao <thunderggnn@gmail.com>
2026-11-13 18:46:11 +08:00

3.8 KiB
Raw Blame History

Backend (backend/)

The Python backend: the publishable harness in packages/harness/deerflow/, the public extension contract in packages/extension-api/, and the unpublished Gateway and IM channels in app/. In every deployment the agent runtime runs inside the Gateway. Design docs are in docs/; start with ARCHITECTURE.md and API.md.

Guides by area

Read the guide for an area before you change it.

Area Guide
Run streaming, checkpoints, run ownership runtime
Repositories, leases, scheduled tasks, schema changes persistence, migrations
Scheduler failure isolation design conventions
config.yaml, extensions_config.json config
Lead agent, prompt, thread state, middleware chain agents, middlewares
Memory, subagents, skills, tools memory, subagents, skills, tools
Sandbox, uploads, MCP, models, extensions sandbox, uploads, mcp, models, extensions
Trace ID, embedded client, other root modules harness package
Search, fetch and sandbox providers community, then the provider's own guide
Gateway, routers, IM channels gateway, routers, channels
Tests, benchmarks tests, benchmarks

Verify

make test               # offline suite in parallel shards
make test-blocking-io   # strict blocking-I/O suite
make lint
make format
make test-live          # calls real APIs; needs DEER_FLOW_RUN_LIVE_TESTS=1

Run make test and make test-blocking-io before and after a change. Every feature and bug fix ships with a test in tests/. Live tests stay opt-in, so the default suite needs no network and no API key.

Rules

  • The harness never imports app. app.* imports deerflow.*, and not the reverse, because the harness is published on its own. tests/test_harness_boundary.py enforces this in CI.
  • Start the Gateway with make dev or make gateway. make dev excludes DEER_FLOW_HOME and backend/sandbox from the reload watcher. A bare uvicorn --reload restarts the Gateway during a run, because agent tasks write Python files below DEER_FLOW_HOME.
  • From the repository root, run backend tools with uv run --no-sync --project backend. --project keeps the caller's working directory, so relative config paths still resolve. --no-sync keeps installed extras such as the PostgreSQL drivers.
  • Run Python through uv run inside backend/, without --no-sync, so the environment matches the lock.
  • Guard POSIX-only test markers with os.name. Windows collects the same files.
  • Tool approvals need addressable calls. Strip missing, empty and duplicate tool-call IDs before creating a pause or a tool result. See the run interaction policy.
  • Add a schema change with make migrate-rev MSG="..." and follow the migrations guide.