Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion experiments/agentcompany/openhands/requirements.txt
Original file line number Diff line number Diff line change
Expand Up @@ -174,7 +174,7 @@ tiktoken==0.7.0
tinycss2==1.3.0
tokenizers==0.20.3
tomli==2.0.1
torch==2.4.0+cu121
torch==2.8.0
torchaudio==2.4.0+cu121
torchvision==0.19.0
Comment on lines +177 to 179

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 torch/torchaudio/torchvision version mismatch

torch was bumped to 2.8.0 but torchaudio remains at 2.4.0 and torchvision at 0.19.0 — both of which correspond to the torch 2.4.x release train. These three packages must be kept in lockstep; mismatched versions cause ImportError or silent wrong-dispatch bugs at runtime when torchvision/torchaudio call into torch C++ internals. The expected companions for torch 2.8.0 are torchvision==0.23.0 and torchaudio==2.8.0.

Prompt To Fix With AI
This is a comment left during a code review.
Path: experiments/agentcompany/openhands/requirements.txt
Line: 177-179

Comment:
**torch/torchaudio/torchvision version mismatch**

`torch` was bumped to 2.8.0 but `torchaudio` remains at 2.4.0 and `torchvision` at 0.19.0 — both of which correspond to the torch 2.4.x release train. These three packages must be kept in lockstep; mismatched versions cause `ImportError` or silent wrong-dispatch bugs at runtime when torchvision/torchaudio call into torch C++ internals. The expected companions for torch 2.8.0 are `torchvision==0.23.0` and `torchaudio==2.8.0`.

How can I resolve this? If you propose a fix, please make it concise.

Fix in Cursor Fix in Claude Code Fix in Codex

Comment on lines +177 to 179

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 CUDA build variant dropped for torch

torch was changed from torch==2.4.0+cu121 to torch==2.8.0 (no CUDA suffix), while torchaudio==2.4.0+cu121 still carries the +cu121 CUDA tag. Without the +cu121 variant specifier (and the corresponding --extra-index-url https://download.pytorch.org/whl/cu121), pip will resolve torch==2.8.0 to whichever wheel is on PyPI — which may be the CPU-only build. If CUDA acceleration is required in this environment, the CUDA-tagged build should be specified consistently across all three PyTorch packages.

Prompt To Fix With AI
This is a comment left during a code review.
Path: experiments/agentcompany/openhands/requirements.txt
Line: 177-179

Comment:
**CUDA build variant dropped for torch**

`torch` was changed from `torch==2.4.0+cu121` to `torch==2.8.0` (no CUDA suffix), while `torchaudio==2.4.0+cu121` still carries the `+cu121` CUDA tag. Without the `+cu121` variant specifier (and the corresponding `--extra-index-url https://download.pytorch.org/whl/cu121`), pip will resolve `torch==2.8.0` to whichever wheel is on PyPI — which may be the CPU-only build. If CUDA acceleration is required in this environment, the CUDA-tagged build should be specified consistently across all three PyTorch packages.

How can I resolve this? If you propose a fix, please make it concise.

Fix in Cursor Fix in Claude Code Fix in Codex

tornado==6.4.1
Expand Down