Repository navigation
Conversation
…210) The ray extra and the dev group pinned ray[default]==2.48.0. They now take ray[default]>=2.60.0,<3, and uv.lock holds ray 2.60.0 (with aiohttp 3.14.5 and yarl 1.25.1, which it requires). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
Warning Review limit reached
This review includes 4 billable files and costs up to $1.00.
Reviews can continue after your included limit without a manual trigger. An admin must approve usage-based billing. Or wait 22 minutes for your next included review. View limit details
|
There was a problem hiding this comment.
🟡 Changes recommended
The unconditional Ray 2.60.0 development dependency makes normal uv sync fail on Intel macOS because no compatible wheels or source distribution are available.
1 open issue
What changed in this PR
Updates Orcapod’s optional Ray execution dependency from an exact pin to a bounded version range, alongside the broader dependency refresh in #426.
Changes:
- Requires
ray[default]>=2.60.0,<3in the Ray extra and development group. - Locks Ray 2.60.0 and updates aiohttp and yarl.
- Documents local-cluster token authentication and its opt-out setting.
| File | Description |
|---|---|
uv.lock |
Updates Ray, aiohttp, yarl, and their locked artifacts. |
pyproject.toml |
Replaces both exact Ray pins with the new version range. |
changelog.d/ITL-1210.md |
Records the dependency change and local authentication behavior. |
Review effort: Balanced
| "pytest-xdist>=3.6", | ||
| "psycopg[binary]>=3.0", | ||
| "ray[default]==2.48.0", | ||
| "ray[default]>=2.60.0,<3", |
Codecov Report✅ All modified and coverable lines are covered by tests.
... and 2 files with indirect coverage changes 🚀 New features to boost your workflow:
|
…-1210) A driver started with uv run from a project whose version comes from version control hangs on its first RayExecutor call: Ray rebuilds the project on its workers without .git. The troubleshooting page, the RayExecutor docstring and the changelog fragment give the workaround, RAY_ENABLE_UV_RUN_RUNTIME_ENV=0 or starting the driver with python. ITL-1213 follows up on RayExecutor itself. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Note
Safe to merge after 0.4.0rc1, not for rc1. Merge #426 first, then this branch takes main back in and relocks.
With Ray 2.54 or later, a driver started with
uv runhangs on its firstRayExecutorcall when the project's version comes from version control. No task starts and no error is raised. Ray rebuilds the project on its workers from an upload of the working directory, and since 2.54 that upload leaves.gitout. Affected: a developer runningRayExecutorfrom an Orcapod source checkout withuv run, and, by the same mechanism, a user whose own project takes its version from VCS (hatch-vcs or setuptools-scm) and who starts the driver withuv run. Not affected: a driver started withpython, a project with a fixed version (Orcapod installed from PyPI), and a remote cluster with its own environment.Verified locally with one function pod on a local cluster. ray 2.48.0 with
uv run: works. ray 2.60.0 withuv run: hangs. ray 2.60.0 started with.venv/bin/python: works. ray 2.60.0 withuv runandRAY_ENABLE_UV_RUN_RUNTIME_ENV=0: works. This PR documents that workaround indocs/troubleshooting.md, theRayExecutordocstring and the changelog fragment (Known limitations). ITL-1213 follows up onRayExecutorraising instead of hanging.Raise the Ray requirement (ITL-1210). The
rayextra and the dev group pinnedray[default]==2.48.0, the version that happened to be installed when the pin was written. They now takeray[default]>=2.60.0,<3, anduv.lockholds ray 2.60.0, the latest release (wheels for CPython 3.11 to 3.13). The lower bound is the version tested here.Related: ITL-1210
Changes
pyproject.toml:ray[default]==2.48.0becomesray[default]>=2.60.0,<3in therayextra and in the dev group.uv.lock: ray 2.48.0 → 2.60.0, plus aiohttp 3.12.15 → 3.14.5 and yarl 1.20.1 → 1.25.1, which ray 2.60 requires.docs/troubleshooting.mdand theRayExecutordocstring: theuv runhang and its workaround.changelog.d/ITL-1210.md.What changes for a user
Ray 2.59 turned on token authentication by default for local clusters.
RayExecutorcallsray.init()with no address when it is given noray_address. That call now enables authentication and writes a token to~/.ray/auth_tokenif none exists. SetRAY_AUTH_MODE=disabledto opt out. Connecting to a remote or multi-node cluster (ray_address, includingray://) is unchanged.Release notes for Ray 2.49 to 2.60, checked against what Orcapod calls (
ray.init(address=, runtime_env=),ray.remote(...),ray.get,ObjectRef.future()including Ray Client,ray.nodes,ray.cluster_resources,ray.available_resources,ray.is_initialized,ray.shutdown): none of these is removed or changed. Besides the authentication default, the relevant changes are: Python 3.9 dropped (2.54); Pydantic v1 support removed (2.56; Orcapod requires Pydantic 2); cloudpickle 3.1.2 (2.55); hardenedruntime_envpackage extraction and pickle deserialization (2.56).Merge order
This PR touches
uv.lockandchangelog.d/ITL-1210.md, as #426 does. Merge #426 first. This branch then takes main back in, relocks and combines the two fragments.Checked locally (Python 3.12, ray 2.60.0)
tests/test_core/test_regression_fixes.py,tests/test_pipeline/test_logging_capture.py,tests/test_core/function_pod/test_function_pod_decorator.py): 80 passed, no warnings. These mock Ray or run the capture wrapper in-process: no test in the suite starts a Ray cluster.ruff check,ruff format --check, basedpyright (0 errors), and the changelog fragment check.🤖 Generated with Claude Code
Posted by a Claude Code agent on behalf of @eywalker.