deer-flow/backend/tests/test_scheduled_task_run_listing.py
Totoro 2dd2e5415c
feat(scheduled-tasks): finish the user-facing side of conversation schedules (RFC #6340, 1/2) (#6378)
* feat(scheduler): lifecycle rules, goal/limit parity and coded errors for scheduled tasks

- Migration 0031: nullable scheduled_tasks.unmet_streak_after_seq (internal
  streak boundary) and stop_condition (the user's stop rule, own column).
- Stop rule is normalized (stop_rule.py) and appended only at launch; the
  stored prompt never contains it. Wording adapts when scheduler.tool_enabled
  is off.
- Willem 1: page-created tasks get goal evaluation, <standing_notes>, the
  previous-run reference and own-schedule stop; request_stop and the
  scheduled capability no longer require an origin conversation.
- Repository: single reactivation choke point raising
  ScheduledTaskLimitsExhausted; streak boundary moves on goal/prompt/stop
  condition/note changes (not on resume); goal-check failures neither count
  nor reset the streak; pause of a finished task returns "finished"; trials
  on a paused task keep the host pause marker.
- New repository reads: automatic_runs_used_for, active_run_status_for,
  list_manageable_from_thread, thread_relation/thread_run on thread tasks,
  task_ids_for_thread, run_number, and run_number/total_tokens/summary on
  run history rows.
- REST: goal/max_runs/end_at/stop_condition on create and PATCH (null
  clears, naive end_at = task timezone), resume recomputes from now with an
  optional renewal body, once_time_passed, task_finished, limits_exhausted,
  scheduler_not_running on create, trigger returns outcome/existing/thread_id,
  task responses add automatic_runs_used and active_run_status.
- Coded errors {code, message, params} for routes, shared validation and the
  chat capability (scheduled_task_errors.py), pinned by
  contracts/scheduled_task_errors_contract.json; goal notes contract v2 with
  check_failure_codes, scheduled_origin_key and host_run_errors (host_notes.py).
- /api/features adds scheduled_tasks {available, running, tool_enabled,
  min_interval_seconds}; ScheduledTaskService.is_running.
- Docs: six README scheduler sections, API.md scheduled tasks section
  (breaking error shape), CONFIGURATION.md, AGENTS notes, CHANGELOGs.
- Tests: migration 0031, stop rule, error contract, run listing, lifecycle
  over HTTP, repository, service and capability cases; updated tests for the
  new error shape, finished-task pause and head revision.

* feat(scheduler): conversation update/resume, run-conversation authority and readable launches

- schedule_task: update and resume actions, stop_condition and clear_fields
  parameters, plain parameter types (value rules come back as coded results),
  rewritten docstrings for schedule_task and stop_scheduled_task.
- Capability: update/resume share the REST validation and error codes;
  interactive turns in a task's run conversation may manage that task;
  scheduled runs keep only own-stop; grants require a running scheduler.
- Results: compact JSON-safe task views with local times, display card/text,
  last run in list, timezone_source/browser_timezone, now_local; no ISO, user,
  lease or origin fields; stop_instructions removed.
- Timezone: explicit > browser (context.client_timezone, validated in
  start_run and never forwarded to the run config) > not needed for intervals
  and offset run_at > timezone_required.
- Trial gate accepts natural direct requests after acknowledgements and
  particles; trial results report thread_id and existing.
- Scheduled launches: stable message id scheduled-<task_run_id>, server-owned
  deerflow_scheduled_origin metadata with the user-language parts, run thread
  title for fresh-thread tasks.
- Worker records goal continuations in the verdict; lead prompt language rule
  covers stored task text and scheduled runs.
- Docs: six READMEs, CONFIGURATION, API, runtime/tools AGENTS, CHANGELOGs.

* feat(frontend): scheduled-task core types, formatting, errors and glossary

- throwGatewayApiError now throws GatewayApiError (status, code, params,
  rawMessage); message stays the string detail or detail.message
- scheduled-task types gain stop_condition, automatic_runs_used,
  active_run_status, origin/notes, run_number/total_tokens/summary, thread
  relation, trigger result, renewal and scheduled origin; isTaskBusy and
  hasActiveRun helpers
- api: fetchScheduledTask, resume with optional renewal body, typed trigger
  result and update payload with null clears
- hooks: polling at 3 s while a run is active (list, thread list, run
  history), useScheduledTask with live gating and final 404, useInView,
  localized error toasts; run history refreshes tasks when a run finishes
- new pure modules: errors.ts (contract code to localized copy), format.ts
  (relative task times, viewer time, display zone), status.ts, actions.ts,
  run-error.ts; describeTaskSchedule in cron.ts; goal-outcome adds unchecked
  goal checks, describeTaskOutcome and parseStopRunId
- features: scheduled_tasks block with defaults when missing
- buildRunContext sends client_timezone
- titleOfThread takes a localized untitled label; breadcrumb names scheduled
  tasks and agents; reference chips use the localized untitled label
- schedule input: shared browserTimeZone, labelled selects, aria-pressed
  type toggles, interval minimum from the hint template
- i18n: all PR1 scheduled-task keys in en-US and zh-CN, glossary fixes,
  recipe instructions moved into i18n
- e2e mocks follow the new task, trigger, resume, thread-task and features
  shapes; expectNoRawIdentifiers helpers for e2e and DOM tests
- tests for errors, format, cron, status, actions, goal outcome, run errors,
  hooks, run context, thread titles and features; scheduled e2e copy updated

* feat(frontend): list-first scheduled tasks page with outcomes and editable goals

- page.tsx is now a thin composition of components/workspace/scheduled-tasks:
  status tabs (All/Active/Paused/Finished) and search over the task list,
  ?task_id= deep link with router.replace on selection, ?thread_id= chip
  with Show all, empty state, scheduler-off notice and unavailable state
- task list rows show the schedule in words and one status line (next run,
  running now, paused by agent, auto-paused, finished by its cap)
- task detail: status badge, actions from availableActions with reasons,
  More actions menu (Duplicate, Copy task ID, Delete), outcome notice,
  Runs / Stops when / Each run's goal / Does / Notes from chat / History,
  origin chat link; success toasts for every action
- run rows: run number or Trial run, summary, goal and assumption badges,
  continuations, tokens, Open chat link; raw errors and the evaluator
  reason only behind Details
- create/edit/duplicate dialog with goal, stop condition, safety caps and
  advanced agent/context options; PATCH sends only changed fields, null
  clears a cap
- renew dialog raises or removes caps and resumes in one request; a
  limits_exhausted Resume opens it
- removed i18n keys the old page used; added feedback.resumedNoTime
- recorded en-3 and zh-1 page fixtures; scheduled e2e specs rewritten for
  the new page; DOM tests for the detail and the form dialog
- CHANGELOG entries and the frontend AGENTS.md scheduled-task note

* feat(frontend): live schedule card, run conversation provenance and header entry

- schedule_task results (create, update, pause, resume, trial, delete) become
  an assistant:scheduled-task message group rendered as a live card: schedule,
  next run, stop condition with the safety cap, goal, where results go, Run
  once now, Pause/Resume and Open task; the card polls the task only while it
  is on screen and shows deleted, scheduler-off and limits-exhausted states
- one card per task per assistant turn; the card group is not a turn boundary
  for usage, branching, editing, outline or skill attribution
- a human message with deerflow_scheduled_origin stays a human group with
  scheduledOrigin and renders as a "Scheduled run / Trial run" block with the
  task instructions, stop condition and notes collapsed; the launched text is
  never shown and the message is not editable
- readable step labels for schedule_task actions and stop_scheduled_task
- ThreadScheduledTasksButton replaces the header link: hidden without tasks,
  shows the count, links to the task (or the chat filter), and a run's chat
  links to its task
- recorded en-3 / zh-1 chat and run-thread fixtures; chat-card and run-thread
  e2e specs; unit and DOM tests for parsing, grouping, turn boundaries, card,
  run block, header button, step labels and reconnect hydration
- i18n: header.countLabelOne added, unused card.next removed; CHANGELOG and
  frontend AGENTS.md notes

* fix(scheduler): address verification findings

Move the scheduled-task lifecycle guidance from backend/AGENTS.md into the persistence guide and leave a one-line pointer, so the effective AGENTS.md chains for agents/middlewares, sandbox and subagents stay under the 98304-byte hard limit enforced by scripts/check_agent_guidance.py in lint-check.

* fix(scheduler): address review findings

* fix(scheduled-tasks): polish from live acceptance

- zh schedule wording: an interval of one unit reads 每分钟 / 每小时 / 每秒,
  and a saved interval of whole days reads 每天 / 每 2 天 (Every day / Every 2
  days) instead of 每 1 分钟 or 每 24 小时; several units keep the number
- zh spacing: 已于{time} 满足 and 在{time} 的运行中 now leave a space between
  the interpolated time and the Chinese after it; a copy test guards every
  scheduled-task zh string against a placeholder glued to Chinese
- run summary: when the first line of the final reply only leads in to a list
  (ends with ":" or ":"), the list items follow it as plain text (bullets,
  numbering, checkboxes, bold, code and links stripped), joined with ";" for
  CJK text and "; " otherwise, within the 160-character cap
- a schedule_task result (create, update, pause, resume, trial, delete) that
  arrives in a chat invalidates that chat's task list, the tasks list and the
  named task, so the header button and cards update without waiting for the
  idle poll; results already in the loaded history do not refetch
- e2e and unit fixtures are now the live acceptance recordings (DeepSeek
  Flash, demo data, fictional names): live-weekday.json (create, trial, edit,
  pause, resume in one zh chat) and live-minute.json (per-minute chat, run 1
  and run 2, paused by the agent), fetched with GET from the demo Gateway and
  trimmed; the hand-shaped en-3 / zh-1 fixtures are removed and the chat-card,
  run-thread and tasks-page specs run in both locales over the recorded data

* docs(changelog): reference #6378 for the scheduled-tasks entries

* docs(agents): shorten the scheduled-task pointer to stay under the guidance limit

* test(scheduled-tasks): pin the live takes to their recorded time zone

The live fixtures were recorded in Asia/Shanghai, and an interval task
reads in the viewer's zone, so the 16:48 assertions failed on UTC CI
runners. Pin the browser zone in the two live-take e2e specs and the
zh live-take unit test.

* fix(scheduled-tasks): keep untouched end times and drop a chat filter the new task is not in

- The edit, duplicate and renew dialogs keep a stored end time's instant
  while its field still shows it. A minute-precision wall value cannot
  keep seconds or name the later 01:30 of a DST fall-back, so a
  title-only edit moved the cap an hour earlier, and raising the run
  limit re-sent the end time without its seconds.
- Creating or duplicating a task from a chat's task view drops the chat
  filter when the new task does not belong to that chat, instead of
  showing "This task isn't one of this chat's tasks".

* fix(scheduled-tasks): tie pause notices to the pause they describe

- Paused by agent links and times only the run named in last_error. When
  that run is not loaded, the notice shows no link and the task's own time
  instead of an earlier run that also asked to stop.
- The outcome notice reads the latest history page whichever page is
  shown, so browsing older runs no longer swaps the auto-pause reason and
  "Open latest run" to an earlier miss. It shares that page's request.

* fix(scheduled-tasks): three lifecycle gaps found while re-checking review classes

- The edit form compares a cron in the form its schedule input emits, so an
  untouched "0 09 * * 0,6" is not re-sent as "0 9 * * 6,0" and a title-only
  edit no longer re-arms or refuses a finished task.
- Chat resume asks for a timezone, as update does, when a naive end_at would
  land in the UTC placeholder of a zone-free task.
- Re-arming a task clears a host pause marker, as resume does, so a later
  manual pause no longer reads as "Paused by agent".

* fix(scheduled-tasks): keep the notice's latest-runs query from refreshing older pages

useLatestScheduledTaskRuns kept React Query's default refetch on mount,
focus and reconnect, so going offline and back while an older history page
was shown fetched the latest page again. Refreshing stays with the history,
which refreshes the latest page only while it is shown.

* test(scheduled-tasks): let the viewer's time carry its own day label

Between 16:00 and 24:00 UTC, UTC and Asia/Shanghai are on different days,
so the run prompt shows "Tomorrow 01:00 · Today 09:00 your time" and the
fixed "01:00 · 09:00 your time" assertion failed depending on the hour.

---------

Co-authored-by: Totoro-qaq <279883115+Totoro-qaq@users.noreply.github.com>
Co-authored-by: Willem Jiang <willem.jiang@gmail.com>
2026-10-07 07:47:32 +08:00

136 lines
7.8 KiB
Python
Raw Permalink Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

"""Run history rows carry run numbers, token totals and the agent's summary."""
import pytest
import pytest_asyncio
from _scheduled_rows import create_task, durable_run, occurrence
from deerflow.config.database_config import DatabaseConfig
from deerflow.persistence.engine import close_engine, get_session_factory, init_engine_from_config
from deerflow.persistence.scheduled_task_runs import ScheduledTaskRunRepository
from deerflow.persistence.scheduled_tasks import ScheduledTaskRepository
@pytest_asyncio.fixture
async def repos(tmp_path):
await init_engine_from_config(DatabaseConfig(backend="sqlite", sqlite_dir=str(tmp_path)))
sf = get_session_factory()
try:
yield sf, ScheduledTaskRepository(sf), ScheduledTaskRunRepository(sf)
finally:
await close_engine()
@pytest.mark.asyncio
async def test_run_numbers_match_the_safety_cap_count_and_skip_unlaunched_rows(repos):
sf, tasks, runs = repos
await create_task(tasks, max_runs=10)
async with sf() as session:
session.add_all(
[
occurrence("first", seq=1, run_id="run-first"),
occurrence("trial", seq=2, trigger="manual", run_id="run-trial"),
occurrence("skipped", seq=3, status="skipped", accounted=False),
occurrence("second", seq=4, status="unmet", run_id="run-second"),
occurrence("cancelled", seq=5, status="interrupted", accounted=False, error="scheduled task was paused while queued"),
occurrence("third", seq=6, status="failed", run_id="run-third"),
occurrence("legacy", seq=None, accounted=None, run_id="run-legacy"),
]
)
await session.commit()
rows = {row["id"]: row for row in await runs.list_by_task("task-1", limit=50)}
assert {key: rows[key]["run_number"] for key in rows} == {"first": 1, "trial": None, "skipped": None, "second": 2, "cancelled": None, "third": 3, "legacy": None}
used = (await tasks.automatic_runs_used_for(["task-1"]))["task-1"]
assert max(row["run_number"] or 0 for row in rows.values()) == used == 3
assert await runs.run_number("third") == 3
assert await runs.run_number("trial") is None
assert await runs.run_number("skipped") is None
@pytest.mark.asyncio
async def test_a_launching_row_gets_the_number_it_will_have_once_accounted(repos):
sf, tasks, runs = repos
await create_task(tasks)
async with sf() as session:
session.add_all([occurrence("first", seq=1, run_id="run-first"), occurrence("trial", seq=2, trigger="manual", run_id="run-trial"), occurrence("now", seq=3, status="launching", accounted=False)])
await session.commit()
assert await runs.run_number("now") == 2
assert {row["id"]: row["run_number"] for row in await runs.list_by_task("task-1")}["now"] == 2
@pytest.mark.asyncio
async def test_rows_carry_token_totals_and_the_agents_reply_not_the_evaluator_reason(repos):
sf, tasks, runs = repos
await create_task(tasks, goal_objective="all items checked")
verdict = {"satisfied": False, "reason": "The evaluator wrote this in English.", "stand_down_reason": "blocked:goal_not_met_yet"}
async with sf() as session:
session.add_all(
[
occurrence("done", seq=1, run_id="run-done", thread_id="thread-done"),
occurrence("missed", seq=2, status="unmet", run_id="run-missed", thread_id="thread-missed", goal_verdict=verdict, error="blocked:goal_not_met_yet"),
occurrence("waiting", seq=3, status="queued", accounted=False),
durable_run("run-done", thread_id="thread-done", total_tokens=1234, last_ai_message="\n## 清单检查结果\n\n- 还有 2 项未勾选"),
durable_run("run-missed", thread_id="thread-missed", total_tokens=88, last_ai_message="**Two items** are still open: [owner list](https://example.test)."),
]
)
await session.commit()
rows = {row["id"]: row for row in await runs.list_by_task("task-1")}
assert (rows["done"]["total_tokens"], rows["done"]["summary"]) == (1234, "清单检查结果")
assert (rows["missed"]["total_tokens"], rows["missed"]["summary"]) == (88, "Two items are still open: owner list.")
assert rows["missed"]["goal_verdict"]["reason"] == "The evaluator wrote this in English."
assert (rows["waiting"]["total_tokens"], rows["waiting"]["summary"], rows["waiting"]["run_number"]) == (None, None, None)
assert "occurrence_seq" not in rows["done"] and "launch_accounted" not in rows["done"]
def test_summary_is_bounded():
from deerflow.persistence.scheduled_task_runs.sql import run_summary
summary = run_summary("x" * 400)
assert len(summary) == 160 and summary.endswith("…")
assert run_summary("---\n\n ") is None
assert run_summary(None) is None
# The final reply of run 1 of the live acceptance task (ux-audit/impl/live/S5-runs.json,
# task-run-f83bbe9076644db0b7cf4907e9911d08, thread c18ee7af-…), recorded on DeepSeek Flash.
# Demo data; the names are fictional.
LIVE_RUN_1_REPLY = (
"清单中还有 2 项未完成:\n\n"
"- **Publish the Docker image** — 负责人:Sam Okafor\n"
"- **Post the release notes** — 负责人:Nora Lind\n\n"
"其余 3 项(冻结发布分支、更新变更日志、运行完整测试套件)均已完成。由于仍有未勾选条目,停止条件未满足,本次不暂停计划。"
)
LIVE_RUN_2_REPLY = "已按停止规则暂停该定时任务:清单中所有条目均已完成,没有未勾选项,无需继续轮询。如需恢复,可在界面中重新启用该计划。"
def test_a_lead_in_line_carries_the_list_that_follows_it():
from deerflow.persistence.scheduled_task_runs.sql import run_summary
# Recorded live: the first line alone ("清单中还有 2 项未完成:") said nothing.
assert run_summary(LIVE_RUN_1_REPLY) == "清单中还有 2 项未完成:Publish the Docker image — 负责人:Sam Okafor;Post the release notes — 负责人:Nora Lind"
# A first line that is a full sentence (colon inside, not at the end) stays as it is.
assert run_summary(LIVE_RUN_2_REPLY) == LIVE_RUN_2_REPLY
def test_lead_in_list_variants():
from deerflow.persistence.scheduled_task_runs.sql import run_summary
# No list after the colon: the line is returned unchanged.
assert run_summary("Two items are still open:\n\nSee the checklist for details.") == "Two items are still open:"
assert run_summary("还有 2 项未完成:") == "还有 2 项未完成:"
# Numbered list, English: "; " between items, a space after the colon.
assert run_summary("Still open:\n1. Publish the image — Sam\n2) Post the notes — Nora\n\nNothing else changed.") == "Still open: Publish the image — Sam; Post the notes — Nora"
# Markdown bold, links, code and task checkboxes are stripped from the items; the list ends at the first prose line.
assert run_summary("**Open items:**\n\n- [ ] **Publish** the [image](https://example.test) — `Sam`\n* [x] Post the notes — Nora\nThat is all.\n- not part of it") == "Open items: Publish the image — Sam; Post the notes — Nora"
# The script of the summary text picks the separator, also with an ASCII colon,
# which keeps a space after it (a full-width ":" does not need one).
assert run_summary("未完成的条目:\n- 发布镜像\n- 发布说明") == "未完成的条目: 发布镜像;发布说明"
def test_a_long_lead_in_list_is_capped_with_an_ellipsis():
from deerflow.persistence.scheduled_task_runs.sql import run_summary
reply = "还有这些未完成:\n" + "\n".join(f"- 第 {n} 项任务,负责人是一位很忙的同事" for n in range(1, 20))
summary = run_summary(reply)
assert len(summary) == 160 and summary.endswith("…")
assert summary.startswith("还有这些未完成:第 1 项任务,负责人是一位很忙的同事;第 2 项任务")