mirror of
https://github.com/bytedance/deer-flow.git
synced 2026-09-14 16:08:41 +00:00
* refactor(gateway): issue request trace ids unconditionally The request trace id was gated behind logging.enhance.enabled at every entry point, so downstream code had to keep asking whether one existed: a header-provenance flag in its own ContextVar, a precedence resolver, and three-level carrier fallbacks at each consumer. Bind one unconditionally instead. TraceMiddleware covers Gateway HTTP; ensure_trace_context covers the entry points that never touch ASGI -- scheduled occurrences, MCP task notification runs, IM channel messages, and the embedded client -- each scoped to one unit of work so a long-lived worker task cannot leak one occurrence's id into the next. The ContextVar becomes the only source; the response header, runtime context, run metadata and log records are derived outputs. Consumers now use ensure_trace_id() or resolve_trace_id(*carriers) and drop their presence guards. Removed: resolve_deerflow_trace_id, the header-provenance flag and its three helpers, set/reset_current_trace_id, is_trace_correlation_enabled and its gateway alias. BREAKING CHANGE: every Gateway HTTP response now carries X-Trace-Id and it cannot be turned off; logging.enhance.enabled controls log output only. Installations on the default enabled: false will start seeing the header. No config keys were added or removed. * fix(gateway): stop persisting a caller-supplied trace id on the run record body.metadata forks two ways: through build_run_config into the live run config, which the run worker restamps, and through create_or_reject into the run record that the runs API echoes verbatim. Only the first was covered, so a client sending metadata.deerflow_trace_id made the most durable and most visible surface of a run disagree with the X-Trace-Id and the log lines the same request produced -- a correlation id that does not match the logs is worse than none. Stamp the server-issued id once at the trust boundary so both forks receive it, preserving the caller's own metadata keys. Close the same gap on config.context, which reaches the runtime context by a separate path: _build_runtime_context no longer merges server-owned keys from the caller, and _install_runtime_context assigns rather than setdefaults. A thread's metadata is no longer seeded with the run-scoped id of whichever run created it -- one thread spans many runs and as many trace ids. Found by driving a real run through the Gateway and reading the run back from the runs API; every unit test built its metadata by hand and so could not see it. * fix(gateway): expose X-Trace-Id to split-origin browser clients X-Trace-Id is not on the CORS safelist, so a browser client served from a separate origin could not read it -- and those are exactly the clients that cannot read the Gateway's logs either, leaving them with nothing to quote in a bug report. Same-origin nginx deployments were unaffected, which is why this stayed hidden. Add it to CORS_EXPOSED_HEADERS beside Content-Location, referencing TRACE_ID_HEADER rather than repeating the literal. * fix(gateway): keep X-Trace-Id on unhandled-exception 500s Starlette's ServerErrorMiddleware sits outside every user middleware and emits unhandled-exception 500s through the raw send, so those responses never pass TraceMiddleware's header-writing wrapper. The 500 for a server bug is exactly the response a user most needs to correlate with a log line, and it was the one response that shipped without the id. TraceMiddleware now tracks whether http.response.start has been sent. On an exception with no response started it emits its own plain 500 carrying the header, then re-raises: the outer ServerErrorMiddleware sees the response already started and only re-raises too, so the server's exception logging is untouched. An exception mid-stream keeps propagating unchanged — a second response start cannot be sent, and the already-written header stands. The trace id is printable ASCII by construction (normalize_trace_id / generate_trace_id), which is what makes the raw latin-1 header encoding safe. * fix(gateway): strip the forged trace id from the persisted request echo The run-record fix stopped a forged metadata.deerflow_trace_id on the authoritative metadata surface, but the raw request echo still carried one: create_or_reject persists body.config verbatim as runs.kwargs_json, which the runs API serves back. A client posting config.context.deerflow_trace_id therefore still got its forged value stored and echoed on one API surface while the header, logs, run metadata, and checkpoint all carried the real id — the id is ignored as input there, so echoing it back only manufactures disagreement. Two changes close it. redact_config_secrets — already the shared scrub for that echo, applied at admission and again at serve time, so historical records are covered too — now also drops deerflow_trace_id from config.metadata and config.context. And build_run_config now merges run metadata onto a copy of the caller's config["metadata"] instead of updating it in place: the nested values of the request config are reference copies, so the in-place merge was writing the server-stamped key through into body.config, contaminating the "what the client sent" record before it was persisted (and incidentally masking the forged-value echo on the metadata container). The regression test posts a forged id through body.metadata, config.metadata, and config.context at once and reads the kwargs echo back off the run record, failing if either leak returns. * docs(harness): record the trace-echo scrub, 500 fallback, and accepted retry divergence The trace section of the harness AGENTS.md now covers the two fixes that close the derived-output rule (the kwargs-echo scrub in redact_config_secrets plus build_run_config's copy merge, and TraceMiddleware's own 500 for unhandled exceptions), and CHANGELOG gains their Fixed entries. It also writes down the one accepted divergence: a crash-recovered scheduled launch reuses the durable run through its idempotency key, and start_run returns early on idempotency_reused without restamping — so the run record keeps the first attempt's deerflow_trace_id while the retry's own log lines carry the freshly minted id of its ensure_trace_context binding. The divergence is confined to the crash-recovery window and is accepted rather than fixed: restamping on reuse would rewrite a persisted record for a run that already exists, which is worse than two ids that each correlate their own attempt's logs. Written down so the next reader of the scheduler recovery path does not diagnose it as a bug. * docs(config): align the logging.enhance schema note with the unconditional trace id The config-module AGENTS.md still described logging.enhance as the gate for the Gateway X-Trace-Id header and Langfuse deerflow_trace_id. That model is gone: ids are issued unconditionally and this block decides log output only. Left as-is, the stale wording invites an agent to "restore" a header gate it believes was lost. Reworded to match the sibling AGENTS.md files and config.example.yaml, with a pointer to the Request Trace Context section that owns the full model. * docs(changelog): link the trace entries to #5119 The five new entries pointed at the ([#XXXX]) placeholder with no reference definition, rendering as literal text instead of a link — and RELEASING.md step 2 relies on those references when the section becomes release notes. All five now point at #5119, with the definition appended to the reference block. * refactor(harness): rename _stream_without_trace_context to _stream_turn The name asserted the opposite of what the method now does. It was accurate while logging.enhance.enabled could route stream() around the trace scope; with the gate gone it is the only stream implementation left, and it binds the id itself via ensure_trace_id(). Private, so the rename touches only the definition and the one stream() call site. * docs(harness): fit the trace-context guidance inside the AGENTS.md chain budget The expanded Request Trace Context section pushed the effective AGENTS.md chain for agents/middlewares to 99,815 bytes, past the 98,304 hard limit scripts/check_agent_guidance.py enforces in CI (AG002). Compressed the section from 7,359 to 4592 bytes with no facts removed: the entry-point table, the derived-output rule and its enforcement points, the accepted scheduled-retry divergence, the two resolution helpers, the stream() binding rationale, the log-output-only gate, the CORS listing, the 500 fallback, and the test map all remain. Sized against the merge, not just the branch: current main grew the same chain by ~724 bytes, so the check was verified on the merged tree as well (97,772 bytes; branch tree 97,048). * fix(gateway): declare content-length on the fallback 500 The pre-response 500 declared content-type but no content-length, leaving the framing to the ASGI server: chunked on HTTP/1.1, close-delimited on HTTP/1.0 — the one wire difference from the ServerErrorMiddleware response it replaces, which sends content-length: 21. The explicit header keeps the fallback byte-identical to what clients saw before. * docs(readme): drop the trace-correlation condition from the translations The zh/ja/fr/ru Langfuse sections still said metadata.deerflow_trace_id matches X-Trace-Id "when request trace correlation is enabled". The id now always matches and that condition no longer exists, so each bullet states the unconditional match and that logging.enhance.enabled only controls whether the id is printed into logs — the one piece of the feature a user can still configure. * test(gateway): pin TraceMiddleware wiring through create_app() Every X-Trace-Id test exercised a hand-built four-route app, so the real stack's add_middleware(TraceMiddleware) line was pinned by nothing: deleting it — or short-circuiting above it — passed CI while silently dropping both the response header and the ambient id the run-record stamp and enhanced log records derive from. One case now drives /health through create_app() and asserts the inbound id round-trips; mutation-checked by removing the wiring line, which fails exactly this test. * docs(gateway): note the fallback 500 is CORS-opaque The pre-response 500 is emitted outside CORSMiddleware — the exception has already unwound past it — so it carries no Access-Control-Allow-Origin and a split-origin browser client cannot read the id on this one response, unchanged from the ServerErrorMiddleware 500 it replaces. Documented on the class and in the CHANGELOG entry rather than fixed: replicating the origin allowlist outside CORSMiddleware would let the two policies drift. * fix(harness): keep abandoned-stream cleanup inside the trace binding stream() binds the turn's id around each next(inner) and resets it before yielding, but the finally's inner.close() ran after that binding was gone. Abandoning the stream therefore drove the inner LangGraph generator's GeneratorExit/finally path with no trace id — or an unrelated ambient one from whichever context ran the close — so cancellation and finalization logs and callbacks did not correlate with the turn they belong to. inner.close() is now wrapped in a local bind/reset of the same turn id. The token is set and reset in the same frame, never across a yield, so the per-step cross-context safety is preserved even when GC closes the generator from another Context — pinned by the existing copy_context close test, which now exercises this path. The regression test records the id from the inner generator's finally and fails without the binding. * test(harness): teach the worker-trace fake about RunManager.cleanup Upstream #5112 (bound gateway memory after terminal runs) added a run_manager.cleanup(run_id) call to run_agent's finalization, so the merge-commit CI run failed all five worker-trace-binding tests with AttributeError on this PR's _FakeRunManager. The fake gains the same no-op shape as its other methods. * docs(gateway): bring the gateway AGENTS.md back under its soft budget Upstream #5092 grew backend/app/gateway/AGENTS.md to 40,966 bytes, 6 over the 40,960 soft budget that test_agent_guidance_check.py::test_repository_guidance_stays_below_soft_budgets_and_avoids_doc_indexes enforces — its Unit Tests run on main was cancelled by push concurrency, so main is currently red on that test and every PR merge-run inherits the failure. Two whitespace/wording trims in the row #5092 touched (a doubled space, and "its configured `context_window`" → "its `context_window`") bring the file to 40,953 with no content change. --------- Co-authored-by: Willem Jiang <willem.jiang@gmail.com>
153 lines
7.0 KiB
Python
153 lines
7.0 KiB
Python
"""Regression tests for the config reload boundary registry.
|
|
|
|
Bytedance/deer-flow issue #3144: the hot-reload boundary is the contract
|
|
between gateway dependencies that resolve ``AppConfig`` every request and the
|
|
infrastructure that captures the snapshot once at startup. The registry in
|
|
``deerflow.config.reload_boundary`` is the machine-readable source of truth;
|
|
these tests pin the registry against the actual Pydantic schema so a future
|
|
field rename / addition / boundary change cannot silently drift.
|
|
"""
|
|
|
|
from __future__ import annotations
|
|
|
|
import pytest
|
|
|
|
from deerflow.config.app_config import AppConfig
|
|
from deerflow.config.reload_boundary import (
|
|
STARTUP_ONLY_FIELDS,
|
|
STARTUP_ONLY_PREFIX,
|
|
format_field_description,
|
|
is_startup_only_field,
|
|
iter_startup_only_field_paths,
|
|
)
|
|
from deerflow.config.skills_config import SkillsConfig
|
|
|
|
|
|
def test_registry_has_a_reason_for_every_field():
|
|
"""Every registry entry must explain *why* the field is restart-required.
|
|
|
|
The reason text is what surfaces in IDE hover and in the AppConfig schema
|
|
description, so an empty / placeholder value would defeat the purpose.
|
|
"""
|
|
for field_path, reason in STARTUP_ONLY_FIELDS.items():
|
|
assert reason.strip(), f"empty reason for {field_path}"
|
|
assert len(reason) > 20, f"reason for {field_path} too short to be useful: {reason!r}"
|
|
|
|
|
|
def test_iter_startup_only_field_paths_matches_registry():
|
|
"""Iterator stays in sync with the registry mapping."""
|
|
assert sorted(iter_startup_only_field_paths()) == sorted(STARTUP_ONLY_FIELDS)
|
|
|
|
|
|
def test_is_startup_only_field_recognises_registered_fields():
|
|
"""The membership helper accepts every registered field path."""
|
|
for field_path in STARTUP_ONLY_FIELDS:
|
|
assert is_startup_only_field(field_path)
|
|
assert not is_startup_only_field("memory") # hot-reloadable
|
|
assert not is_startup_only_field("models")
|
|
assert not is_startup_only_field("nonexistent_field")
|
|
|
|
|
|
def test_format_field_description_prefixes_with_marker():
|
|
"""The formatter produces a description that machine-readable tooling can
|
|
pivot on (drift tests, future "needs-restart" scanners)."""
|
|
for field_path in STARTUP_ONLY_FIELDS:
|
|
text = format_field_description(field_path)
|
|
assert text.startswith(STARTUP_ONLY_PREFIX), text
|
|
# The reason is appended after the prefix; the formatter must not
|
|
# silently drop it.
|
|
assert STARTUP_ONLY_FIELDS[field_path] in text
|
|
|
|
|
|
def test_format_field_description_rejects_unknown_field():
|
|
with pytest.raises(KeyError):
|
|
format_field_description("not_in_registry")
|
|
|
|
|
|
def test_format_field_description_appends_optional_field_doc():
|
|
"""The formatter composes the startup-only marker with the field's own
|
|
human-facing description when supplied.
|
|
|
|
The original ``Field(description=)`` used to document allowed values
|
|
(e.g. ``log_level`` listed ``debug/info/warning/error``); registry
|
|
adoption must not drop that. The composed output keeps the marker as
|
|
the leading token so machine-readable tooling still pivots on it,
|
|
then appends the prose after a blank line.
|
|
"""
|
|
text = format_field_description("log_level", field_doc="Logging level (debug/info/warning/error).")
|
|
assert text.startswith(STARTUP_ONLY_PREFIX)
|
|
assert STARTUP_ONLY_FIELDS["log_level"] in text
|
|
assert "debug/info/warning/error" in text
|
|
|
|
|
|
def test_appconfig_descriptions_retain_original_field_documentation():
|
|
"""``AppConfig.model_fields[name].description`` for restart-required
|
|
fields should still carry the original human-facing field doc so IDE
|
|
hover documents what the field is *and* why a restart is needed."""
|
|
descriptions = {
|
|
"log_level": "debug/info/warning/error",
|
|
"logging": "Structured logging settings: whether request trace ids appear in log records, and in which format.",
|
|
"database": "memory, sqlite, or postgres",
|
|
"sandbox": "Sandbox provider",
|
|
"run_events": "memory for dev",
|
|
"checkpointer": "state-persistence checkpointer",
|
|
"stream_bridge": "Stream bridge",
|
|
"channel_connections": "IM channel connection",
|
|
}
|
|
for field_name, expected_substring in descriptions.items():
|
|
description = AppConfig.model_fields[field_name].description or ""
|
|
assert description.startswith(STARTUP_ONLY_PREFIX), f"AppConfig.{field_name} missing startup-only marker"
|
|
assert expected_substring in description, f"AppConfig.{field_name} description lost original field doc; got {description!r}"
|
|
|
|
|
|
def test_appconfig_schema_marks_registered_fields_with_prefix():
|
|
"""Every registry entry that corresponds to a top-level AppConfig field
|
|
must carry the standardized ``startup-only:`` prefix in its Pydantic
|
|
``Field(description=...)``. This is the contract IDE hover relies on.
|
|
"""
|
|
schema_fields = AppConfig.model_fields
|
|
for field_path in STARTUP_ONLY_FIELDS:
|
|
if field_path not in schema_fields:
|
|
# Some entries (e.g. ``channels``) live outside the AppConfig
|
|
# schema. The registry still owns them, but the schema-prefix
|
|
# assertion does not apply.
|
|
continue
|
|
description = schema_fields[field_path].description or ""
|
|
assert description.startswith(STARTUP_ONLY_PREFIX), f"AppConfig.{field_path} should have Field(description=) starting with {STARTUP_ONLY_PREFIX!r}, got {description!r}"
|
|
|
|
|
|
def test_skills_container_path_is_registered_as_startup_only():
|
|
"""AIO and E2B snapshot the mount root when their provider starts."""
|
|
field_path = "skills.container_path"
|
|
assert field_path in STARTUP_ONLY_FIELDS
|
|
description = SkillsConfig.model_fields["container_path"].description or ""
|
|
assert description.startswith(STARTUP_ONLY_PREFIX)
|
|
assert STARTUP_ONLY_FIELDS[field_path] in description
|
|
|
|
|
|
def test_no_appconfig_field_uses_prefix_without_registration():
|
|
"""Reverse drift check: if a future schema edit adds the
|
|
``startup-only:`` prefix to a new field, the registry must list it.
|
|
|
|
This catches the silent-drift case where someone marks a field
|
|
restart-required in the schema but forgets to update the registry
|
|
that the operator-facing scanners and docs consume.
|
|
"""
|
|
for name, info in AppConfig.model_fields.items():
|
|
description = info.description or ""
|
|
if not description.startswith(STARTUP_ONLY_PREFIX):
|
|
continue
|
|
assert name in STARTUP_ONLY_FIELDS, f"AppConfig.{name} schema description starts with {STARTUP_ONLY_PREFIX!r} but the field is not listed in reload_boundary.STARTUP_ONLY_FIELDS — update the registry."
|
|
|
|
|
|
def test_pydantic_field_descriptions_are_introspectable_at_runtime():
|
|
"""``AppConfig.model_fields[name].description`` is the IDE-hover source.
|
|
|
|
If this read ever breaks (e.g. Pydantic deprecation, schema swap), the
|
|
IDE-hover guarantee #3144 promises silently regresses. Pin it.
|
|
"""
|
|
assert "database" in AppConfig.model_fields
|
|
description = AppConfig.model_fields["database"].description
|
|
assert description is not None
|
|
assert description.startswith(STARTUP_ONLY_PREFIX)
|