Charles YaoandClaude Opus 4.8
ad06a30961
Final-review fix wave for the "reply in the user's input language" feature: - serde.py: context_from_dict omitted reply_language from the explicit field allowlist, so it round-tripped to "" on every read despite context_to_dict (asdict) serializing it -- the localization feature silently no-op'd after the first persisted write. Added it to the constructor call; TDD'd with a failing-then-passing round-trip test in test_serde.py. - localize.py: Localizer._cache was per-instance, but a fresh Localizer is built per advance-task invocation, so the static string catalog was re-translated every turn instead of once per language. Moved the cache to a module-level _TRANSLATION_CACHE dict (safe to share: keys are tenant/session-independent catalog-string+language pairs); added an autouse fixture in test_localize.py to clear it between tests for isolation. - localize.py: detect_language and _fill_cache called self._model_provider() outside their try/except, violating the Env callback contract that these must never raise. Moved both calls inside their try/except so a raising provider degrades to the existing safe fallback instead of propagating into advance/_commit. - strings.py: documented that Template.translate_fields is advisory only -- the Localizer re-inserts all captured groups verbatim and does not consult it. No behavior change. uv run --project api pytest tests/unit_tests/core/dify_builder tests/unit_tests/services/dify_builder -q -> 722 passed. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Dify Backend API
Setup and Run
Important
In the v1.3.0 release,
poetryhas been replaced withuvas the package manager for Dify API backend service.
uv and pnpm are required to run the setup and development commands below.
Using scripts (recommended)
The scripts resolve paths relative to their location, so you can run them from anywhere.
-
Run setup (copies env files and installs dependencies).
./dev/setup -
Review
api/.env,web/.env.local, anddocker/middleware.envvalues (see theSECRET_KEYnote below). -
Start middleware (PostgreSQL/Redis/Weaviate).
./dev/start-docker-compose -
Start backend (runs migrations first).
./dev/start-api -
Start Dify web service.
./dev/start-web./dev/setupand./dev/start-webinstall JavaScript dependencies through the repository root workspace, so you do not need a separatecd web && pnpm installstep. -
Set up your application by visiting
http://localhost:3000. -
Start the worker service (async and scheduler tasks, runs from
api)../dev/start-worker -
Optional: start Celery Beat (scheduled tasks).
./dev/start-beat
Environment notes
Important
When the frontend and backend run on different subdomains, set COOKIE_DOMAIN to the site’s top-level domain (e.g.,
example.com). The frontend and backend must be under the same top-level domain in order to share authentication cookies.
-
Generate a
SECRET_KEYin the.envfile.bash for Linux
sed -i "/^SECRET_KEY=/c\\SECRET_KEY=$(openssl rand -base64 42)" .envbash for Mac
secret_key=$(openssl rand -base64 42) sed -i '' "/^SECRET_KEY=/c\\ SECRET_KEY=${secret_key}" .env
Testing
-
Install dependencies for both the backend and the test environment
cd api uv sync --group dev -
Run the tests locally with mocked system environment variables in
tool.pytest_envsection inpyproject.toml, more can check Claude.mdContinue in the
apidirectory from the previous step.uv run pytest # Run all tests uv run pytest tests/unit_tests/ # Unit tests only uv run pytest tests/integration_tests/ # Integration tests # Code quality ../dev/reformat # Run all formatters and linters uv run ruff check --fix ./ # Fix linting issues uv run ruff format ./ # Format code uv run pyrefly check # Type checking
Generate TS stub
uv run dev/generate_swagger_specs.py --output-dir openapi
use https://jsontotable.org/openapi-to-typescript to convert to typescript