[Windows support] Very long filenames #40
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
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.
The
huggingface_hubdownloads files with very long filenames (135 characters). Since these files may be downloaded to any arbitrary folder, the total length of the path may exceed the 260 character limit imposed by some Windows versions, as visible hereThis PR allows identifying if we're running on the Windows platform and if so checks the absolute length of both the lock file and the actual file to be downloaded. If either of the two resulting paths is too long, it concatenates the
\\?\prefix that specifies it is an extended path, which has a limit of 32k+ characters.Closes #35