Charles YaoandClaude Opus 5
a96ed2d387
Code review finding: build.initial_plan was left in _WAITING with zero _ACTIONS_FOR entries but a handler still gated on find_resources. Since a waiting state settles the runner's advance loop (is_waiting(next_state) -> settled), continue_adjusting from build.review landed a session there with no button the FE could render and no action the handler would accept -- the loop-back could never advance. Reclassify build.initial_plan as working (state.py _WORKING, not _WAITING): it is now a genuine pass-through step, matching build.test_and_repair / build.publish / build.governance_feedback. handle_initial_plan drops its find_resources gate and runs resource discovery unconditionally on entry; the runner drives it with the action already consumed and falls straight through to build.resource_recommendation within the same advance() call. Removed the now-stale BUILD_INITIAL_PLAN entry from service.py's _BACKEND_ACTIONS_FOR (no action to gate on any more) and the compensating exemption it required in test_every_backend_waiting_action_has_a_ui_path (the invariant now holds with no special case). Added a state-classification test (test_build_initial_plan_is_working_not_ waiting) and an end-to-end regression driving the Runner from build.review through continue_adjusting with no find_resources action ever sent (test_continue_adjusting_reaches_resources_without_find_resources_action), which is the scenario this fix exists to unwedge. Fixed the two existing idempotency flow tests that asserted the old (broken) two-step loop-back. 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