Skip to content
This repository has been archived by the owner on Dec 29, 2022. It is now read-only.

Component rls unavailable for download - README hints do not suffice #1758

Open
AndiDog opened this issue Jan 10, 2022 · 5 comments
Open

Component rls unavailable for download - README hints do not suffice #1758

AndiDog opened this issue Jan 10, 2022 · 5 comments

Comments

@AndiDog
Copy link

AndiDog commented Jan 10, 2022

The README says to pin to a specific version found at https://rust-lang.github.io/rustup-components-history/ – however, that site only shows the last 7 days. It currently (at time of writing: 2022-01-10) does not even list "rls" anywhere, likely because no recent RLS builds are available for the nightly toolchain. Thus, I had to trick around like this

for n in $(seq 10 30); do if rustup toolchain add nightly-2021-11-${n} -c rls; then break; fi; done

in order to find that the latest available toolchain with RLS was 2021-11-09 at the time.

Other, more obvious solutions such as finding the latest successful CI build (linked from the button in the README: https://github.com/rust-lang/rls/actions?query=workflow%3ACI+branch%3Amaster) did not work for me, likely because their date does not necessarily relate directly to the (nightly) toolchain release date.

Having to pin a version isn't super bad, but then users should be given better hints how to solve it. Modern Rust projects often require nightly builds, so having RLS is essential for developer experience.

@ms140569
Copy link

According to this site:

https://rust-lang-nursery.github.io/rust-toolstate/

the latest available build of RLS was 2021-12-04. I've doublechecked and this is correct, but it took me quite a while to get there. Therefore i totally agree with @AndiDog that there need to be better ways to figure this out ...

@MingweiSamuel
Copy link
Contributor

MingweiSamuel commented Jan 14, 2022

@calebcartwright
Copy link
Member

This is going to become significantly less of an issue now that RLS has removed the auto-publish crates from its dependency tree, and will become completely obviated if/when RLS moves to the subtree model.

Worth noting, however, that those looking for a RLS containing nightly can always use the in-repo toolchain file as a reference, using that date, potentially plus a day or two to account for release delays.

Users that have a previously installed nightly toolchain containing RLS and want to update to the latest RLS-containing nightly can utilize rustup's default behavior, which will update to the latest version that contains the components you already have installed.

Those two, combined if necessary, should cover most/all scenarios.

@MingweiSamuel
Copy link
Contributor

About rustup, it seems to only go back a few weeks to check for needed components before failing, and since RLS hasn't built in longer than that it just fails currently

@calebcartwright
Copy link
Member

About rustup, it seems to only go back a few weeks to check for needed components before failing, and since RLS hasn't built in longer than that it just fails currently

Well TIL 🎓

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants