-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Crate failed to unpack on Windows (os error 3) - path name too long #2516
Comments
What version of Cargo were you using for this? It looks like this may be similar to #2309 where the path name is just too long in the servo-skia crate |
2016-03-04 version for servo/servo#10089 and 2015-10-01 for servo/servo#9442 (based on github history) |
The "spaces in path" mentioned in servo/servo#9442 I don't think have anything to do with Cargo. It sounded like that was primarily for makefiles and various scripts here and there which didn't properly escape spaces, but Cargo doesn't have to worry about any of that. For servo/servo#10089 the error message is "The system can not find the path specified" for a path name with 263 bytes in it, which on my system returns "The filename or extension is too long". I suspect a different version of Windows may have been in use which had a different error for the report. |
This doesn’t significantly affect the size of tarballs, but make them not include some files with very long paths like gm/rebaseline_server/testdata/outputs/expected/compare_rendered_pictures_test.CompareRenderedPicturesTest.test_endToEnd/compare_rendered_pictures.json This will hopefull help on Windows: http://logs.glob.uno/?c=mozilla%23servo#c403696 https://i.imgur.com/JeBRLlE.png rust-lang/cargo#2516 http://logs.glob.uno/?c=mozilla%23servo#c403699 The longest path from the crate root is now 65, down from 150. third_party/freetype/include_overrides/freetype/config/ftoption.h I’ve checked that `cargo build --target arm-linux-androideabi` still succeeds when run on the result of extracting the tarball.
This doesn’t significantly affect the size of tarballs, but make them not include some files with very long paths like gm/rebaseline_server/testdata/outputs/expected/compare_rendered_pictures_test.CompareRenderedPicturesTest.test_endToEnd/compare_rendered_pictures.json This will hopefully help on Windows: http://logs.glob.uno/?c=mozilla%23servo#c403696 https://i.imgur.com/JeBRLlE.png rust-lang/cargo#2516 http://logs.glob.uno/?c=mozilla%23servo#c403699 The longest path from the crate root is now 65, down from 150. third_party/freetype/include_overrides/freetype/config/ftoption.h I’ve checked that `cargo build --target arm-linux-androideabi` still succeeds when run on the result of extracting the tarball.
This doesn’t significantly affect the size of tarballs, but make them not include some files with very long paths like gm/rebaseline_server/testdata/outputs/expected/compare_rendered_pictures_test.CompareRenderedPicturesTest.test_endToEnd/compare_rendered_pictures.json This will hopefully help on Windows: http://logs.glob.uno/?c=mozilla%23servo#c403696 https://i.imgur.com/JeBRLlE.png rust-lang/cargo#2516 http://logs.glob.uno/?c=mozilla%23servo#c403699 The longest path from the crate root is now 65, down from 150. third_party/freetype/include_overrides/freetype/config/ftoption.h I’ve checked that `cargo build --target arm-linux-androideabi` still succeeds when run on the result of extracting the tarball.
Exclude more directories in Cargo.toml This doesn’t significantly affect the size of tarballs, but make them not include some files with very long paths like ``` gm/rebaseline_server/testdata/outputs/expected/compare_rendered_pictures_test.CompareRenderedPicturesTest.test_endToEnd/compare_rendered_pictures.json ``` This will hopefully help on Windows: http://logs.glob.uno/?c=mozilla%23servo#c403696 https://i.imgur.com/JeBRLlE.png rust-lang/cargo#2516 http://logs.glob.uno/?c=mozilla%23servo#c403699 The longest path from the crate root is now 65, down from 150. ``` third_party/freetype/include_overrides/freetype/config/ftoption.h ``` I’ve checked that `cargo build --target arm-linux-androideabi` still succeeds when run on the result of extracting the tarball. r? @mbrubeck <!-- Reviewable:start --> --- This change is [<img src="https://reviewable.io/review_button.svg" height="35" align="absmiddle" alt="Reviewable"/>](https://reviewable.io/reviews/servo/skia/91) <!-- Reviewable:end -->
I just encountered this with neon-sys. Apparently cargo can't unpack crates that cause paths that are too long. This is not an issue of Windows though, as I was able to manually unzip it with WinRAR. So this is definitely a bug in cargo. This was the path that was causing trouble:
|
I have the same problem |
I have the same problem when I try to install cargo-edit-locally using the cargo install command. Here is the entire stacktrace (C:\Users\Administrator\anaconda3) C:\Users\Administrator\source\AzureMlCli\dataprep\Core\rust_lex\rslex-http-stream>cargo install cargo-edit-locally Caused by: Caused by: Caused by: Caused by: Caused by: Caused by: Caused by: |
I rewrote the code to this form, and it does not crash the program, but there is one thing, but, as I said, the program cannot find the path to the file, although it exists, and that’s the essence of the question, how to fix this? It produces the following error, Error: The system cannot find the specified path. (os error 3) |
Failed if path has spaces servo/servo#9442
and also for unknown reason servo/servo#10089 (maybe too many subfolders or capital letters?)
or something wrong with crate
servo-skia
?The text was updated successfully, but these errors were encountered: