How To Update Client For Rust Mac

Join GitHub today

How To Update Mac Computer
How To Update Client For Rust Mac Requirements
Rust Download Mac

GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.

We release an update every month. Each patch brings significant additions and features to the game. Each patch brings significant additions and features to the game. We also include an assortment of performance improvements, balance changes, and bug fixes. Rust is a programming language that is under constant development, aimed to provide users with a reliable means of creating client / server software which works over the Internet.

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

Comments

commented Dec 25, 2017

It's in the title. Looks like you can't install rls-preview anymore (or even rls) with the latest nightly.

commented Dec 26, 2017

commented Dec 28, 2017•
edited

For those who made it here looking for a workaround, the most recent toolchain I found which still has rls-preview is nightly-2017-12-21.

Then in your VSCode user settings:

commented Dec 28, 2017

It's annoying, so I wrote a simple script to help you find the latest nightly version containing rls-preview, have a try🤪

or just do this

commented Dec 28, 2017

To ease the pain, one can use @alexheretic's script to see if the new version contains the rls component: rust-lang/rustup.rs#1301 (comment)

commented Dec 28, 2017

@crazymousethief ah, you were faster! 😉
Attaching the script from the linked comment:

commented Dec 28, 2017

@Xanewok Wow, thanks, I will use it for the next upgrade🎉

How To Update Mac Computer

commented Dec 29, 2017

seeing same issue with windows. when will the core rustup issue get fixed?

commented Dec 29, 2017

Hopefully the rls and rustfmt will be included in today's nightly, as per rust-lang-nursery/rust-toolstate@ac83be8

commented Dec 30, 2017

rls-preview component should be available in the 2017-12-30 nightly build (https://static.rust-lang.org/dist/channel-rust-nightly.toml)!

commented Jan 12, 2018•
edited

You can check the nightly RLS status over at https://rust-lang-nursery.github.io/rust-toolstate/ (thanks @kennytm!).
There's also a state-changing commit next to the tool listed, so if it's currently listed as failing, fetching and using a toolchain from day before will likely be enough.

Closing this as there's no way we can 'fix' the issue instead of somehow always guaranteeing that the tool builds with every commit in Rust CI. The information here should be enough to help users with what to do when the rls component is missing in nightly.

commented Jan 13, 2018

I guess it is not easy to just bundle the last working one, compiled against the old compiler?

commented Jan 13, 2018

Well, that's actually a fair point. I imagine tool can't be broken for more than few days, so possible desync between current nightly compiler and the one rls has last successfully built against won't be much of an issue.
@nrc@kennytm is this something we might consider doing/worth the work?

commented Jan 13, 2018

I don't think it is that easy. When loading, the dynamic linker looks for a specific library. Even if nothing changed, I think it would still count as a different library, but stuff would change (even if it is not API the RLS uses) and that means the RLS executable wouldn't be able to find the ABI it needs.

commented Jan 18, 2018•
edited

Closing this as there's no way we can 'fix' the issue instead of somehow always guaranteeing that the tool builds with every commit in Rust CI.

@Xanewok Considering that rls is supposed to become part of the standard set of components managed by rustup, why is this an unreasonable thing to do? But, thank you for making that website! It's nice to have somewhere to look.

commented Jan 18, 2018

I don't think it is that easy. When loading, the dynamic linker looks for a specific library

Well, the older RLS could bundle its copy of the old old library too. I don't know how easy or hard would that be to do and it would make the rls component significantly bigger. Not saying that's worth it, though.

commented Feb 3, 2018

Has it disappeared from Nightly again?

commented Feb 3, 2018

Nope. As linked above, there is a website that shows whether RLS was in the latest nightly or not. I just confirmed locally that RLS is part of the latest nightly, if you follow the instructions to install it.

commented Feb 3, 2018

ok thanks @coder543 looks like i must have uninstalled it, i reinstalled it and its working now

commented Aug 24, 2018•
edited

Gone again for rustc 1.30.0-nightly (63d66494a 2018-08-23) and rustc 1.30.0-nightly (d41f21f11 2018-08-24).

To get back into a working state, do the following:
rustup toolchain install nightly-2018-08-19
(I found the previous nightly by counting down from the date of the latest nightly until I found an existing previous nightly. Please holler if you know of a better way involving less trial & error. The only resource I'm aware of is https://static.rust-lang.org/dist/index.html )

List the installed toolchains to find the platform-specific name of the just installed toolchain:
rustup toolchain list
In my case, the correct value would be nightly-2018-08-19-x86_64-apple-darwin.

Set default to that toolchain:
rustup default nightly-2018-08-19-x86_64-apple-darwin

Install RLS for that toolchain:
rustup component add rls-preview rust-analysis rust-src

Leaving this step-by-step instruction here because this issue shows up when you google the problem.

commented Aug 24, 2018

Yep it has disappeared again on linux too, just like the old days. My understanding was that rust releases would be blocked on rls now, so this shouldn't happen. Hopefully this is just a mistake.

Nice to see my atom ide-rust code still handling this case well. But I'm less impressed with rustup update printing a warning that rls is missing then just updating anyway :/.

Closed

Open

commented Aug 25, 2018

@huxi I've tried to downgrade nightly and now I'm getting command 'rls.restart' not found. Do you know why that might happen? Thanks!

commented Aug 25, 2018

@Kane-Sendgrid If this is an error in an IDE like VS Code then it might help to restart the IDE. Not aware of this error in particular but had some errors like that in the past after upgrading. Restarting the IDE helped.

commented Aug 25, 2018

@huxi yeah, that comes from IDE (vs code), rls works separately, I guess I'll try to bug plugin team (restart doesn't help).

Thanks!

commented Aug 26, 2018

RLS is present again in today's nightly. Sorry for the disruption.

commented Aug 29, 2018

😐

commented Aug 29, 2018•
edited

I also thought it was supposed to block if components were not available but now this horrible thing happened:

and it continued to remove my old install and 'update' to something that is obviously useless.

commented Aug 29, 2018

Suddenly I get the same error after trying to update the toolchains (everything was up to date though):
toolchain 'nightly-x86_64-apple-darwin' does not contain component 'rls-preview' for target 'x86_64-apple-darwin'

commented Aug 30, 2018

Should be back again today and we're looking into why the update went badly

commented Aug 30, 2018

@nrc Could you please make sure we can make sure we always have rls, clippy and so on included?

commented Aug 30, 2018

Thanks for fixing it so quickly. I think the best case is for rustup to just refuse to do the update if currently added components are not available. This could be overridden by a --force, or even require the user to remove the component first before updating. That way you can be certain an existing working install won't be trashed.

commented Aug 30, 2018

Could you please make sure we can make sure we always have rls, clippy and so on included?

We were doing this, but the tools were breaking so often that we didn't get a nightly for more than a week, so we had to change to issuing nightlies without broken tools.

I think the best case is for rustup to just refuse to do the update if currently added components are not available. This could be overridden by a --force

This is what should happen, but we've had a few teething troubles. Hopefully they are all resolved now.

commented Sep 2, 2018

commented Sep 2, 2018•
edited

(rustup 1.13.0)

So at least the update aborted this time, which is already better! :)

commented Sep 3, 2018

After a clean install of rustup and the toolchain:

commented Sep 3, 2018

FYI; the current latest nightly containing RLS seems to be this one for me:

commented Sep 6, 2018

There seems to be a new nightly out that fixes this: rust version 1.30.0-nightly (6e0f1cc15 2018-09-05)

commented Sep 24, 2018

Looks like the latest nightly for Mac is missing rls-preview, so I just had to install the one from yesterday:

commented Dec 1, 2018

I'm on 1.32 nightly. How do I get rls working in vscode again?

Closed

commented Dec 10, 2018

rustc 1.32.0-nightly (4a45578bc 2018-12-07) - toolchain without rls rustfmt and clippy?
In nightly list of components - rls, rustfmt and clippy not exists.

commented Dec 10, 2018•
edited

On these pages, you can see that the last nightly with rls-preview is 2018-12-06:
https://rust-lang-nursery.github.io/rust-toolstate/
https://mexus.github.io/rustup-components-history/

I believe the solution is to install that nightly until there is a more up-to-date nightly with rls-preview working.

commented Dec 11, 2018

Whats the reason rls keeps dropping out from nightly?

commented Dec 11, 2018

Whats the reason rls keeps dropping out from nightly?

Here's how I understand it. The development of rustc's internals is quite fast paced. Downstream projects that rely on nightly internals, particularly clippy, can break fairly often because of this.

Rust can either not release a nightly when this happens, or release one without clippy & rls. They did follow the former strategy for a while, but now follow the latter to avoid blocking the rust nightly releases for over-long periods for people that don't need clippy/rls.

To mitigate the issues we have:

rustup will warn if the update is missing any components you currently have. This means you can no longer accidently update to a no-rls release. Once rls is available again it'll update.
rls, clippy are available on the stable channel. Meaning most developers installing for the first time should use stable.
However, if you need latest nightly rls you can use https://mexus.github.io/rustup-components-history/ to find and install a dated nightly release ie rustup install nightly-2018-12-06. Or use atom ide-rust which can pick out the latest for you automatically ;)

commented Dec 11, 2018

Thanks @alexheretic great answer

Closed