Skip to content

Stop scaling after coordinator shutdown - #481

Closed
hermabr wants to merge 1 commit into
t3code/migrate-http-to-websocketsfrom
stop-scaling-after-coordinator-shutdown
Closed

Stop scaling after coordinator shutdown#481
hermabr wants to merge 1 commit into
t3code/migrate-http-to-websocketsfrom
stop-scaling-after-coordinator-shutdown

Conversation

@hermabr

@hermabr hermabr commented Aug 2, 2026

Copy link
Copy Markdown
Owner

Stacked on #470.

Summary

  • report zero satisfiable jobs after the execution coordinator is done
  • prevent a still-running pool scaler from starting workers during failure or interruption teardown
  • cover the behavior with ready work left in the coordinator

Tests

  • uv run pytest -n0 tests/test_worker_execution_coordinator.py::test_count_satisfiable_jobs_returns_zero_when_coordinator_is_done -q
  • uv run ruff check
  • uv run ty check

The full parallel suite reached 612 passed and 4 skipped, with two unrelated existing lock-contention tests failing their sub-second timeouts; both reproduced in isolation.

hermabr commented Aug 2, 2026

Copy link
Copy Markdown
Owner Author

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

This stack of pull requests is managed by Graphite. Learn more about stacking.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant