We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
$ rustup-toolchain-install-master c963187 detecting the channel of the `c963187` toolchain... error: toolchain `c963187` doesn't exist in any channel $ rustup-toolchain-install-master c963187c6f959417cbb13a33e9eaea4607696fc4 1 ✘ detecting the channel of the `c963187c6f959417cbb13a33e9eaea4607696fc4` toolchain... downloading <https://ci-artifacts.rust-lang.org/rustc-builds/c963187c6f959417cbb13a33e9eaea4607696fc4/rustc-nightly-x86_64-unknown-linux-gnu.tar.xz>... 50.60 MB / 50.60 MB [========================================================================================================================================================================] 100.00 % 11.49 MB/s downloading <https://ci-artifacts.rust-lang.org/rustc-builds/c963187c6f959417cbb13a33e9eaea4607696fc4/rust-std-nightly-x86_64-unknown-linux-gnu.tar.xz>... 24.49 MB / 24.49 MB [========================================================================================================================================================================] 100.00 % 10.94 MB/s toolchain `c963187c6f959417cbb13a33e9eaea4607696fc4` is successfully installed!
I'm not sure if it's possible to find the matching build for a truncated hash, but an error message might be useful here.
The text was updated successfully, but these errors were encountered:
Looks really similar to rust-lang/cargo-bisect-rustc#20 which was fixed by (me 🙈 ) @ rust-lang/cargo-bisect-rustc#33
It should be possible to do something similar here
Sorry, something went wrong.
The problem is that this project doesn't use git as a dependency.
git
I think a reasonable solution would be to check the revision string length and warn in a more friendly way.
Filed #43 for this.
Successfully merging a pull request may close this issue.
I'm not sure if it's possible to find the matching build for a truncated hash, but an error message might be useful here.
The text was updated successfully, but these errors were encountered: