Repository navigation
Use protocol-correct Dask health checks in Compose - #938
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #938 +/- ##
=======================================
Coverage 74.34% 74.34%
=======================================
Files 183 183
Lines 36506 36506
Branches 2540 2540
=======================================
+ Hits 27140 27141 +1
+ Misses 8456 8455 -1
Partials 910 910 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
Review blocker: the three required running-topology tests are currently opt-in and no CI job enables them. This PR will remain Draft until a path-filtered Compose job exercises healthy startup, task submission, scheduler loss, unhealthy transition, and dependency gating on the final head. |
125dee4 to
61d9bfa
Compare
|
Resolved: a path-filtered Compose job now enables the live suite. The final head passed all 15 tests, including healthy startup and task submission for all three tracked topologies, scheduler-loss health transitions, and dependency restart gating. |
Closes #795.
Replaces the HTTP probe on Dask's scheduler protocol port with one bounded
distributed.Clientscheduler RPC. Worker and frontend services now wait for a healthy scheduler in all three Dask Compose topologies, while MongoDB dependency behavior remains unchanged.Validation:
docker compose config, Black,py_compile, andgit diff --check: passedIndependent agent review: PASS with no code changes.
The local Docker daemon was unavailable, so the opt-in full-container lifecycle tests were not claimed as executed; CI is expected to exercise container integration.