[INFO] fetching crate jmt 0.11.0... [INFO] testing jmt-0.11.0 against try#b83b707f97d809763b7861afa7638871f3339a33 for pr-145838-1 [INFO] extracting crate jmt 0.11.0 into /workspace/builds/worker-7-tc2/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-7-tc2/source/Cargo.toml [INFO] validating manifest of crates.io crate jmt 0.11.0 on toolchain b83b707f97d809763b7861afa7638871f3339a33 [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+b83b707f97d809763b7861afa7638871f3339a33" "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" "+b83b707f97d809763b7861afa7638871f3339a33" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Updating crates.io index [INFO] [stderr] Locking 129 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" "+b83b707f97d809763b7861afa7638871f3339a33" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc2/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" "+b83b707f97d809763b7861afa7638871f3339a33" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] bd0c89b7392f157cee16e7b3b8a01ecfa4eac492e75ec957f9507919fe95844b [INFO] running `Command { std: "docker" "start" "-a" "bd0c89b7392f157cee16e7b3b8a01ecfa4eac492e75ec957f9507919fe95844b", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "bd0c89b7392f157cee16e7b3b8a01ecfa4eac492e75ec957f9507919fe95844b", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "bd0c89b7392f157cee16e7b3b8a01ecfa4eac492e75ec957f9507919fe95844b", kill_on_drop: false }` [INFO] [stdout] bd0c89b7392f157cee16e7b3b8a01ecfa4eac492e75ec957f9507919fe95844b [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc2/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" "+b83b707f97d809763b7861afa7638871f3339a33" "build" "--frozen" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 2fb7ecdd6d09584a2fa5b694b8637a477f6932113a574e0e4a610ff430d8f341 [INFO] running `Command { std: "docker" "start" "-a" "2fb7ecdd6d09584a2fa5b694b8637a477f6932113a574e0e4a610ff430d8f341", kill_on_drop: false }` [INFO] [stderr] Compiling syn v2.0.106 [INFO] [stderr] Compiling blake3 v1.8.2 [INFO] [stderr] Compiling borsh v1.5.7 [INFO] [stderr] Compiling bytes v1.10.1 [INFO] [stderr] Compiling base64 v0.21.7 [INFO] [stderr] Compiling sha2 v0.10.9 [INFO] [stderr] Compiling sha3 v0.10.8 [INFO] [stderr] Compiling blake2 v0.10.6 [INFO] [stderr] Compiling ripemd v0.1.3 [INFO] [stderr] Compiling itertools v0.10.5 [INFO] [stderr] Compiling num-derive v0.3.3 [INFO] [stderr] Compiling mirai-annotations v1.12.0 [INFO] [stderr] Compiling serde_derive v1.0.219 [INFO] [stderr] Compiling prost-derive v0.13.5 [INFO] [stderr] Compiling borsh-derive v1.5.7 [INFO] [stderr] Compiling tracing-attributes v0.1.30 [INFO] [stderr] Compiling thiserror-impl v1.0.69 [INFO] [stderr] Compiling tracing v0.1.41 [INFO] [stderr] Compiling thiserror v1.0.69 [INFO] [stderr] Compiling prost v0.13.5 [INFO] [stderr] Compiling serde v1.0.219 [INFO] [stderr] Compiling informalsystems-pbjson v0.7.0 [INFO] [stderr] Compiling ics23 v0.12.0 [INFO] [stderr] Compiling 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: 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)]` (part of `#[warn(unused)]`) 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] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 25.10s [INFO] running `Command { std: "docker" "inspect" "2fb7ecdd6d09584a2fa5b694b8637a477f6932113a574e0e4a610ff430d8f341", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "2fb7ecdd6d09584a2fa5b694b8637a477f6932113a574e0e4a610ff430d8f341", kill_on_drop: false }` [INFO] [stdout] 2fb7ecdd6d09584a2fa5b694b8637a477f6932113a574e0e4a610ff430d8f341 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc2/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" "+b83b707f97d809763b7861afa7638871f3339a33" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 085de3cb7474af84c4f60b11bb9e1753b46e9d7633cdec89927bcd5b7fa1ff9e [INFO] running `Command { std: "docker" "start" "-a" "085de3cb7474af84c4f60b11bb9e1753b46e9d7633cdec89927bcd5b7fa1ff9e", kill_on_drop: false }` [INFO] [stderr] Compiling proc-macro2 v0.4.30 [INFO] [stderr] Compiling unicode-xid v0.1.0 [INFO] [stderr] Compiling bitflags v2.9.3 [INFO] [stderr] Compiling syn v0.15.44 [INFO] [stderr] Compiling hex v0.4.3 [INFO] [stderr] Compiling wait-timeout v0.2.1 [INFO] [stderr] Compiling rand_xorshift v0.4.0 [INFO] [stderr] Compiling rand v0.9.2 [INFO] [stderr] Compiling rand_chacha v0.9.0 [INFO] [stderr] Compiling serde_json v1.0.143 [INFO] [stderr] Compiling rustix v1.0.8 [INFO] [stderr] Compiling ics23 v0.12.0 [INFO] [stderr] Compiling quote v0.6.13 [INFO] [stderr] Compiling jmt v0.11.0 (/opt/rustwide/workdir) [INFO] [stderr] Compiling tempfile v3.21.0 [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] [stderr] Compiling rusty-fork v0.3.0 [INFO] [stderr] Compiling proptest v1.7.0 [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)]` (part of `#[warn(unused)]`) 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] [stderr] Compiling proptest-derive v0.3.0 [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] 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" "085de3cb7474af84c4f60b11bb9e1753b46e9d7633cdec89927bcd5b7fa1ff9e", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "085de3cb7474af84c4f60b11bb9e1753b46e9d7633cdec89927bcd5b7fa1ff9e", kill_on_drop: false }` [INFO] [stdout] 085de3cb7474af84c4f60b11bb9e1753b46e9d7633cdec89927bcd5b7fa1ff9e