mirror of
https://github.com/bytedance/deer-flow.git
synced 2026-06-13 10:55:59 +00:00
aa015462a7
* Add user-owned IM channel connections * Fix dev startup and channel connect popup * Use async channel connect flow * Harden dev service daemon startup * Support local IM channel connections * Align IM connections with local channels * Fix safe user id digest algorithm * Address Copilot IM channel feedback * Address IM channel review comments * Support all integrated IM channel connections * Format additional channel connection tests * Keep unavailable channel connect buttons clickable * Fix IM channel provider icons * Add runtime setup for enabled IM channels * Guard global shortcut key handling * Keep configured IM channels editable * Avoid password autofill for channel secrets * Make channel threads visible to connection owners * Persist IM runtime config locally * Allow disconnecting runtime IM channels * Route no-auth channel sessions to local user * Use default user for auth-disabled local mode * Show IM channel source on threads * Prefill IM channel runtime config * Reflect IM channel runtime health * Ignore Feishu message read events * Ignore Feishu non-content message events * Let setup wizard enable IM channels * Fix frontend formatting after merge * Stabilize backend tests without local config * Isolate channel runtime config tests * Address channel connection review comments * Use sha256 user buckets with legacy migration * Ensure runtime IM channels are ready after restart * Persist disconnected IM channel state * Address channel connection review comments * Address channel connection review findings Frontend connect flow: - Open the runtime-config dialog only when a provider still needs credentials; configured providers go straight to the connect flow, so the binding-code/deep-link path is reachable from the UI again. - After saving credentials, continue into the connect flow when a user binding is still required (multi-user mode) instead of stopping at a "Connected" toast. - Extract shared provider-state helpers to core/channels/provider-state and add unit + e2e coverage for the direct-connect and configure-then-connect paths. Provider status semantics: - Report connection_status from the user's newest connection row; with no binding it is not_connected, except in auth-disabled local mode where a configured running channel is effectively connected. Concurrency and event-loop correctness: - Offload ChannelRuntimeConfigStore construction and writes, channel service construction, and Slack connection replies to threads; add a tests/blocking_io/ anchor for the runtime-config handlers. - Consume binding codes with a conditional UPDATE so a code can only be used once under concurrent workers; retry upsert_connection as an update when a concurrent insert wins the unique constraint. - Serialize ensure_channel_ready per channel so concurrent provider polls cannot double-start a channel worker. Config and migration hardening: - Stop mutating the get_app_config()-cached Telegram provider config; the runtime store now owns the UI-entered bot username. - Register channel_connections in STARTUP_ONLY_FIELDS with the standardized startup-only Field description. - Match the legacy unsafe-id bucket by recomputing its exact SHA-1 name so another user's same-prefix bucket can never be migrated. - Remove the unused Telegram process_webhook_update path and document src/core/channels in the frontend docs. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * Address PR review comments on authz scoping and channel runtime Security (review feedback from ShenAC-SAC): - Scope internal-token callers to the connection owner carried in X-DeerFlow-Owner-User-Id instead of bypassing owner checks outright, in both require_permission(owner_check=True) and the stateless run endpoints. Internal callers keep access to their own and shared/legacy threads, and may claim a default-owned channel thread for its real owner, but a leaked internal token no longer grants cross-user thread access. - Require admin privileges for POST/DELETE /api/channels/{provider}/ runtime-config: runtime credentials and channel workers are instance-wide shared state (same model as the MCP config API). Read-only provider listing stays available to all users. Performance (review feedback from willem-bd): - Skip the redundant thread channel-metadata PATCH after the first successful backfill per thread. - Reuse the per-connection Slack WebClient until its token changes instead of constructing one per outbound message. - Reconcile channel readiness for all providers concurrently in GET /api/channels/providers. Also resolve the code-quality unused-import flag in the blocking-io anchor by pre-importing the channel service via importlib. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * Fix prettier formatting in provider-state test Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * Reconcile UI runtime channel config with config reload on restart Main now reloads a channel's config.yaml entry on restart_channel() (#3514, issue #3497). Adapt the user-owned connection flow to coexist: - configure_channel() restarts with reload_config=False — the caller just supplied the authoritative config (browser-entered credentials that are never written to config.yaml), so a file reload must not clobber it with the stale on-disk entry. - _load_channel_config() re-applies the UI runtime-store overlay used at startup, so an operator-triggered restart keeps browser-entered credentials for channels without a config.yaml entry and does not resurrect a channel disconnected from the UI. - Offload the reload's disk IO (config.yaml + runtime store) with asyncio.to_thread, matching the blocking-IO policy on this branch. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
142 lines
6.4 KiB
Python
142 lines
6.4 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,
|
|
)
|
|
|
|
|
|
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",
|
|
"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_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)
|