You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The reason will be displayed to describe this comment to others. Learn more.
This toolchain doesn't have rls available - is this intentional? Sorry if this is a silly question, just trying to get my environment set up properly for contributing
❯ rustup component add rls
error: component 'rls' for target 'x86_64-unknown-linux-gnu' is unavailable for download for channel 'nightly-2021-12-29'
Sometimes not all components are available in any given nightly. If you don't need the component, you can remove it with:
rustup component remove --toolchain nightly-2021-12-29 --target x86_64-unknown-linux-gnu rls
The reason will be displayed to describe this comment to others. Learn more.
The channel in this file will always be very intentional, but the exact value is driven by requirements not really applicable with standard application usage. Like most of the official tools, rustfmt is heavily reliant on the private compiler internals, so updates to this are based on private compiler APIs as opposed to standard dev loop usage (like component or feature availability).
The RLS availability issue was long lasting, though resolved and unlikely to recur (at least at that duration), so you could try using a newer nightly; this is just reflective of the fact that nothing pre-this channel can be used
The reason will be displayed to describe this comment to others. Learn more.
And if you find you can't use one of the latest nightlies that contain RLS, you can always run the rustup command with the --force flag to tell it to proceed despite the missing component (fwiw you may want to use RA anyway)
50bbb43There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This toolchain doesn't have
rlsavailable - is this intentional? Sorry if this is a silly question, just trying to get my environment set up properly for contributing50bbb43There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The channel in this file will always be very intentional, but the exact value is driven by requirements not really applicable with standard application usage. Like most of the official tools, rustfmt is heavily reliant on the private compiler internals, so updates to this are based on private compiler APIs as opposed to standard dev loop usage (like component or feature availability).
The RLS availability issue was long lasting, though resolved and unlikely to recur (at least at that duration), so you could try using a newer nightly; this is just reflective of the fact that nothing pre-this channel can be used
50bbb43There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And if you find you can't use one of the latest nightlies that contain RLS, you can always run the rustup command with the
--forceflag to tell it to proceed despite the missing component (fwiw you may want to use RA anyway)