I'm not sure if rust analyzer is supposed to be nightly only, didn't see any mention of that. But trying to update this morning I hit this.
―― 09:15:23 - rust analyzer ―――――――――――――――――――――――――――――――――――――――――――――――――――― Finished dev [unoptimized + debuginfo] target(s) in 0.38s Running `target/debug/ra_tools install-ra` will run: cargo install --path crates/ra_lsp_server --force Installing ra_lsp_server v0.1.0 (/home/jlusby/git/rust/rust-analyzer/crates/ra_lsp_server) Updating crates.io index Updating git repository `https://github.com/rust-lang/chalk.git` Downloaded ra_rustc_lexer v0.1.0-pre.3 Downloaded ra_vfs v0.2.7 Compiling autocfg v0.1.6 Compiling ra_rustc_lexer v0.1.0-pre.3 Compiling ra_vfs v0.2.7 error[E0554]: #![feature] may not be used on the stable release channel --> /home/jlusby/.cargo/registry/src/github.com-1ecc6299db9ec823/ra_rustc_lexer-0.1.0-pre.3/src/lib.rs:3:43 | 3 | #![cfg_attr(not(feature = "unicode-xid"), feature(unicode_internals))] | ^^^^^^^^^^^^^^^^^^^^^^^^^^ warning: ignoring -C extra-filename flag due to -o flag error: aborting due to previous error For more information about this error, try `rustc --explain E0554`. error: Could not compile `ra_rustc_lexer`. warning: build failed, waiting for other jobs to finish... error: failed to compile `ra_lsp_server v0.1.0 (/home/jlusby/git/rust/rust-analyzer/crates/ra_lsp_server)`, intermediate artifacts can be found at `/home/jlusby/git/rust/rust-analyzer/target` Caused by: build failed Error: "`cargo install --path crates/ra_lsp_server --force` exited with exit code: 101"
heh, I've published ra_rustc_lexer v0.1.0-pre.3 about a minute ago :-)
lol, blame topgrade for keeping me on the bleeding edge :P
not sure why it is picked up by you though: the lockfile should be on -pre.2 still...
Could you check if
Cargo.lock is not modfied and contains
master $ rg pre Cargo.lock 592: "number_prefix 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)", 874:name = "number_prefix" 1259:version = "0.1.0-pre.2" 1271: "ra_rustc_lexer 0.1.0-pre.2 (registry+https://github.com/rust-lang/crates.io-index)", 2115:"checksum number_prefix 0.2.8 (registry+https://github.com/rust-lang/crates.io-index)" = "dbf9993e59c894e3c08aa1c2712914e9e6bf1fcbfc6bef283e2183df345a4fee" 2137:"checksum ra_rustc_lexer 0.1.0-pre.2 (registry+https://github.com/rust-lang/crates.io-index)" = "6baccda91574dfadd7f8a0bc8f9f110f874b6b484289b2536d3dbf4f0d5d97bb"
Hm, could it be the case that
cargo install --path crates/ra_lsp_server --force ignores the lockfiles?
I've never touched the lockfile code in cargo so I don't know
i would be pretty surprised though
I figured its only supposed to run if you change the toml
its only supposed to ignore the lockfile when you change the cargo.toml8
but then it updates the lockfile as a result of the build usually right?
my lockfile doesnt have unstaged changes as a result of this build
If you really want to get to the bottom of this I'd say ping the cargo people on discord
Heh, I am a Cargo person unfortunately: https://github.com/rust-lang/cargo/graphs/contributors :D
cargo install --path crates/ra_lsp_server --force --locked should work (notice the
same, but im just starting :)
#13 on the list tho
movin' on up
And I think this might be the issue:
Updating crates.io index warning: package `getrandom v0.1.9` in Cargo.lock is yanked in registry `crates.io`, consider running without --locked
is that from your local run? I didn't see that yanked package message when I built it
I see it when I explicitelly pass
--locked to our installation procedure. Thanks for catching this @Jane Lusby !
ahaa, no problem and my pleasure!
today i learned about --locked so it was a very productive bug report :)
lmk if / when you push a fix so I can try updating again
@Jane Lusby that PR is merged, you can try updating again!
@matklad worked like a charm :tada: