Skip to content
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

On Windows, projects living at the root of a drive don't work #3783

Closed
wagenet opened this issue Mar 1, 2017 · 10 comments
Closed

On Windows, projects living at the root of a drive don't work #3783

wagenet opened this issue Mar 1, 2017 · 10 comments
Labels
A-workspaces Area: workspaces C-bug Category: bug O-windows OS: Windows

Comments

@wagenet
Copy link

wagenet commented Mar 1, 2017

I had a project that was directly mounted to E:. When I tried to run cargo I got the following unclear error: "error: invalid path url E:". I was able to resolve this problem by moving my project into a directory.

@alexcrichton
Copy link
Member

Hm I seem to be unable to reproduce this locally in a C: drive, do you have a set of instructions of how to reproduce? I'd be surprised if it was specific to E: as opposed to C:...

@wagenet
Copy link
Author

wagenet commented Mar 1, 2017

@alexcrichton I had a shared directory mounted to E: with a cargo project in that directory. Any cargo command that tried to do something with my code (i.e. not cargo -V, but cargo test) caused this error. Our project is also set up as a workspace with members inside of it.

@alexcrichton
Copy link
Member

Oh this may be related to the shared drive then maybe? We've had reports of fs::canonicalize returning errors in these situations in the past.

Could you gist the full error you saw as well as a description of the structure of the project (e.g. workspace layout)

@wagenet
Copy link
Author

wagenet commented Mar 7, 2017

There was no error message except what I posted. The project was a clone of https://github.com/tildeio/helix.

@carols10cents
Copy link
Member

This is the similar-sounding issue that has to do with fs::canonicalize: #2990

Given that this issue is stale, I'm going to close this.

@wagenet if this is still an issue, could you try running RUST_LOG=debug cargo build in the project on shared drive and reopen with a gist of the output? Thanks!

@wagenet
Copy link
Author

wagenet commented Oct 11, 2017

@carols10cents I'm still seeing issues with rust 1.22.0-nightly (d6d711dd8 2017-10-10). I'm not seeing any additional output beyond the single line error message. I'm investigating more right now.

@wagenet
Copy link
Author

wagenet commented Oct 11, 2017

Whoops, I forgot to add the RUST_LOG=debug. Here's the output I get:

$ RUST_LOG=debug cargo build
DEBUG:cargo::build: executing; cmd=cargo-build; args=["C:\\Users\\Peter\\.rustup\\toolchains\\nightly-x86_64-pc-windows-msvc\\bin\\cargo.exe", "build"]
DEBUG:cargo::core::workspace: find_root - is root Z:\Cargo.toml
DEBUG:cargo::core::workspace: find_members - Z:\examples\calculator\Cargo.toml
INFO:cargo::util::job::imp: found 0 remaining processes
DEBUG:cargo: exit_with_error; err=CliError { error: Some(CargoError(Msg("invalid path url `Z:`"), State { next_error: None, backtrace: None })), unknown: false, exit_code: 101 }
error: invalid path url `Z:`

@carols10cents
Copy link
Member

Interesting, thank you! Reopening!

@carols10cents carols10cents reopened this Oct 13, 2017
@carols10cents carols10cents added A-workspaces Area: workspaces C-bug Category: bug O-windows OS: Windows labels Oct 16, 2017
@stale
Copy link

stale bot commented Sep 20, 2018

As there hasn't been any activity here in over 6 months I've marked this as stale and if no further activity happens for 7 days I will close it.

I'm a bot so this may be in error! If this issue should remain open, could someone (the author, a team member, or any interested party) please comment to that effect?

The team would be especially grateful if such a comment included details such as:

  • Is this still relevant?
  • If so, what is blocking it?
  • Is it known what could be done to help move this forward?

Thank you for contributing!

(The cargo team is currently evaluating the use of Stale bot, and using #6035 as the tracking issue to gather feedback.)

If you're reading this comment from the distant future, fear not if this was closed automatically. If you believe it's still an issue please leave a comment and a team member can reopen this issue. Opening a new issue is also acceptable!

@stale stale bot added the stale label Sep 20, 2018
@stale
Copy link

stale bot commented Oct 20, 2018

As I didn't see any updates in 30 days I'm going to close this. Please see the previous comment for more information!

@stale stale bot closed this as completed Oct 20, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-workspaces Area: workspaces C-bug Category: bug O-windows OS: Windows
Projects
None yet
Development

No branches or pull requests

3 participants