found unstable fingerprints - Cargo build when installing dependencies.rocket_contrib - Rust 1.52.0

[superjose]

Hi guys 🤗. I'm tinkering with Rust (Nightly 1.52.0) and I was including Rocket's contrib package into the cargo.toml.

The project blew up when I tried to build it. It said to summit the issue, so here I am.

Code

Cargo.toml

[package]
name = "backend"
version = "0.1.0"
authors = ["Jose Asilis <superjose_49@hotmail.com>"]
edition = "2018"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[dependencies]
rocket = "0.4.7"

[dependencies.rocket_contrib]
version = "0.4.7"
default-features = false
features = ["json", "serve"]

#![feature(proc_macro_hygiene, decl_macro)]

#[macro_use] extern crate rocket;

mod routes;

use routes::hello::hello_world;


#[get("/")]
fn index() -> &'static str {
    "Hello, world!"
}

fn main() {
    
    rocket::ignite().mount("/api", routes![index, hello_world::world, hello_world::user]).launch();
}

Meta

rustc --version --verbose:

rustc 1.52.0-nightly (f5d8117c3 2021-03-16)
binary: rustc
commit-hash: f5d8117c338a788bd24abec733fd143dfceb25a0
commit-date: 2021-03-16
host: x86_64-pc-windows-msvc
release: 1.52.0-nightly
LLVM version: 12.0.0

Error output

 Compiling winapi v0.3.9
   Compiling ryu v1.0.5
   Compiling serde_json v1.0.64
   Compiling itoa v0.4.7
   Compiling time v0.1.43
   Compiling winapi-util v0.1.5
   Compiling filetime v0.2.14
   Compiling atty v0.2.14
   Compiling same-file v1.0.6
   Compiling walkdir v2.3.1
   Compiling hyper v0.10.16
   Compiling cookie v0.11.4
   Compiling notify v4.0.15
   Compiling rocket_http v0.4.7
   Compiling rocket_codegen v0.4.7
   Compiling rocket v0.4.7
   Compiling rocket_contrib v0.4.7
   Compiling backend v0.1.0 (C:\Users\asili\Dropbox\Programming\rust-svelte\backend)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

error: internal compiler error: unexpected panic

note: the compiler unexpectedly panicked. this is a bug.

note: we would appreciate a bug report: https://github.com/rust-lang/rust/issues/new?labels=C-bug%2C+I-ICE%2C+T-compiler&template=ice.md

note: rustc 1.52.0-nightly (f5d8117c3 2021-03-16) running on x86_64-pc-windows-msvc

note: compiler flags: -C embed-bitcode=no -C debuginfo=2 -C incremental --crate-type bin

note: some of the compiler flags provided by cargo are hidden

query stack during panic:
#0 [predicates_of] computing predicates of `std::convert::From`
#1 [typeck] type-checking `main`
end of query stack
error: could not compile `backend`

Backtrace

   Fresh version_check v0.9.3
       Fresh cfg-if v1.0.0
       Fresh yansi v0.5.0
       Fresh subtle v2.4.0
       Fresh unicode-xid v0.1.0
       Fresh opaque-debug v0.3.0
       Fresh tinyvec_macros v0.1.0
       Fresh matches v0.1.8
       Fresh cpuid-bool v0.2.0
       Fresh version_check v0.1.5
       Fresh autocfg v1.0.1
       Fresh ppv-lite86 v0.2.10
       Fresh percent-encoding v1.0.1
       Fresh byteorder v1.4.3
       Fresh safemem v0.3.3
       Fresh cpuid-bool v0.1.2
       Fresh typeable v0.1.2
       Fresh percent-encoding v2.1.0
       Fresh base64 v0.13.0
       Fresh traitobject v0.1.0
       Fresh language-tags v0.2.2
       Fresh hashbrown v0.9.1
       Fresh state v0.4.2
       Fresh smallvec v1.6.1
       Fresh glob v0.3.0
       Fresh itoa v0.4.7
       Fresh base64 v0.12.3
       Fresh tinyvec v1.1.1
       Fresh unicode-bidi v0.3.4
       Fresh base64 v0.9.3
       Fresh typenum v1.13.0
       Fresh winapi v0.3.9
       Fresh proc-macro2 v0.4.30
       Fresh libc v0.2.89
       Fresh getrandom v0.2.2
       Fresh log v0.4.14
       Fresh unicode-normalization v0.1.17
       Fresh bitflags v1.2.1
       Fresh httparse v1.3.5
       Fresh serde v1.0.124
       Fresh memchr v2.3.4
       Fresh ryu v1.0.5
       Fresh generic-array v0.14.4
       Fresh quote v0.6.13
       Fresh rand_core v0.6.2
       Fresh time v0.1.43
       Fresh idna v0.1.5
       Fresh log v0.3.9
       Fresh unicase v1.4.2
       Fresh num_cpus v1.13.0
       Fresh winapi-util v0.1.5
       Fresh atty v0.2.14
       Fresh filetime v0.2.14
       Fresh syn v0.15.44
       Fresh cipher v0.2.5
       Fresh digest v0.9.0
       Fresh universal-hash v0.4.0
       Fresh crypto-mac v0.10.0
       Fresh rand_chacha v0.3.0
       Fresh aead v0.3.2
       Fresh block-buffer v0.9.0
       Fresh url v1.7.2
       Fresh indexmap v1.6.2
       Fresh toml v0.4.10
       Fresh serde_json v1.0.64
       Fresh aes-soft v0.6.4
       Fresh polyval v0.4.5
       Fresh ctr v0.6.0
       Fresh hmac v0.10.1
       Fresh rand v0.8.3
       Fresh mime v0.2.6
       Fresh devise_core v0.2.0
       Fresh pear_codegen v0.1.4
       Fresh same-file v1.0.6
       Fresh aes v0.6.0
       Fresh ghash v0.3.1
       Fresh hkdf v0.10.0
       Fresh sha2 v0.9.3
       Fresh hyper v0.10.16
       Fresh aes-gcm v0.8.0
       Fresh pear v0.1.4
       Fresh devise_codegen v0.2.0
       Fresh walkdir v2.3.1
       Fresh cookie v0.11.4
       Fresh devise v0.2.0
       Fresh notify v4.0.15
       Fresh rocket_http v0.4.7
       Fresh rocket_codegen v0.4.7
       Fresh rocket v0.4.7
       Fresh rocket_contrib v0.4.7
   Compiling backend v0.1.0 (C:\Users\asili\Dropbox\Programming\rust-svelte\backend)
     Running `rustc --crate-name backend --edition=2018 src\main.rs --error-format=json --json=diagnostic-rendered-ansi --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debuginfo=2 -C metadata=ca958e3483787192 --out-dir C:\Users\asili\Dropbox\Programming\rust-svelte\backend\target\debug\deps -C incremental=C:\Users\asili\Dropbox\Programming\rust-svelte\backend\target\debug\incremental -L dependency=C:\Users\asili\Dropbox\Programming\rust-svelte\backend\target\debug\deps --extern rocket=C:\Users\asili\Dropbox\Programming\rust-svelte\backend\target\debug\deps\librocket-c54f70af5f4dbef5.rlib --extern rocket_contrib=C:\Users\asili\Dropbox\Programming\rust-svelte\backend\target\debug\deps\librocket_contrib-2de34e6aa1ef0f4e.rlib`
thread 'rustc' panicked at 'found unstable fingerprints for predicates_of(core[f48f]::convert::From)', /rustc/f5d8117c338a788bd24abec733fd143dfceb25a0\compiler\rustc_query_system\src\query\plumbing.rs:593:5
stack backtrace:
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

error: internal compiler error: unexpected panic

note: the compiler unexpectedly panicked. this is a bug.

note: we would appreciate a bug report: https://github.com/rust-lang/rust/issues/new?labels=C-bug%2C+I-ICE%2C+T-compiler&template=ice.md

note: rustc 1.52.0-nightly (f5d8117c3 2021-03-16) running on x86_64-pc-windows-msvc

note: compiler flags: -C embed-bitcode=no -C debuginfo=2 -C incremental --crate-type bin

note: some of the compiler flags provided by cargo are hidden

query stack during panic:
#0 [predicates_of] computing predicates of `std::convert::From`
#1 [typeck] type-checking `main`
#2 [typeck_item_bodies] type-checking all item bodies
#3 [analysis] running analysis passes on this crate
end of query stack
error: could not compile `backend`

Caused by:
  process didn't exit successfully: `rustc --crate-name backend --edition=2018 src\main.rs --error-format=json --json=diagnostic-rendered-ansi --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debuginfo=2 -C metadata=ca958e3483787192 --out-dir C:\Users\asili\Dropbox\Programming\rust-svelte\backend\target\debug\deps -C incremental=C:\Users\asili\Dropbox\Programming\rust-svelte\backend\target\debug\incremental -L dependency=C:\Users\asili\Dropbox\Programming\rust-svelte\backend\target\debug\deps --extern rocket=C:\Users\asili\Dropbox\Programming\rust-svelte\backend\target\debug\deps\librocket-c54f70af5f4dbef5.rlib --extern rocket_contrib=C:\Users\asili\Dropbox\Programming\rust-svelte\backend\target\debug\deps\librocket_contrib-2de34e6aa1ef0f4e.rlib` (exit code: 101)

[superjose]

I ended up deleting the target folder and re-building the project again and it worked without problems.

[wesleywiser]

Thanks for filing the bug report! We just shipped a patch release to work around this issue and are currently triaging related issues related to ensure each underlying problem gets resolved. Since this appears to be a duplicate of #83259, I'm going to close in favor of that issue.