[INFO] fetching crate jmt 0.11.0... [INFO] checking jmt-0.11.0 against master#8c32e313cccf7df531e2d49ffb8227bb92304aee for pr-145608-1 [INFO] extracting crate jmt 0.11.0 into /workspace/builds/worker-0-tc1/source [INFO] started tweaking crates.io crate jmt 0.11.0 [INFO] finished tweaking crates.io crate jmt 0.11.0 [INFO] tweaked toml for crates.io crate jmt 0.11.0 written to /workspace/builds/worker-0-tc1/source/Cargo.toml [INFO] validating manifest of crates.io crate jmt 0.11.0 on toolchain 8c32e313cccf7df531e2d49ffb8227bb92304aee [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+8c32e313cccf7df531e2d49ffb8227bb92304aee" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+8c32e313cccf7df531e2d49ffb8227bb92304aee" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Updating crates.io index [INFO] [stderr] Locking 130 packages to latest compatible versions [INFO] [stderr] Adding hashbrown v0.13.2 (available: v0.16.0) [INFO] [stderr] Adding itertools v0.10.5 (available: v0.14.0) [INFO] [stderr] Adding num-derive v0.3.3 (available: v0.4.2) [INFO] [stderr] Adding proptest-derive v0.3.0 (available: v0.6.0) [INFO] [stderr] Adding rand v0.8.5 (available: v0.9.2) [INFO] [stderr] Adding thiserror v1.0.69 (available: v2.0.16) [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+8c32e313cccf7df531e2d49ffb8227bb92304aee" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] [stderr] Downloading crates ... [INFO] [stderr] Downloaded proptest-derive v0.3.0 [INFO] [stderr] Downloaded mirai-annotations v1.12.0 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:7ad1b28ee6f5f7f699f6cf7015098d6ccdd96d6f2d78dd06228f5b4c9faf309c" "/opt/rustwide/cargo-home/bin/cargo" "+8c32e313cccf7df531e2d49ffb8227bb92304aee" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 21d5d7da1c60f59901608e7b9ad12cebb05d2bccf35216dd2ec8d14eebc37535 [INFO] running `Command { std: "docker" "start" "-a" "21d5d7da1c60f59901608e7b9ad12cebb05d2bccf35216dd2ec8d14eebc37535", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "21d5d7da1c60f59901608e7b9ad12cebb05d2bccf35216dd2ec8d14eebc37535", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "21d5d7da1c60f59901608e7b9ad12cebb05d2bccf35216dd2ec8d14eebc37535", kill_on_drop: false }` [INFO] [stdout] 21d5d7da1c60f59901608e7b9ad12cebb05d2bccf35216dd2ec8d14eebc37535 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-0-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:7ad1b28ee6f5f7f699f6cf7015098d6ccdd96d6f2d78dd06228f5b4c9faf309c" "/opt/rustwide/cargo-home/bin/cargo" "+8c32e313cccf7df531e2d49ffb8227bb92304aee" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 7ba2d64ffc83224cc36b826838cbc748d1228b79040d49ec5103bc0139c0c8f0 [INFO] running `Command { std: "docker" "start" "-a" "7ba2d64ffc83224cc36b826838cbc748d1228b79040d49ec5103bc0139c0c8f0", kill_on_drop: false }` [INFO] [stderr] Compiling syn v2.0.106 [INFO] [stderr] Checking digest v0.10.7 [INFO] [stderr] Compiling itertools v0.14.0 [INFO] [stderr] Compiling blake3 v1.8.2 [INFO] [stderr] Compiling borsh v1.5.7 [INFO] [stderr] Compiling proc-macro-crate v3.3.0 [INFO] [stderr] Checking bytes v1.10.1 [INFO] [stderr] Checking base64 v0.21.7 [INFO] [stderr] Compiling syn v0.15.44 [INFO] [stderr] Checking blake2 v0.10.6 [INFO] [stderr] Checking sha3 v0.10.8 [INFO] [stderr] Checking sha2 v0.10.9 [INFO] [stderr] Checking ripemd v0.1.3 [INFO] [stderr] Compiling syn v1.0.109 [INFO] [stderr] Checking ahash v0.8.12 [INFO] [stderr] Checking wait-timeout v0.2.1 [INFO] [stderr] Checking itertools v0.10.5 [INFO] [stderr] Checking hashbrown v0.13.2 [INFO] [stderr] Checking rusty-fork v0.3.0 [INFO] [stderr] Checking rand_chacha v0.9.0 [INFO] [stderr] Checking rand v0.9.2 [INFO] [stderr] Checking rand_xorshift v0.4.0 [INFO] [stderr] Checking mirai-annotations v1.12.0 [INFO] [stderr] Checking unarray v0.1.4 [INFO] [stderr] Checking proptest v1.7.0 [INFO] [stderr] Compiling num-derive v0.3.3 [INFO] [stderr] Compiling serde_derive v1.0.219 [INFO] [stderr] Compiling prost-derive v0.13.5 [INFO] [stderr] Compiling thiserror-impl v1.0.69 [INFO] [stderr] Compiling tracing-attributes v0.1.30 [INFO] [stderr] Compiling borsh-derive v1.5.7 [INFO] [stderr] Compiling proptest-derive v0.3.0 [INFO] [stderr] Checking tracing v0.1.41 [INFO] [stderr] Checking thiserror v1.0.69 [INFO] [stderr] Checking prost v0.13.5 [INFO] [stderr] Checking serde v1.0.219 [INFO] [stderr] Checking informalsystems-pbjson v0.7.0 [INFO] [stderr] Checking hex v0.4.3 [INFO] [stderr] Checking serde_json v1.0.143 [INFO] [stderr] Checking ics23 v0.12.0 [INFO] [stderr] Checking jmt v0.11.0 (/opt/rustwide/workdir) [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/bytes32ext.rs:43:9 [INFO] [stdout] | [INFO] [stdout] 43 | assume!(index < 32 * 2); // assumed precondition [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/bytes32ext.rs:85:9 [INFO] [stdout] | [INFO] [stdout] 85 | assume!(index < self.pos.end); // assumed precondition [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/bytes32ext.rs:86:9 [INFO] [stdout] | [INFO] [stdout] 86 | assume!(self.hash_bytes.len() == 32); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/bytes32ext.rs:87:9 [INFO] [stdout] | [INFO] [stdout] 87 | assume!(self.pos.end == self.hash_bytes.len() * 8); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:102:9 [INFO] [stdout] | [INFO] [stdout] 102 | checked_precondition!(bytes.len() <= ROOT_NIBBLE_HEIGHT / 2); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `checked_precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `checked_precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `checked_precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:112:9 [INFO] [stdout] | [INFO] [stdout] 112 | checked_precondition!(bytes.len() <= ROOT_NIBBLE_HEIGHT / 2); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `checked_precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `checked_precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `checked_precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:177:9 [INFO] [stdout] | [INFO] [stdout] 177 | assume!(self.num_nibbles <= ROOT_NIBBLE_HEIGHT); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:186:9 [INFO] [stdout] | [INFO] [stdout] 186 | assume!(self.num_nibbles <= ROOT_NIBBLE_HEIGHT); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:283:9 [INFO] [stdout] | [INFO] [stdout] 283 | precondition!(start <= end); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:284:9 [INFO] [stdout] | [INFO] [stdout] 284 | precondition!(start <= ROOT_NIBBLE_HEIGHT); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:285:9 [INFO] [stdout] | [INFO] [stdout] 285 | precondition!(end <= ROOT_NIBBLE_HEIGHT); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:295:9 [INFO] [stdout] | [INFO] [stdout] 295 | assume!(self.start <= self.pos.start); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:296:9 [INFO] [stdout] | [INFO] [stdout] 296 | assume!(self.pos.start <= ROOT_NIBBLE_HEIGHT); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:302:9 [INFO] [stdout] | [INFO] [stdout] 302 | assume!(self.pos.start <= self.pos.end); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:303:9 [INFO] [stdout] | [INFO] [stdout] 303 | assume!(self.pos.end <= ROOT_NIBBLE_HEIGHT); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:309:9 [INFO] [stdout] | [INFO] [stdout] 309 | assume!(self.pos.start <= self.pos.end); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:310:9 [INFO] [stdout] | [INFO] [stdout] 310 | assume!(self.pos.end <= ROOT_NIBBLE_HEIGHT); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:327:9 [INFO] [stdout] | [INFO] [stdout] 327 | assume!(self.start <= self.pos.end); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/restore.rs:83:9 [INFO] [stdout] | [INFO] [stdout] 83 | precondition!(index < 16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/bytes32ext.rs:43:9 [INFO] [stdout] | [INFO] [stdout] 43 | assume!(index < 32 * 2); // assumed precondition [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/bytes32ext.rs:85:9 [INFO] [stdout] | [INFO] [stdout] 85 | assume!(index < self.pos.end); // assumed precondition [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/bytes32ext.rs:86:9 [INFO] [stdout] | [INFO] [stdout] 86 | assume!(self.hash_bytes.len() == 32); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/bytes32ext.rs:87:9 [INFO] [stdout] | [INFO] [stdout] 87 | assume!(self.pos.end == self.hash_bytes.len() * 8); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:102:9 [INFO] [stdout] | [INFO] [stdout] 102 | checked_precondition!(bytes.len() <= ROOT_NIBBLE_HEIGHT / 2); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `checked_precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `checked_precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `checked_precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:112:9 [INFO] [stdout] | [INFO] [stdout] 112 | checked_precondition!(bytes.len() <= ROOT_NIBBLE_HEIGHT / 2); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `checked_precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `checked_precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `checked_precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:177:9 [INFO] [stdout] | [INFO] [stdout] 177 | assume!(self.num_nibbles <= ROOT_NIBBLE_HEIGHT); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:186:9 [INFO] [stdout] | [INFO] [stdout] 186 | assume!(self.num_nibbles <= ROOT_NIBBLE_HEIGHT); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:283:9 [INFO] [stdout] | [INFO] [stdout] 283 | precondition!(start <= end); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:284:9 [INFO] [stdout] | [INFO] [stdout] 284 | precondition!(start <= ROOT_NIBBLE_HEIGHT); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:285:9 [INFO] [stdout] | [INFO] [stdout] 285 | precondition!(end <= ROOT_NIBBLE_HEIGHT); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:295:9 [INFO] [stdout] | [INFO] [stdout] 295 | assume!(self.start <= self.pos.start); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:296:9 [INFO] [stdout] | [INFO] [stdout] 296 | assume!(self.pos.start <= ROOT_NIBBLE_HEIGHT); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:302:9 [INFO] [stdout] | [INFO] [stdout] 302 | assume!(self.pos.start <= self.pos.end); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:303:9 [INFO] [stdout] | [INFO] [stdout] 303 | assume!(self.pos.end <= ROOT_NIBBLE_HEIGHT); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:309:9 [INFO] [stdout] | [INFO] [stdout] 309 | assume!(self.pos.start <= self.pos.end); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:310:9 [INFO] [stdout] | [INFO] [stdout] 310 | assume!(self.pos.end <= ROOT_NIBBLE_HEIGHT); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/types/nibble/nibble_path.rs:327:9 [INFO] [stdout] | [INFO] [stdout] 327 | assume!(self.start <= self.pos.end); // invariant [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `assume` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `assume` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `assume` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `mirai` [INFO] [stdout] --> src/restore.rs:83:9 [INFO] [stdout] | [INFO] [stdout] 83 | precondition!(index < 16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `precondition` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `precondition` may come from an old version of the `mirai_annotations` crate, try updating your dependency with `cargo update -p mirai_annotations` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `precondition` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: associated function `from_bit_iter` is never used [INFO] [stdout] --> src/bytes32ext.rs:19:8 [INFO] [stdout] | [INFO] [stdout] 5 | pub trait Bytes32Ext: Index + Sized { [INFO] [stdout] | ---------- associated function in this trait [INFO] [stdout] ... [INFO] [stdout] 19 | fn from_bit_iter(iter: impl ExactSizeIterator) -> Option; [INFO] [stdout] | ^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(dead_code)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: enum `NodeTag` is never used [INFO] [stdout] --> src/node_type.rs:871:6 [INFO] [stdout] | [INFO] [stdout] 871 | enum NodeTag { [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item [INFO] [stdout] --> src/node_type.rs:869:10 [INFO] [stdout] | [INFO] [stdout] 869 | #[derive(FromPrimitive, ToPrimitive, BorshDeserialize, BorshSerialize)] [INFO] [stdout] | ^------------ [INFO] [stdout] | | [INFO] [stdout] | `FromPrimitive` is not local [INFO] [stdout] | move the `impl` block outside of this constant `_IMPL_NUM_FromPrimitive_FOR_NodeTag` [INFO] [stdout] 870 | #[borsh(use_discriminant = false)] [INFO] [stdout] 871 | enum NodeTag { [INFO] [stdout] | ------- `NodeTag` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromPrimitive` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromPrimitive` may come from an old version of the `num_derive` crate, try updating your dependency with `cargo update -p num_derive` [INFO] [stdout] = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl` [INFO] [stdout] = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint [INFO] [stdout] = note: `#[warn(non_local_definitions)]` on by default [INFO] [stdout] = note: this warning originates in the derive macro `FromPrimitive` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item [INFO] [stdout] --> src/node_type.rs:869:25 [INFO] [stdout] | [INFO] [stdout] 869 | #[derive(FromPrimitive, ToPrimitive, BorshDeserialize, BorshSerialize)] [INFO] [stdout] | ^---------- [INFO] [stdout] | | [INFO] [stdout] | `ToPrimitive` is not local [INFO] [stdout] | move the `impl` block outside of this constant `_IMPL_NUM_ToPrimitive_FOR_NodeTag` [INFO] [stdout] 870 | #[borsh(use_discriminant = false)] [INFO] [stdout] 871 | enum NodeTag { [INFO] [stdout] | ------- `NodeTag` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `ToPrimitive` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `ToPrimitive` may come from an old version of the `num_derive` crate, try updating your dependency with `cargo update -p num_derive` [INFO] [stdout] = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl` [INFO] [stdout] = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint [INFO] [stdout] = note: this warning originates in the derive macro `ToPrimitive` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/types/nibble/nibble_path.rs:176:17 [INFO] [stdout] | [INFO] [stdout] 176 | pub fn bits(&self) -> BitIterator { [INFO] [stdout] | ^^^^^ ----------- the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 176 | pub fn bits(&self) -> BitIterator<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/types/nibble/nibble_path.rs:185:20 [INFO] [stdout] | [INFO] [stdout] 185 | pub fn nibbles(&self) -> NibbleIterator { [INFO] [stdout] | ^^^^^ -------------- the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 185 | pub fn nibbles(&self) -> NibbleIterator<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0599]: the method `fill_bytes` exists for struct `OsRng`, but its trait bounds were not satisfied [INFO] [stdout] --> src/tests/node_type.rs:40:11 [INFO] [stdout] | [INFO] [stdout] 40 | OsRng.fill_bytes(&mut nibbles); [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/rand_core-0.6.4/src/os.rs:48:1 [INFO] [stdout] | [INFO] [stdout] 48 | pub struct OsRng; [INFO] [stdout] | ---------------- doesn't satisfy `OsRng: DerefMut`, `OsRng: Deref` or `_: RngCore` [INFO] [stdout] | [INFO] [stdout] = note: the following trait bounds were not satisfied: [INFO] [stdout] `OsRng: DerefMut` [INFO] [stdout] which is required by `OsRng: _IMPL_ARBITRARY_FOR_RootHash::_proptest::prelude::RngCore` [INFO] [stdout] `OsRng: Deref` [INFO] [stdout] which is required by `OsRng: _IMPL_ARBITRARY_FOR_RootHash::_proptest::prelude::RngCore` [INFO] [stdout] = help: items from traits can only be used if the trait is in scope [INFO] [stdout] help: trait `RngCore` which provides `fill_bytes` is implemented but not in scope; perhaps you want to import it [INFO] [stdout] | [INFO] [stdout] 3 + use rand::RngCore; [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0599]: the method `gen` exists for struct `OsRng`, but its trait bounds were not satisfied [INFO] [stdout] --> src/tests/node_type.rs:139:30 [INFO] [stdout] | [INFO] [stdout] 139 | Child::new(OsRng.gen(), 0 /* version */, NodeType::Leaf), [INFO] [stdout] | ^^^ method cannot be called on `OsRng` due to unsatisfied trait bounds [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/rand_core-0.6.4/src/os.rs:48:1 [INFO] [stdout] | [INFO] [stdout] 48 | pub struct OsRng; [INFO] [stdout] | ---------------- doesn't satisfy `_: RngCore` or `_: Rng` [INFO] [stdout] | [INFO] [stdout] = note: the following trait bounds were not satisfied: [INFO] [stdout] `OsRng: _IMPL_ARBITRARY_FOR_RootHash::_proptest::prelude::RngCore` [INFO] [stdout] which is required by `OsRng: _IMPL_ARBITRARY_FOR_RootHash::_proptest::prelude::Rng` [INFO] [stdout] = help: items from traits can only be used if the trait is in scope [INFO] [stdout] help: trait `Rng` which provides `gen` is implemented but not in scope; perhaps you want to import it [INFO] [stdout] | [INFO] [stdout] 3 + use rand::Rng; [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0599]: the method `gen` exists for struct `OsRng`, but its trait bounds were not satisfied [INFO] [stdout] --> src/tests/node_type.rs:149:37 [INFO] [stdout] | [INFO] [stdout] 149 | let address = KeyHash(OsRng.gen()); [INFO] [stdout] | ^^^ method cannot be called on `OsRng` due to unsatisfied trait bounds [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/rand_core-0.6.4/src/os.rs:48:1 [INFO] [stdout] | [INFO] [stdout] 48 | pub struct OsRng; [INFO] [stdout] | ---------------- doesn't satisfy `_: RngCore` or `_: Rng` [INFO] [stdout] | [INFO] [stdout] = note: the following trait bounds were not satisfied: [INFO] [stdout] `OsRng: _IMPL_ARBITRARY_FOR_RootHash::_proptest::prelude::RngCore` [INFO] [stdout] which is required by `OsRng: _IMPL_ARBITRARY_FOR_RootHash::_proptest::prelude::Rng` [INFO] [stdout] = help: items from traits can only be used if the trait is in scope [INFO] [stdout] help: trait `Rng` which provides `gen` is implemented but not in scope; perhaps you want to import it [INFO] [stdout] | [INFO] [stdout] 3 + use rand::Rng; [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0599]: the method `gen` exists for struct `OsRng`, but its trait bounds were not satisfied [INFO] [stdout] --> src/tests/node_type.rs:369:42 [INFO] [stdout] | [INFO] [stdout] 369 | vec![index0, Nibble::from(OsRng.gen::() % 16)])); [INFO] [stdout] | ^^^ method cannot be called on `OsRng` due to unsatisfied trait bounds [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/rand_core-0.6.4/src/os.rs:48:1 [INFO] [stdout] | [INFO] [stdout] 48 | pub struct OsRng; [INFO] [stdout] | ---------------- doesn't satisfy `_: RngCore` or `_: Rng` [INFO] [stdout] | [INFO] [stdout] = note: the following trait bounds were not satisfied: [INFO] [stdout] `OsRng: _IMPL_ARBITRARY_FOR_RootHash::_proptest::prelude::RngCore` [INFO] [stdout] which is required by `OsRng: _IMPL_ARBITRARY_FOR_RootHash::_proptest::prelude::Rng` [INFO] [stdout] = help: items from traits can only be used if the trait is in scope [INFO] [stdout] help: trait `Rng` which provides `gen` is implemented but not in scope; perhaps you want to import it [INFO] [stdout] | [INFO] [stdout] 3 + use rand::Rng; [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0599]: the method `gen` exists for struct `OsRng`, but its trait bounds were not satisfied [INFO] [stdout] --> src/tests/node_type.rs:380:120 [INFO] [stdout] | [INFO] [stdout] 380 | leaf_keys.push(gen_leaf_keys(0 /* version */, internal_node_key.nibble_path(), vec![index5, Nibble::from(OsRng.gen::() % 16)])); [INFO] [stdout] | ^^^ method cannot be called on `OsRng` due to unsatisfied trait bounds [INFO] [stdout] | [INFO] [stdout] ::: /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/rand_core-0.6.4/src/os.rs:48:1 [INFO] [stdout] | [INFO] [stdout] 48 | pub struct OsRng; [INFO] [stdout] | ---------------- doesn't satisfy `_: RngCore` or `_: Rng` [INFO] [stdout] | [INFO] [stdout] = note: the following trait bounds were not satisfied: [INFO] [stdout] `OsRng: _IMPL_ARBITRARY_FOR_RootHash::_proptest::prelude::RngCore` [INFO] [stdout] which is required by `OsRng: _IMPL_ARBITRARY_FOR_RootHash::_proptest::prelude::Rng` [INFO] [stdout] = help: items from traits can only be used if the trait is in scope [INFO] [stdout] help: trait `Rng` which provides `gen` is implemented but not in scope; perhaps you want to import it [INFO] [stdout] | [INFO] [stdout] 3 + use rand::Rng; [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] For more information about this error, try `rustc --explain E0599`. [INFO] [stdout] [INFO] [stderr] error: could not compile `jmt` (lib test) due to 5 previous errors; 19 warnings emitted [INFO] running `Command { std: "docker" "inspect" "7ba2d64ffc83224cc36b826838cbc748d1228b79040d49ec5103bc0139c0c8f0", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "7ba2d64ffc83224cc36b826838cbc748d1228b79040d49ec5103bc0139c0c8f0", kill_on_drop: false }` [INFO] [stdout] 7ba2d64ffc83224cc36b826838cbc748d1228b79040d49ec5103bc0139c0c8f0