Rollout-host-only: 3.10 toolchain, ROLLOUT_INSTALL, rollout-requirements#402
Draft
rl2aloha wants to merge 2 commits into
Draft
Rollout-host-only: 3.10 toolchain, ROLLOUT_INSTALL, rollout-requirements#402rl2aloha wants to merge 2 commits into
rl2aloha wants to merge 2 commits into
Conversation
Local-only branch that should NOT be merged. Carries the patches the rollout host needs to bring up the policy: - pyproject.toml: relax `requires-python` to `>=3.10` (ARX `arx5_interface` ships as a cpython-310 .so, so the rollout host can't be 3.11) and drop `zarr==3.1.5` from the runtime deps (training-only). - pull_models.sh: REMOTE_PATH bumped to the EgoVerse4 logs dir. - rollout-requirements.txt: trimmed sibling of requirements.txt with zarr removed and 3.10-friendly pins. - uv.lock: 3.10-resolved lockfile (used to seed openpi's pip install via `uv export -c`). - ROLLOUT_INSTALL.md: end-to-end setup guide for the rollout host (Python 3.10, openpi fork, ARX bindings, HF auth, checkpoint conversion). External submodule pointer for `external/openpi` is intentionally left uncommitted here; commit inside the submodule first if you want to freeze the openpi rollout-fork rev. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
The "Branches" section claimed external/openpi is on a fork branch with the rollout patches "already committed" — it isn't. The submodule is detached at upstream 981483d with the patches as uncommitted working-tree edits, plus an untracked scripts/patch_transformers.py. The fork has a pi-rollout-changes branch with overlapping patches, but it diverges from this host's working tree (adds chex, loosens numpy / opencv-python, patches pi0_pytorch.py; missing .python-version, packages/openpi-client/pyproject.toml, uv.lock, patch_transformers.py). Calling out the divergence so future-us doesn't merge them blindly. Replaces the prior "checked out on a rollout branch" wording with an explicit "openpi patches to apply on top of 981483d" checklist — file-by-file, what to change and why — so the setup is reproducible even without a clean fork branch. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
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.
This stack of pull requests is managed by Graphite. Learn more about stacking. |
This was referenced May 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rollout-host-only: 3.10 toolchain, ROLLOUT_INSTALL, rollout-requirements
Local-only branch that should NOT be merged. Carries the patches the
rollout host needs to bring up the policy:
requires-pythonto>=3.10(ARXarx5_interfaceships as a cpython-310 .so, so the rollout host can't be 3.11) and drop
zarr==3.1.5from the runtime deps (training-only).zarr removed and 3.10-friendly pins.
via
uv export -c).(Python 3.10, openpi fork, ARX bindings, HF auth, checkpoint conversion).
External submodule pointer for
external/openpiis intentionally leftuncommitted here; commit inside the submodule first if you want to
freeze the openpi rollout-fork rev.
Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com
ROLLOUT_INSTALL.md: document actual openpi state, not aspirational
The "Branches" section claimed external/openpi is on a fork branch with
the rollout patches "already committed" — it isn't. The submodule is
detached at upstream 981483d with the patches as uncommitted
working-tree edits, plus an untracked scripts/patch_transformers.py.
The fork has a pi-rollout-changes branch with overlapping patches, but
it diverges from this host's working tree (adds chex, loosens numpy /
opencv-python, patches pi0_pytorch.py; missing .python-version,
packages/openpi-client/pyproject.toml, uv.lock, patch_transformers.py).
Calling out the divergence so future-us doesn't merge them blindly.
Replaces the prior "checked out on a rollout branch" wording with an
explicit "openpi patches to apply on top of 981483d" checklist —
file-by-file, what to change and why — so the setup is reproducible
even without a clean fork branch.
Co-Authored-By: Claude Opus 4.7 (1M context) noreply@anthropic.com