-
Notifications
You must be signed in to change notification settings - Fork 926
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
Change default for RUSTUP_WINDOWS_PATH_ADD_BIN #3703
Conversation
8dc8a39
to
a34d06a
Compare
Just raising that this seems to have broken |
As an additional data point, Dylint is currently using It may be that we could set |
Can one of you open a new issue discussing what the use case here is and how/why we broke it? |
Fixes #267! For more context, see [this comment](#267 (comment)): > I found the issue! Due to [rust-lang/rustup#3703](rust-lang/rustup#3703), Rustup no longer modifies the `PATH` on Windows because it prevented sub-invocations of `cargo` and `rustc` from going through their proxy. There was a [call for testing](https://internals.rust-lang.org/t/help-test-windows-behavior-between-rustup-and-cargo/20237) related to this, but it was announced before the linter was ever created. Because I don't use Windows frequently, I never caught the issue. > > We can fix this by setting `RUSTUP_WINDOWS_PATH_ADD_BIN=1`: > > ```cmd > > set RUSTUP_WINDOWS_PATH_ADD_BIN=1 > > rustup run nightly-2025-01-09 .\bevy_lint.exe > ```
This changes the default for the RUSTUP_WINDOWS_PATH_ADD_BIN opt-in to fix the issue where adding the
bin
directory on windows was preventing recursive calls to programs like cargo from being able to use the rustup proxies.There was a call for testing at https://internals.rust-lang.org/t/help-test-windows-behavior-between-rustup-and-cargo/20237 and https://users.rust-lang.org/t/help-test-windows-behavior-between-rustup-and-cargo/106145. AFAIK, there have not been any indications of anyone having problems.
Fixes #3036