-
Notifications
You must be signed in to change notification settings - Fork 0
Bump torch from 2.4.0+cu121 to 2.8.0 in /experiments/agentcompany/openhands #33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -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
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Prompt To Fix With AIThis 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. |
||
| tornado==6.4.1 | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
torchwas bumped to 2.8.0 buttorchaudioremains at 2.4.0 andtorchvisionat 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 causeImportErroror silent wrong-dispatch bugs at runtime when torchvision/torchaudio call into torch C++ internals. The expected companions for torch 2.8.0 aretorchvision==0.23.0andtorchaudio==2.8.0.Prompt To Fix With AI