[codex] Fix torch resolution on macOS x86_64#150
Open
anth-volk wants to merge 1 commit into
Open
Conversation
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.
Fixes #145
Summary
torchrequirements off that platform becausetorch==2.11.0does not publish macOS x86_64 wheels.Root Cause
uv sync --extra policyengineresolvedtorch==2.11.0, but that release only has macOS wheels for arm64. The project lock did not require uv to satisfy macOS x86_64, so the incompatibility surfaced only during install on Intel macOS.Validation
uv lock --checkuv run pytest tests/test_project_metadata.py -quv run ruff check tests/test_project_metadata.pyuv sync --extra policyengineon macOS x86_64, repeated after the fixuv run python -c "import importlib.util; print(importlib.util.find_spec('torch'))"returnedNoneon macOS x86_64, confirming torch is not installed on the unsupported platformNotes
The GitNexus MCP tools referenced in
AGENTS.mdwere not available in this session. I did not use the npm-distributed GitNexus CLI after user clarification; staged scope was validated with git diff/status and focused tests.