feat: support automatic worker sizing - #235
Conversation
Co-Authored-By: OpenAI Codex <codex@openai.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3679b14a1f
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "Codex (@codex) review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "Codex (@codex) address that feedback".
Co-Authored-By: OpenAI Codex <codex@openai.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 635ed744b8
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "Codex (@codex) review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "Codex (@codex) address that feedback".
Co-Authored-By: OpenAI Codex <codex@openai.com>
What changed
num_workers="auto"for local and cloud launchesWhy
Users can size execution directly from pipeline sharding without manually counting shards. Fixed positive integer worker counts remain unchanged.
Validation
uv run pytest tests/launchers/test_cloud_launcher.py tests/launchers/test_local_launcher.py -k auto_workersuv run pytest tests/launchers/test_base_launcher.py tests/pipeline/test_planning.py tests/platform/test_cloud_client.pyuv run ruff check ...uv run ty check