Pin Torch version to <2.2.0 #2394
Merged
Conversation
This file contains 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
|
The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update. |
|
Merging this as an emergency measure so we can fix the transformers CI - it's a one-line change, and we can discuss/revert it later if it's an issue! |
|
Why do we need torch to be less than 2.2.0? |
|
CI failures - we'll unpin it soon, I'm sure! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
See huggingface/transformers#28785 - torch 2.2.0 was pushed to pypi and broke the CI. We pinned the version in Transformers, but because it installs accelerate from
mainat the end of the other installations, we need to pin the version inaccelerateas well, or theaccelerateinstallation upgrades totorch 2.2.0regardless.