fix(test): correct dynamic config path in docker-compose

[abhishekj720]

Summary

The ubercadence/server image places dynamic config files under /etc/cadence/dynamicconfig/, but the docker-compose DYNAMIC_CONFIG_FILE_PATH was set to config/dynamicconfig/development.yaml. That path does not exist in the image so the config file was silently ignored meaning worker.enableScheduler: true never loaded and all schedule API calls timed out with DEADLINE_EXCEEDED.

Fix: set the path to dynamicconfig/development.yaml, which resolves correctly to /etc/cadence/dynamicconfig/development.yaml inside the container.

Also removes the now-redundant CADENCE_OVERRIDE_DYNAMIC_CONFIG=system.enableSchedules:true line, the bundled development.yaml already sets worker.enableScheduler: true.

How it was found

Running samples/schedule_sample.py demo against the Docker stack: create_schedule succeeded but describe_schedule always returned DEADLINE_EXCEEDED. Confirmed by running find inside the container the file was at dynamicconfig/development.yaml, not config/dynamicconfig/development.yaml. After the fix, the full demo ran end-to-end successfully.

Test plan

• docker compose up -d → uv run python samples/schedule_sample.py demo completes all steps without error

[gitar-bot]

Code Review ✅ Approved

Updates the docker-compose dynamic config path to align with the server image structure, resolving scheduler timeout issues. Redundant environment overrides were removed as the updated configuration file now correctly enables the scheduler.

Options

Auto-apply is off → Gitar will not commit updates to this branch.
Display: compact → Showing less information.

Comment with these commands to change:

Auto-apply	Compact
gitar auto-apply:on	gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.