Charles YaoandClaude Opus 5
6877532f8e
_repair_is_repeating could never fire in production. _note_repair_error counted repeats by exact string equality on diagnosis.root_cause, which is LLM prose regenerated on every diagnosis call. Observed live across four turns of one session: same failure, reworded every time, one turn switching to Chinese. Equality therefore never held, repair_attempts reset forever, and the guard was unreachable -- that session burned 9 failed verify runs and 8 repair approvals with the guard in place. The call site's own comment reads "ESQ1-285 burned nine approvals this way, ESQ1-290 six". The reproduction burned nine again. Key on the ENGINE's output instead: _failure_signature(run) returns the first failed node's id plus its error text (whitespace-collapsed), falling back to the launch error, and "" when the run identifies nothing -- so two unknown failures never compare equal. Why the existing tests passed while production was broken: every one of them fed _note_repair_error the SAME literal string twice, and StubAgent.diagnose always returns one fixed root_cause. They encoded the premise that is false in production. The new handler-level test drives three turns with an agent that rewords its root_cause each call while the engine fails identically, and fails against the old implementation with repair_attempts == 0. last_repair_error now holds that signature rather than prose. It was never displayed -- its only use was this comparison. Co-Authored-By: Claude Opus 5 (1M context) <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 AGENTS.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