unable to install nushell plugins on Windows 11 #14234
Replies: 3 comments 5 replies
-
|
If rust is installed properly in Windows and you can compile other rust programs without issue, then it's probably not the rust install with the msvc toolchains or the Visual Studio components install since rust building will use Visual Studio's compiler. If you're running nushell and you try to compile/install nushell in Windows, you'll get an access violation because you can't really overwrite a running program in Windows. (This is by design for Windows. Nushell has no say in this) If you have an underpowered PC, you may have issues. I've been able to compile nushell, polars, and any other program with 16GB of ram and a 5 or 6 year old CPU (can't remember which cpu i have right now). The place I would start is just cloning the repo, cd to the nushell folder, and do If that all works, then I'd try If you still have errors, it would be more helpful to post the error instead of describing it. Others may be able to jump in and help. |
Beta Was this translation helpful? Give feedback.
-
|
After four failed attempts without a PC lockup or crash, I was able to |
Beta Was this translation helpful? Give feedback.
-
|
Having an elevated terminal isn't required to compile nushell. I rarely have my terminal elevated. I'm not sure what these STATUS_ACCESS_VIOLATION's are about. About the only time I have compile failures is when I'm out of disk space. Maybe someone will have an idea. |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, I just used elevated to rule out any permissions/access issues. I found lots of reports of similar issues. At least some of them turned out to be upstream LLVM bugs. |
Beta Was this translation helpful? Give feedback.
-
|
I tried |
Beta Was this translation helpful? Give feedback.
-
|
If your PC crashes, I feel like it's a RAM/MB issue, not software issue - not sure how to test that though. |
Beta Was this translation helpful? Give feedback.
-
|
If it weren't for the consistent STATUS_ACCESS_VIOLATION errors I'd be inclined to agree with you. As it stands, I'm inclined to think there's a compiler bug. |
Beta Was this translation helpful? Give feedback.
-
|
Maybe you can init a blank rust project and add the failed crate to test, for instance, 'chardetng', if you can successfully compile by recent rust, maybe you can try use the same rust version to build nushell. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I feel like I'm missing something, so I'll start here and open an issue later if need be. I run nushell on macOS at work, and I thought it would be lovely to have the same shell on my PC. If I use a prebuilt binary from scoop, winget, github, etc., nushell runs just fine. I particularly wanted the polars plugin because I want to crunch some data, but
cargo install nu_plugin_polarsfails with heap overflows and memory overruns status access violations and fairly consistently either crashes my PC altogether or locks it up entirely.I initially thought something might be jacked up with my Rust install, so I nuked and paved that. Same results. Then I thought maybe something was jacked with my Windows install because it had unceremoniously been crashed so many times while trying to install plugins with cargo, so I clean-installed Windows last night. Fresh Rust install with fresh prereqs (as far as I can tell).
I installed Rust 1.82.0 and 1.80.1 with rustup, and since I had problems after letting rustup-init automatically install Visual Studio, I tried following the manual installation instructions. Here's what I have:
I couldn't tell if it was entirely necessary, but I ran
cargo install cargo-llvm-covandcargo llvm-cov clean, and then I cloned the nushell repo, opened that dir in an elevated Visual Studio developer terminal, and ranpowershell scripts\install-all.ps1from the root of the repo. That also failed spectacularly, successfully building precisely nothing the first time and locking up my PC the second.Now, this isn't my first rodeo, so I'm starting with the assumption that despite rtfm'ing I'm missing some crucial dependency somewhere. Does anything obvious stand out here that I should have installed/configured as a pre-req? If not, what all do you need for me to open an issue?
Beta Was this translation helpful? Give feedback.
All reactions