[INFO] cloning repository https://github.com/pizzasuperapp/StacksPizza [INFO] running `Command { std: "git" "-c" "credential.helper=" "-c" "credential.helper=/workspace/cargo-home/bin/git-credential-null" "clone" "--bare" "https://github.com/pizzasuperapp/StacksPizza" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fpizzasuperapp%2FStacksPizza", kill_on_drop: false }` [INFO] [stderr] Cloning into bare repository '/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fpizzasuperapp%2FStacksPizza'... [INFO] running `Command { std: "git" "rev-parse" "HEAD", kill_on_drop: false }` [INFO] [stdout] 6c1c9a5bba10c0d760683bdab0c515283af0e3bf [INFO] building pizzasuperapp/StacksPizza/6c1c9a5bba10c0d760683bdab0c515283af0e3bf against master#44f415c1d617ebc7b931a243b7b321ef8a6ca47c for pr-142134-abi-ast-error [INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fpizzasuperapp%2FStacksPizza" "/workspace/builds/worker-5-tc1/source", kill_on_drop: false }` [INFO] [stderr] Cloning into '/workspace/builds/worker-5-tc1/source'... [INFO] [stderr] done. [INFO] validating manifest of git repo https://github.com/pizzasuperapp/StacksPizza on toolchain 44f415c1d617ebc7b931a243b7b321ef8a6ca47c [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+44f415c1d617ebc7b931a243b7b321ef8a6ca47c" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] removed /workspace/builds/worker-5-tc1/source/.cargo/config [INFO] removed /workspace/builds/worker-5-tc1/source/rust-toolchain [INFO] started tweaking git repo https://github.com/pizzasuperapp/StacksPizza [INFO] finished tweaking git repo https://github.com/pizzasuperapp/StacksPizza [INFO] tweaked toml for git repo https://github.com/pizzasuperapp/StacksPizza written to /workspace/builds/worker-5-tc1/source/Cargo.toml [INFO] crate git repo https://github.com/pizzasuperapp/StacksPizza already has a lockfile, it will not be regenerated [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+44f415c1d617ebc7b931a243b7b321ef8a6ca47c" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] [stderr] Updating crates.io index [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] [stderr] Downloading crates ... [INFO] [stderr] Downloaded slog-json v2.5.0 [INFO] [stderr] Downloaded secp256k1 v0.21.2 [INFO] [stderr] Downloaded sha2-asm v0.6.2 [INFO] [stderr] Downloaded rstest_reuse v0.1.3 [INFO] [stderr] Downloaded libflate v1.1.2 [INFO] [stderr] Downloaded stacker v0.1.14 [INFO] [stderr] Downloaded serde_stacker v0.1.4 [INFO] [stderr] Downloaded rstest v0.11.0 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-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:eea15d5475069c3ef791f10c2c6b5af2ee421ef2da1e680ecce1cba46243983b" "/opt/rustwide/cargo-home/bin/cargo" "+44f415c1d617ebc7b931a243b7b321ef8a6ca47c" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] c309a87423c92b878346f13e1f15518126a606fef60ee2e94920586e8cbf7179 [INFO] running `Command { std: "docker" "start" "-a" "c309a87423c92b878346f13e1f15518126a606fef60ee2e94920586e8cbf7179", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "c309a87423c92b878346f13e1f15518126a606fef60ee2e94920586e8cbf7179", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "c309a87423c92b878346f13e1f15518126a606fef60ee2e94920586e8cbf7179", kill_on_drop: false }` [INFO] [stdout] c309a87423c92b878346f13e1f15518126a606fef60ee2e94920586e8cbf7179 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-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=warn" "-e" "RUSTDOCFLAGS=--cap-lints=warn" "-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:eea15d5475069c3ef791f10c2c6b5af2ee421ef2da1e680ecce1cba46243983b" "/opt/rustwide/cargo-home/bin/cargo" "+44f415c1d617ebc7b931a243b7b321ef8a6ca47c" "build" "--frozen" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] c39a757d8678ff7899cdba89d8d0b3fef274d2715e81b490ceeb940a69c2c9ab [INFO] running `Command { std: "docker" "start" "-a" "c39a757d8678ff7899cdba89d8d0b3fef274d2715e81b490ceeb940a69c2c9ab", kill_on_drop: false }` [INFO] [stderr] Compiling cc v1.0.72 [INFO] [stderr] Compiling libc v0.2.117 [INFO] [stderr] Compiling version_check v0.9.4 [INFO] [stderr] Compiling typenum v1.15.0 [INFO] [stderr] Compiling cfg-if v1.0.0 [INFO] [stderr] Compiling proc-macro2 v1.0.36 [INFO] [stderr] Compiling unicode-xid v0.2.2 [INFO] [stderr] Compiling syn v1.0.86 [INFO] [stderr] Compiling autocfg v1.0.1 [INFO] [stderr] Compiling serde_derive v1.0.136 [INFO] [stderr] Compiling serde v1.0.136 [INFO] [stderr] Compiling getrandom v0.1.16 [INFO] [stderr] Compiling generic-array v0.14.5 [INFO] [stderr] Compiling standback v0.2.17 [INFO] [stderr] Compiling proc-macro-hack v0.5.19 [INFO] [stderr] Compiling byteorder v1.4.3 [INFO] [stderr] Compiling quote v1.0.15 [INFO] [stderr] Compiling num-traits v0.2.14 [INFO] [stderr] Compiling memchr v2.4.1 [INFO] [stderr] Compiling num-integer v0.1.44 [INFO] [stderr] Compiling byte-tools v0.3.1 [INFO] [stderr] Compiling pkg-config v0.3.24 [INFO] [stderr] Compiling psm v0.1.16 [INFO] [stderr] Compiling sha2-asm v0.6.2 [INFO] [stderr] Compiling clear_on_drop v0.2.4 [INFO] [stderr] Compiling dirs-sys-next v0.1.2 [INFO] [stderr] Compiling generic-array v0.12.4 [INFO] [stderr] Compiling rand_core v0.5.1 [INFO] [stderr] Compiling stacker v0.1.14 [INFO] [stderr] Compiling libsqlite3-sys v0.20.1 [INFO] [stderr] Compiling digest v0.8.1 [INFO] [stderr] Compiling secp256k1-sys v0.4.2 [INFO] [stderr] Compiling block-padding v0.1.5 [INFO] [stderr] Compiling ahash v0.4.7 [INFO] [stderr] Compiling slog v2.7.0 [INFO] [stderr] Compiling serde_json v1.0.78 [INFO] [stderr] Compiling ppv-lite86 v0.2.16 [INFO] [stderr] Compiling const_fn v0.4.9 [INFO] [stderr] Compiling hashbrown v0.9.1 [INFO] [stderr] Compiling block-buffer v0.7.3 [INFO] [stderr] Compiling dirs-next v2.0.0 [INFO] [stderr] Compiling block-buffer v0.10.2 [INFO] [stderr] Compiling crypto-common v0.1.3 [INFO] [stderr] Compiling rand_chacha v0.2.2 [INFO] [stderr] Compiling digest v0.10.3 [INFO] [stderr] Compiling time v0.1.44 [INFO] [stderr] Compiling time v0.2.27 [INFO] [stderr] Compiling fake-simd v0.1.2 [INFO] [stderr] Compiling once_cell v1.9.0 [INFO] [stderr] Compiling zeroize v1.5.2 [INFO] [stderr] Compiling itoa v1.0.1 [INFO] [stderr] Compiling ryu v1.0.9 [INFO] [stderr] Compiling percent-encoding v2.1.0 [INFO] [stderr] Compiling tinyvec_macros v0.1.0 [INFO] [stderr] Compiling bitflags v1.3.2 [INFO] [stderr] Compiling subtle v2.4.1 [INFO] [stderr] Compiling opaque-debug v0.2.3 [INFO] [stderr] Compiling tinyvec v1.5.1 [INFO] [stderr] Compiling chrono v0.4.19 [INFO] [stderr] Compiling sha2 v0.8.2 [INFO] [stderr] Compiling thread_local v1.1.4 [INFO] [stderr] Compiling time-macros-impl v0.1.2 [INFO] [stderr] Compiling rand v0.7.3 [INFO] [stderr] Compiling hashlink v0.6.0 [INFO] [stderr] Compiling term v0.7.0 [INFO] [stderr] Compiling time-macros v0.1.1 [INFO] [stderr] Compiling atty v0.2.14 [INFO] [stderr] Compiling memoffset v0.6.5 [INFO] [stderr] Compiling keccak v0.1.0 [INFO] [stderr] Compiling cpufeatures v0.2.1 [INFO] [stderr] Compiling smallvec v1.8.0 [INFO] [stderr] Compiling matches v0.1.9 [INFO] [stderr] Compiling fallible-iterator v0.2.0 [INFO] [stderr] Compiling log v0.4.14 [INFO] [stderr] Compiling fallible-streaming-iterator v0.1.9 [INFO] [stderr] Compiling sha3 v0.10.1 [INFO] [stderr] Compiling unicode-normalization v0.1.19 [INFO] [stderr] Compiling sha2 v0.10.2 [INFO] [stderr] Compiling slog-term v2.8.0 [INFO] [stderr] Compiling ripemd v0.1.1 [INFO] [stderr] Compiling aho-corasick v0.7.18 [INFO] [stderr] Compiling lazy_static v1.4.0 [INFO] [stderr] Compiling unicode-bidi v0.3.7 [INFO] [stderr] Compiling regex-syntax v0.6.25 [INFO] [stderr] Compiling cfg-if v0.1.10 [INFO] [stderr] Compiling net2 v0.2.37 [INFO] [stderr] Compiling idna v0.2.3 [INFO] [stderr] Compiling form_urlencoded v1.0.1 [INFO] [stderr] Compiling iovec v0.1.4 [INFO] [stderr] Compiling integer-sqrt v0.1.5 [INFO] [stderr] Compiling slab v0.4.5 [INFO] [stderr] Compiling blockstack-core v0.0.1 (/opt/rustwide/workdir) [INFO] [stderr] Compiling url v2.2.2 [INFO] [stderr] Compiling mio v0.6.23 [INFO] [stderr] Compiling nix v0.23.1 [INFO] [stderr] Compiling siphasher v0.3.9 [INFO] [stderr] Compiling regex v1.5.4 [INFO] [stderr] Compiling curve25519-dalek v2.0.0 [INFO] [stderr] Compiling serde_stacker v0.1.4 [INFO] [stderr] Compiling secp256k1 v0.21.2 [INFO] [stderr] Compiling rusqlite v0.24.2 [INFO] [stderr] Compiling ed25519-dalek v1.0.0-pre.3 [INFO] [stderr] Compiling stacks-common v0.0.1 (/opt/rustwide/workdir/stacks-common) [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/util/macros.rs:353:20 [INFO] [stdout] | [INFO] [stdout] 353 | #[cfg_attr(feature = "clippy", allow(expl_impl_clone_on_copy))] // we don't define the `struct`, we have to explicitly impl [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/util/hash.rs:98:1 [INFO] [stdout] | [INFO] [stdout] 98 | impl_array_newtype!(Hash160, u8, 20); [INFO] [stdout] | ------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [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 `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/util/macros.rs:353:20 [INFO] [stdout] | [INFO] [stdout] 353 | #[cfg_attr(feature = "clippy", allow(expl_impl_clone_on_copy))] // we don't define the `struct`, we have to explicitly impl [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/util/hash.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | impl_array_newtype!(Keccak256Hash, u8, 32); [INFO] [stdout] | ------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/util/macros.rs:353:20 [INFO] [stdout] | [INFO] [stdout] 353 | #[cfg_attr(feature = "clippy", allow(expl_impl_clone_on_copy))] // we don't define the `struct`, we have to explicitly impl [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/util/hash.rs:123:1 [INFO] [stdout] | [INFO] [stdout] 123 | impl_array_newtype!(Sha256Sum, u8, 32); [INFO] [stdout] | -------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/util/macros.rs:353:20 [INFO] [stdout] | [INFO] [stdout] 353 | #[cfg_attr(feature = "clippy", allow(expl_impl_clone_on_copy))] // we don't define the `struct`, we have to explicitly impl [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/util/hash.rs:141:1 [INFO] [stdout] | [INFO] [stdout] 141 | impl_array_newtype!(Sha512Sum, u8, 64); [INFO] [stdout] | -------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/util/macros.rs:353:20 [INFO] [stdout] | [INFO] [stdout] 353 | #[cfg_attr(feature = "clippy", allow(expl_impl_clone_on_copy))] // we don't define the `struct`, we have to explicitly impl [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/util/hash.rs:153:1 [INFO] [stdout] | [INFO] [stdout] 153 | impl_array_newtype!(Sha512Trunc256Sum, u8, 32); [INFO] [stdout] | ---------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/util/macros.rs:353:20 [INFO] [stdout] | [INFO] [stdout] 353 | #[cfg_attr(feature = "clippy", allow(expl_impl_clone_on_copy))] // we don't define the `struct`, we have to explicitly impl [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/util/hash.rs:165:1 [INFO] [stdout] | [INFO] [stdout] 165 | impl_array_newtype!(DoubleSha256, u8, 32); [INFO] [stdout] | ----------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unnecessary parentheses around index expression [INFO] [stdout] --> stacks-common/src/util/hash.rs:428:61 [INFO] [stdout] | [INFO] [stdout] 428 | let h = MerkleTree::get_node_hash(&nodes[i][(2 * j)], &nodes[i][2 * j + 1]); [INFO] [stdout] | ^ ^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(unused_parens)]` on by default [INFO] [stdout] help: remove these parentheses [INFO] [stdout] | [INFO] [stdout] 428 - let h = MerkleTree::get_node_hash(&nodes[i][(2 * j)], &nodes[i][2 * j + 1]); [INFO] [stdout] 428 + let h = MerkleTree::get_node_hash(&nodes[i][2 * j], &nodes[i][2 * j + 1]); [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/util/macros.rs:353:20 [INFO] [stdout] | [INFO] [stdout] 353 | #[cfg_attr(feature = "clippy", allow(expl_impl_clone_on_copy))] // we don't define the `struct`, we have to explicitly impl [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/util/secp256k1.rs:66:1 [INFO] [stdout] | [INFO] [stdout] 66 | impl_array_newtype!(MessageSignature, u8, 65); [INFO] [stdout] | --------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/util/macros.rs:353:20 [INFO] [stdout] | [INFO] [stdout] 353 | #[cfg_attr(feature = "clippy", allow(expl_impl_clone_on_copy))] // we don't define the `struct`, we have to explicitly impl [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/util/uint.rs:475:1 [INFO] [stdout] | [INFO] [stdout] 475 | construct_uint!(Uint256, 4); [INFO] [stdout] | --------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/util/macros.rs:353:20 [INFO] [stdout] | [INFO] [stdout] 353 | #[cfg_attr(feature = "clippy", allow(expl_impl_clone_on_copy))] // we don't define the `struct`, we have to explicitly impl [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/util/uint.rs:476:1 [INFO] [stdout] | [INFO] [stdout] 476 | construct_uint!(Uint512, 8); [INFO] [stdout] | --------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/util/macros.rs:353:20 [INFO] [stdout] | [INFO] [stdout] 353 | #[cfg_attr(feature = "clippy", allow(expl_impl_clone_on_copy))] // we don't define the `struct`, we have to explicitly impl [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/types/mod.rs:25:1 [INFO] [stdout] | [INFO] [stdout] 25 | impl_array_newtype!(StacksPublicKeyBuffer, u8, 33); [INFO] [stdout] | -------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/util/macros.rs:353:20 [INFO] [stdout] | [INFO] [stdout] 353 | #[cfg_attr(feature = "clippy", allow(expl_impl_clone_on_copy))] // we don't define the `struct`, we have to explicitly impl [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/types/chainstate.rs:32:1 [INFO] [stdout] | [INFO] [stdout] 32 | impl_array_newtype!(TrieHash, u8, 32); [INFO] [stdout] | ------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/util/macros.rs:353:20 [INFO] [stdout] | [INFO] [stdout] 353 | #[cfg_attr(feature = "clippy", allow(expl_impl_clone_on_copy))] // we don't define the `struct`, we have to explicitly impl [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/types/chainstate.rs:47:1 [INFO] [stdout] | [INFO] [stdout] 47 | impl_array_newtype!(BurnchainHeaderHash, u8, 32); [INFO] [stdout] | ------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/util/macros.rs:353:20 [INFO] [stdout] | [INFO] [stdout] 353 | #[cfg_attr(feature = "clippy", allow(expl_impl_clone_on_copy))] // we don't define the `struct`, we have to explicitly impl [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/types/chainstate.rs:52:1 [INFO] [stdout] | [INFO] [stdout] 52 | impl_array_newtype!(BlockHeaderHash, u8, 32); [INFO] [stdout] | -------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/util/macros.rs:353:20 [INFO] [stdout] | [INFO] [stdout] 353 | #[cfg_attr(feature = "clippy", allow(expl_impl_clone_on_copy))] // we don't define the `struct`, we have to explicitly impl [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/types/chainstate.rs:64:1 [INFO] [stdout] | [INFO] [stdout] 64 | impl_array_newtype!(SortitionId, u8, 32); [INFO] [stdout] | ---------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/util/macros.rs:353:20 [INFO] [stdout] | [INFO] [stdout] 353 | #[cfg_attr(feature = "clippy", allow(expl_impl_clone_on_copy))] // we don't define the `struct`, we have to explicitly impl [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/types/chainstate.rs:70:1 [INFO] [stdout] | [INFO] [stdout] 70 | impl_array_newtype!(VRFSeed, u8, 32); [INFO] [stdout] | ------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/util/macros.rs:353:20 [INFO] [stdout] | [INFO] [stdout] 353 | #[cfg_attr(feature = "clippy", allow(expl_impl_clone_on_copy))] // we don't define the `struct`, we have to explicitly impl [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/types/chainstate.rs:225:1 [INFO] [stdout] | [INFO] [stdout] 225 | impl_array_newtype!(StacksBlockId, u8, 32); [INFO] [stdout] | ------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/util/macros.rs:353:20 [INFO] [stdout] | [INFO] [stdout] 353 | #[cfg_attr(feature = "clippy", allow(expl_impl_clone_on_copy))] // we don't define the `struct`, we have to explicitly impl [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/types/chainstate.rs:232:1 [INFO] [stdout] | [INFO] [stdout] 232 | impl_array_newtype!(ConsensusHash, u8, 20); [INFO] [stdout] | ------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/mod.rs:29:13 [INFO] [stdout] | [INFO] [stdout] 29 | #![cfg_attr(feature = "clippy", allow(needless_range_loop))] // suggests making a big mess of array newtypes [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/mod.rs:30:13 [INFO] [stdout] | [INFO] [stdout] 30 | #![cfg_attr(feature = "clippy", allow(extend_from_slice))] // `extend_from_slice` only available since 1.6 [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `serde` [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/blockdata/opcodes.rs:23:7 [INFO] [stdout] | [INFO] [stdout] 23 | #[cfg(feature = "serde")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `serde` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `serde` [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/blockdata/opcodes.rs:637:7 [INFO] [stdout] | [INFO] [stdout] 637 | #[cfg(feature = "serde")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `serde` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `serde` [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/blockdata/opcodes.rs:675:7 [INFO] [stdout] | [INFO] [stdout] 675 | #[cfg(feature = "serde")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `serde` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `serde` [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/blockdata/script.rs:634:7 [INFO] [stdout] | [INFO] [stdout] 634 | #[cfg(feature = "serde")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `serde` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `serde` [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/blockdata/script.rs:677:7 [INFO] [stdout] | [INFO] [stdout] 677 | #[cfg(feature = "serde")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `serde` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `serde` [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/internal_macros.rs:224:15 [INFO] [stdout] | [INFO] [stdout] 224 | #[cfg(feature = "serde")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/deps_common/bitcoin/blockdata/transaction.rs:47:1 [INFO] [stdout] | [INFO] [stdout] 47 | serde_struct_impl!(OutPoint, txid, vout); [INFO] [stdout] | ---------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `serde` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `serde_struct_impl` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `serde` [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/internal_macros.rs:319:15 [INFO] [stdout] | [INFO] [stdout] 319 | #[cfg(feature = "serde")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/deps_common/bitcoin/blockdata/transaction.rs:47:1 [INFO] [stdout] | [INFO] [stdout] 47 | serde_struct_impl!(OutPoint, txid, vout); [INFO] [stdout] | ---------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `serde` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `serde_struct_impl` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `serde` [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/internal_macros.rs:224:15 [INFO] [stdout] | [INFO] [stdout] 224 | #[cfg(feature = "serde")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/deps_common/bitcoin/blockdata/transaction.rs:114:1 [INFO] [stdout] | [INFO] [stdout] 114 | serde_struct_impl!(TxIn, previous_output, script_sig, sequence, witness); [INFO] [stdout] | ------------------------------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `serde` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `serde_struct_impl` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `serde` [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/internal_macros.rs:319:15 [INFO] [stdout] | [INFO] [stdout] 319 | #[cfg(feature = "serde")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/deps_common/bitcoin/blockdata/transaction.rs:114:1 [INFO] [stdout] | [INFO] [stdout] 114 | serde_struct_impl!(TxIn, previous_output, script_sig, sequence, witness); [INFO] [stdout] | ------------------------------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `serde` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `serde_struct_impl` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `serde` [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/internal_macros.rs:224:15 [INFO] [stdout] | [INFO] [stdout] 224 | #[cfg(feature = "serde")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/deps_common/bitcoin/blockdata/transaction.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | serde_struct_impl!(TxOut, value, script_pubkey); [INFO] [stdout] | ----------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `serde` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `serde_struct_impl` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `serde` [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/internal_macros.rs:319:15 [INFO] [stdout] | [INFO] [stdout] 319 | #[cfg(feature = "serde")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/deps_common/bitcoin/blockdata/transaction.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | serde_struct_impl!(TxOut, value, script_pubkey); [INFO] [stdout] | ----------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `serde` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `serde_struct_impl` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `serde` [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/internal_macros.rs:224:15 [INFO] [stdout] | [INFO] [stdout] 224 | #[cfg(feature = "serde")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/deps_common/bitcoin/blockdata/transaction.rs:149:1 [INFO] [stdout] | [INFO] [stdout] 149 | serde_struct_impl!(Transaction, version, lock_time, input, output); [INFO] [stdout] | ------------------------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `serde` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `serde_struct_impl` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `serde` [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/internal_macros.rs:319:15 [INFO] [stdout] | [INFO] [stdout] 319 | #[cfg(feature = "serde")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/deps_common/bitcoin/blockdata/transaction.rs:149:1 [INFO] [stdout] | [INFO] [stdout] 149 | serde_struct_impl!(Transaction, version, lock_time, input, output); [INFO] [stdout] | ------------------------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `serde` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `serde_struct_impl` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `serde` [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/internal_macros.rs:108:15 [INFO] [stdout] | [INFO] [stdout] 108 | #[cfg(feature = "serde")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/deps_common/bitcoin/network/constants.rs:50:1 [INFO] [stdout] | [INFO] [stdout] 50 | / user_enum! { [INFO] [stdout] 51 | | /// The cryptocurrency to act on [INFO] [stdout] 52 | | #[derive(Copy, PartialEq, Eq, PartialOrd, Ord, Clone, Hash)] [INFO] [stdout] 53 | | pub enum Network { [INFO] [stdout] ... | [INFO] [stdout] 61 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `serde` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `user_enum` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `serde` [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/internal_macros.rs:157:15 [INFO] [stdout] | [INFO] [stdout] 157 | #[cfg(feature = "serde")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/deps_common/bitcoin/network/constants.rs:50:1 [INFO] [stdout] | [INFO] [stdout] 50 | / user_enum! { [INFO] [stdout] 51 | | /// The cryptocurrency to act on [INFO] [stdout] 52 | | #[derive(Copy, PartialEq, Eq, PartialOrd, Ord, Clone, Hash)] [INFO] [stdout] 53 | | pub enum Network { [INFO] [stdout] ... | [INFO] [stdout] 61 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `serde` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `user_enum` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `serde` [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/util/hash.rs:18:7 [INFO] [stdout] | [INFO] [stdout] 18 | #[cfg(feature = "serde")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `serde` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `serde` [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/util/hash.rs:255:7 [INFO] [stdout] | [INFO] [stdout] 255 | #[cfg(feature = "serde")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `serde` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `serde` [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/util/hash.rs:298:7 [INFO] [stdout] | [INFO] [stdout] 298 | #[cfg(feature = "serde")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `serde` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/util/macros.rs:353:20 [INFO] [stdout] | [INFO] [stdout] 353 | #[cfg_attr(feature = "clippy", allow(expl_impl_clone_on_copy))] // we don't define the `struct`, we have to explicitly impl [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/deps_common/bitcoin/util/hash.rs:41:1 [INFO] [stdout] | [INFO] [stdout] 41 | impl_array_newtype!(Sha256dHash, u8, 32); [INFO] [stdout] | ---------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/util/macros.rs:353:20 [INFO] [stdout] | [INFO] [stdout] 353 | #[cfg_attr(feature = "clippy", allow(expl_impl_clone_on_copy))] // we don't define the `struct`, we have to explicitly impl [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/deps_common/bitcoin/util/hash.rs:48:1 [INFO] [stdout] | [INFO] [stdout] 48 | impl_array_newtype!(Ripemd160Hash, u8, 20); [INFO] [stdout] | ------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/util/macros.rs:353:20 [INFO] [stdout] | [INFO] [stdout] 353 | #[cfg_attr(feature = "clippy", allow(expl_impl_clone_on_copy))] // we don't define the `struct`, we have to explicitly impl [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/deps_common/bitcoin/util/hash.rs:52:1 [INFO] [stdout] | [INFO] [stdout] 52 | impl_array_newtype!(Hash160, u8, 20); [INFO] [stdout] | ------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> stacks-common/src/util/macros.rs:642:23 [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result { [INFO] [stdout] | ^^^^^ ---------------------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/types/chainstate.rs:67:1 [INFO] [stdout] | [INFO] [stdout] 67 | impl_byte_array_rusqlite_only!(SortitionId); [INFO] [stdout] | ------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] = note: this warning originates in the macro `impl_byte_array_rusqlite_only` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> stacks-common/src/util/macros.rs:642:23 [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result { [INFO] [stdout] | ^^^^^ ---------------------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/types/chainstate.rs:228:1 [INFO] [stdout] | [INFO] [stdout] 228 | impl_byte_array_rusqlite_only!(StacksBlockId); [INFO] [stdout] | --------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `impl_byte_array_rusqlite_only` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> stacks-common/src/util/macros.rs:642:23 [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result { [INFO] [stdout] | ^^^^^ ---------------------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/types/chainstate.rs:302:1 [INFO] [stdout] | [INFO] [stdout] 302 | impl_byte_array_rusqlite_only!(ConsensusHash); [INFO] [stdout] | --------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `impl_byte_array_rusqlite_only` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> stacks-common/src/util/macros.rs:642:23 [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result { [INFO] [stdout] | ^^^^^ ---------------------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/types/chainstate.rs:303:1 [INFO] [stdout] | [INFO] [stdout] 303 | impl_byte_array_rusqlite_only!(Hash160); [INFO] [stdout] | --------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `impl_byte_array_rusqlite_only` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> stacks-common/src/util/macros.rs:642:23 [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result { [INFO] [stdout] | ^^^^^ ---------------------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/types/chainstate.rs:304:1 [INFO] [stdout] | [INFO] [stdout] 304 | impl_byte_array_rusqlite_only!(BlockHeaderHash); [INFO] [stdout] | ----------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `impl_byte_array_rusqlite_only` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> stacks-common/src/util/macros.rs:642:23 [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result { [INFO] [stdout] | ^^^^^ ---------------------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/types/chainstate.rs:305:1 [INFO] [stdout] | [INFO] [stdout] 305 | impl_byte_array_rusqlite_only!(VRFSeed); [INFO] [stdout] | --------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `impl_byte_array_rusqlite_only` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> stacks-common/src/util/macros.rs:642:23 [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result { [INFO] [stdout] | ^^^^^ ---------------------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/types/chainstate.rs:306:1 [INFO] [stdout] | [INFO] [stdout] 306 | impl_byte_array_rusqlite_only!(BurnchainHeaderHash); [INFO] [stdout] | --------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `impl_byte_array_rusqlite_only` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> stacks-common/src/util/macros.rs:642:23 [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result { [INFO] [stdout] | ^^^^^ ---------------------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/types/chainstate.rs:307:1 [INFO] [stdout] | [INFO] [stdout] 307 | impl_byte_array_rusqlite_only!(VRFProof); [INFO] [stdout] | ---------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `impl_byte_array_rusqlite_only` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> stacks-common/src/util/macros.rs:642:23 [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result { [INFO] [stdout] | ^^^^^ ---------------------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/types/chainstate.rs:308:1 [INFO] [stdout] | [INFO] [stdout] 308 | impl_byte_array_rusqlite_only!(TrieHash); [INFO] [stdout] | ---------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `impl_byte_array_rusqlite_only` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> stacks-common/src/util/macros.rs:642:23 [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result { [INFO] [stdout] | ^^^^^ ---------------------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/types/chainstate.rs:309:1 [INFO] [stdout] | [INFO] [stdout] 309 | impl_byte_array_rusqlite_only!(Sha512Trunc256Sum); [INFO] [stdout] | ------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `impl_byte_array_rusqlite_only` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> stacks-common/src/util/macros.rs:642:23 [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result { [INFO] [stdout] | ^^^^^ ---------------------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/types/chainstate.rs:310:1 [INFO] [stdout] | [INFO] [stdout] 310 | impl_byte_array_rusqlite_only!(MessageSignature); [INFO] [stdout] | ------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `impl_byte_array_rusqlite_only` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> stacks-common/src/types/chainstate.rs:356:15 [INFO] [stdout] | [INFO] [stdout] 356 | fn to_sql(&self) -> rusqlite::Result { [INFO] [stdout] | ^^^^^ ----------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 356 | fn to_sql(&self) -> rusqlite::Result> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/blockdata/script.rs:392:17 [INFO] [stdout] | [INFO] [stdout] 392 | pub fn iter(&self, enforce_minimal: bool) -> Instructions { [INFO] [stdout] | ^^^^^ ------------ the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 392 | pub fn iter(&self, enforce_minimal: bool) -> Instructions<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Compiling clarity v0.0.1 (/opt/rustwide/workdir/clarity) [INFO] [stdout] warning: unexpected `cfg` condition name: `rollback_value_check` [INFO] [stdout] --> clarity/src/vm/database/key_value_wrapper.rs:31:7 [INFO] [stdout] | [INFO] [stdout] 31 | #[cfg(rollback_value_check)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(rollback_value_check)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(rollback_value_check)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `rollback_value_check` [INFO] [stdout] --> clarity/src/vm/database/key_value_wrapper.rs:33:11 [INFO] [stdout] | [INFO] [stdout] 33 | #[cfg(not(rollback_value_check))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(rollback_value_check)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(rollback_value_check)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `rollback_value_check` [INFO] [stdout] --> clarity/src/vm/database/key_value_wrapper.rs:36:11 [INFO] [stdout] | [INFO] [stdout] 36 | #[cfg(not(rollback_value_check))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(rollback_value_check)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(rollback_value_check)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `rollback_value_check` [INFO] [stdout] --> clarity/src/vm/database/key_value_wrapper.rs:39:11 [INFO] [stdout] | [INFO] [stdout] 39 | #[cfg(not(rollback_value_check))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(rollback_value_check)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(rollback_value_check)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `rollback_value_check` [INFO] [stdout] --> clarity/src/vm/database/key_value_wrapper.rs:47:11 [INFO] [stdout] | [INFO] [stdout] 47 | #[cfg(not(rollback_value_check))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(rollback_value_check)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(rollback_value_check)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `rollback_value_check` [INFO] [stdout] --> clarity/src/vm/database/key_value_wrapper.rs:71:7 [INFO] [stdout] | [INFO] [stdout] 71 | #[cfg(rollback_value_check)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(rollback_value_check)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(rollback_value_check)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `rollback_value_check` [INFO] [stdout] --> clarity/src/vm/database/key_value_wrapper.rs:75:7 [INFO] [stdout] | [INFO] [stdout] 75 | #[cfg(rollback_value_check)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(rollback_value_check)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(rollback_value_check)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `rollback_value_check` [INFO] [stdout] --> clarity/src/vm/database/key_value_wrapper.rs:84:7 [INFO] [stdout] | [INFO] [stdout] 84 | #[cfg(rollback_value_check)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(rollback_value_check)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(rollback_value_check)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> clarity/src/vm/costs/mod.rs:1017:15 [INFO] [stdout] | [INFO] [stdout] 1017 | fn to_sql(&self) -> rusqlite::Result { [INFO] [stdout] | ^^^^^ ----------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 1017 | fn to_sql(&self) -> rusqlite::Result> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> clarity/src/vm/contexts.rs:1600:29 [INFO] [stdout] | [INFO] [stdout] 1600 | pub fn function_context(&self) -> &LocalContext { [INFO] [stdout] | ^^^^^ ------------- [INFO] [stdout] | | || [INFO] [stdout] | | |the lifetimes get resolved as `'_` [INFO] [stdout] | | the lifetimes get resolved as `'_` [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 1600 | pub fn function_context(&self) -> &LocalContext<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> clarity/src/vm/database/key_value_wrapper.rs:194:24 [INFO] [stdout] | [INFO] [stdout] 194 | pub fn new(store: &'a mut dyn ClarityBackingStore) -> RollbackWrapper { [INFO] [stdout] | ^^ --------------- the lifetime gets resolved as `'a` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 194 | pub fn new(store: &'a mut dyn ClarityBackingStore) -> RollbackWrapper<'a> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> clarity/src/vm/database/key_value_wrapper.rs:205:17 [INFO] [stdout] | [INFO] [stdout] 205 | store: &'a mut dyn ClarityBackingStore, [INFO] [stdout] | ^^ this lifetime flows to the output [INFO] [stdout] 206 | log: RollbackWrapperPersistedLog, [INFO] [stdout] 207 | ) -> RollbackWrapper { [INFO] [stdout] | --------------- the lifetime gets resolved as `'a` [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 207 | ) -> RollbackWrapper<'a> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: call to `.clone()` on a reference in this situation does nothing [INFO] [stdout] --> clarity/src/vm/analysis/errors.rs:210:39 [INFO] [stdout] | [INFO] [stdout] 210 | self.expressions.replace(exprs.clone().to_vec()); [INFO] [stdout] | ^^^^^^^^ help: remove this redundant call [INFO] [stdout] | [INFO] [stdout] = note: the type `[SymbolicExpression]` does not implement `Clone`, so calling `clone` on `&[SymbolicExpression]` copies the reference, which does not do anything and can be removed [INFO] [stdout] = note: `#[warn(noop_method_call)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> src/net/mod.rs:459:1 [INFO] [stdout] | [INFO] [stdout] 459 | impl_array_newtype!(PeerAddress, u8, 16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `monitoring_prom`, `prometheus`, `slog-json`, and `slog_json` [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 `impl_array_newtype` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_array_newtype` may come from an old version of the `stacks_common` crate, try updating your dependency with `cargo update -p stacks_common` [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 `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> src/chainstate/burn/mod.rs:58:1 [INFO] [stdout] | [INFO] [stdout] 58 | impl_array_newtype!(OpsHash, u8, 32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `monitoring_prom`, `prometheus`, `slog-json`, and `slog_json` [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 `impl_array_newtype` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_array_newtype` may come from an old version of the `stacks_common` crate, try updating your dependency with `cargo update -p stacks_common` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> src/chainstate/burn/mod.rs:64:1 [INFO] [stdout] | [INFO] [stdout] 64 | impl_array_newtype!(SortitionHash, u8, 32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `monitoring_prom`, `prometheus`, `slog-json`, and `slog_json` [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 `impl_array_newtype` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_array_newtype` may come from an old version of the `stacks_common` crate, try updating your dependency with `cargo update -p stacks_common` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unnecessary parentheses around match arm expression [INFO] [stdout] --> src/chainstate/burn/db/sortdb.rs:2464:39 [INFO] [stdout] | [INFO] [stdout] 2464 | StacksEpochId::Epoch20 => (version == "1" || version == "2" || version == "3"), [INFO] [stdout] | ^ ^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(unused_parens)]` on by default [INFO] [stdout] help: remove these parentheses [INFO] [stdout] | [INFO] [stdout] 2464 - StacksEpochId::Epoch20 => (version == "1" || version == "2" || version == "3"), [INFO] [stdout] 2464 + StacksEpochId::Epoch20 => version == "1" || version == "2" || version == "3", [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unnecessary parentheses around match arm expression [INFO] [stdout] --> src/chainstate/burn/db/sortdb.rs:2465:41 [INFO] [stdout] | [INFO] [stdout] 2465 | StacksEpochId::Epoch2_05 => (version == "2" || version == "3"), [INFO] [stdout] | ^ ^ [INFO] [stdout] | [INFO] [stdout] help: remove these parentheses [INFO] [stdout] | [INFO] [stdout] 2465 - StacksEpochId::Epoch2_05 => (version == "2" || version == "3"), [INFO] [stdout] 2465 + StacksEpochId::Epoch2_05 => version == "2" || version == "3", [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> src/chainstate/stacks/mod.rs:556:1 [INFO] [stdout] | [INFO] [stdout] 556 | impl_array_newtype!(CoinbasePayload, u8, 32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `monitoring_prom`, `prometheus`, `slog-json`, and `slog_json` [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 `impl_array_newtype` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_array_newtype` may come from an old version of the `stacks_common` crate, try updating your dependency with `cargo update -p stacks_common` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> src/chainstate/stacks/mod.rs:564:1 [INFO] [stdout] | [INFO] [stdout] 564 | impl_array_newtype!(TokenTransferMemo, u8, 34); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `monitoring_prom`, `prometheus`, `slog-json`, and `slog_json` [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 `impl_array_newtype` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_array_newtype` may come from an old version of the `stacks_common` crate, try updating your dependency with `cargo update -p stacks_common` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unnecessary parentheses around match arm expression [INFO] [stdout] --> src/chainstate/stacks/db/mod.rs:195:39 [INFO] [stdout] | [INFO] [stdout] 195 | StacksEpochId::Epoch20 => (self.version == "1" || self.version == "2"), [INFO] [stdout] | ^ ^ [INFO] [stdout] | [INFO] [stdout] help: remove these parentheses [INFO] [stdout] | [INFO] [stdout] 195 - StacksEpochId::Epoch20 => (self.version == "1" || self.version == "2"), [INFO] [stdout] 195 + StacksEpochId::Epoch20 => self.version == "1" || self.version == "2", [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> src/chainstate/stacks/index/mod.rs:229:1 [INFO] [stdout] | [INFO] [stdout] 229 | impl_array_newtype!(MARFValue, u8, 40); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `monitoring_prom`, `prometheus`, `slog-json`, and `slog_json` [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 `impl_array_newtype` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_array_newtype` may come from an old version of the `stacks_common` crate, try updating your dependency with `cargo update -p stacks_common` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> src/chainstate/stacks/index/node.rs:117:1 [INFO] [stdout] | [INFO] [stdout] 117 | impl_array_newtype!(TriePath, u8, 32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `monitoring_prom`, `prometheus`, `slog-json`, and `slog_json` [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 `impl_array_newtype` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_array_newtype` may come from an old version of the `stacks_common` crate, try updating your dependency with `cargo update -p stacks_common` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unnecessary parentheses around match arm expression [INFO] [stdout] --> src/chainstate/stacks/index/storage.rs:1830:21 [INFO] [stdout] | [INFO] [stdout] 1830 | None => (1024), // don't try to guess _byte_ allocation here. [INFO] [stdout] | ^ ^ [INFO] [stdout] | [INFO] [stdout] help: remove these parentheses [INFO] [stdout] | [INFO] [stdout] 1830 - None => (1024), // don't try to guess _byte_ allocation here. [INFO] [stdout] 1830 + None => 1024, // don't try to guess _byte_ allocation here. [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unnecessary parentheses around match arm expression [INFO] [stdout] --> src/chainstate/stacks/index/storage.rs:1872:29 [INFO] [stdout] | [INFO] [stdout] 1872 | None => (1024), // don't try to guess _byte_ allocation here. [INFO] [stdout] | ^ ^ [INFO] [stdout] | [INFO] [stdout] help: remove these parentheses [INFO] [stdout] | [INFO] [stdout] 1872 - None => (1024), // don't try to guess _byte_ allocation here. [INFO] [stdout] 1872 + None => 1024, // don't try to guess _byte_ allocation here. [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> src/burnchains/mod.rs:66:1 [INFO] [stdout] | [INFO] [stdout] 66 | impl_array_newtype!(Txid, u8, 32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `monitoring_prom`, `prometheus`, `slog-json`, and `slog_json` [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 `impl_array_newtype` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_array_newtype` may come from an old version of the `stacks_common` crate, try updating your dependency with `cargo update -p stacks_common` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> src/burnchains/mod.rs:75:1 [INFO] [stdout] | [INFO] [stdout] 75 | impl_array_newtype!(MagicBytes, u8, MAGIC_BYTES_LENGTH); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `monitoring_prom`, `prometheus`, `slog-json`, and `slog_json` [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 `impl_array_newtype` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_array_newtype` may come from an old version of the `stacks_common` crate, try updating your dependency with `cargo update -p stacks_common` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `httparse_min_2018` [INFO] [stdout] --> src/deps/httparse/mod.rs:25:13 [INFO] [stdout] | [INFO] [stdout] 25 | #![cfg_attr(httparse_min_2018, allow(rust_2018_idioms))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(httparse_min_2018)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(httparse_min_2018)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin` [INFO] [stdout] --> src/clarity_cli.rs:104:12 [INFO] [stdout] | [INFO] [stdout] 104 | #[cfg_attr(tarpaulin, skip)] [INFO] [stdout] | ^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tarpaulin)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tarpaulin)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin` [INFO] [stdout] --> src/clarity_cli.rs:127:12 [INFO] [stdout] | [INFO] [stdout] 127 | #[cfg_attr(tarpaulin, skip)] [INFO] [stdout] | ^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tarpaulin)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tarpaulin)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin` [INFO] [stdout] --> src/clarity_cli.rs:135:12 [INFO] [stdout] | [INFO] [stdout] 135 | #[cfg_attr(tarpaulin, skip)] [INFO] [stdout] | ^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tarpaulin)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tarpaulin)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: irrefutable `if let` pattern [INFO] [stdout] --> src/net/http.rs:2573:28 [INFO] [stdout] | [INFO] [stdout] 2573 | if let Ok(pages_indexes_value) = value.parse::() { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this pattern will always match, so the `if let` is useless [INFO] [stdout] = help: consider replacing the `if let` with a `let` [INFO] [stdout] = note: `#[warn(irrefutable_let_patterns)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: variable does not need to be mutable [INFO] [stdout] --> src/chainstate/stacks/index/storage.rs:878:21 [INFO] [stdout] | [INFO] [stdout] 878 | let mut ptrs = next_node.ptrs_mut(); [INFO] [stdout] | ----^^^^ [INFO] [stdout] | | [INFO] [stdout] | help: remove this `mut` [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(unused_mut)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: call to `.clone()` on a reference in this situation does nothing [INFO] [stdout] --> src/net/atlas/download.rs:690:39 [INFO] [stdout] | [INFO] [stdout] 690 | ... domain.clone(), [INFO] [stdout] | ^^^^^^^^ help: remove this redundant call [INFO] [stdout] | [INFO] [stdout] = note: the type `str` does not implement `Clone`, so calling `clone` on `&str` copies the reference, which does not do anything and can be removed [INFO] [stdout] = note: `#[warn(noop_method_call)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: using `.clone()` on a double reference, which returns `&stacks_common::types::chainstate::BurnchainHeaderHash` instead of cloning the inner type [INFO] [stdout] --> src/net/chat.rs:647:33 [INFO] [stdout] | [INFO] [stdout] 647 | Some(ref bhh) => bhh.clone(), [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(suspicious_double_ref_op)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: call to `.clone()` on a reference in this situation does nothing [INFO] [stdout] --> src/net/download.rs:364:31 [INFO] [stdout] | [INFO] [stdout] 364 | domain.clone(), [INFO] [stdout] | ^^^^^^^^ help: remove this redundant call [INFO] [stdout] | [INFO] [stdout] = note: the type `str` does not implement `Clone`, so calling `clone` on `&str` copies the reference, which does not do anything and can be removed [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: call to `.clone()` on a reference in this situation does nothing [INFO] [stdout] --> src/net/p2p.rs:3255:27 [INFO] [stdout] | [INFO] [stdout] 3255 | domain.clone(), [INFO] [stdout] | ^^^^^^^^ help: remove this redundant call [INFO] [stdout] | [INFO] [stdout] = note: the type `str` does not implement `Clone`, so calling `clone` on `&str` copies the reference, which does not do anything and can be removed [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/util_lib/db.rs:313:23 [INFO] [stdout] | [INFO] [stdout] 313 | fn to_sql(&self) -> rusqlite::Result { [INFO] [stdout] | ^^^^^ ---------------------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/chainstate/burn/db/mod.rs:45:1 [INFO] [stdout] | [INFO] [stdout] 45 | impl_byte_array_from_column!(Txid); [INFO] [stdout] | ---------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] = note: this warning originates in the macro `impl_byte_array_from_column` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 313 | fn to_sql(&self) -> rusqlite::Result> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/util_lib/db.rs:313:23 [INFO] [stdout] | [INFO] [stdout] 313 | fn to_sql(&self) -> rusqlite::Result { [INFO] [stdout] | ^^^^^ ---------------------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/chainstate/burn/db/mod.rs:50:1 [INFO] [stdout] | [INFO] [stdout] 50 | impl_byte_array_from_column!(OpsHash); [INFO] [stdout] | ------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `impl_byte_array_from_column` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 313 | fn to_sql(&self) -> rusqlite::Result> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/util_lib/db.rs:313:23 [INFO] [stdout] | [INFO] [stdout] 313 | fn to_sql(&self) -> rusqlite::Result { [INFO] [stdout] | ^^^^^ ---------------------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/chainstate/burn/db/mod.rs:52:1 [INFO] [stdout] | [INFO] [stdout] 52 | impl_byte_array_from_column!(SortitionHash); [INFO] [stdout] | ------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `impl_byte_array_from_column` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 313 | fn to_sql(&self) -> rusqlite::Result> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: using `.clone()` on a double reference, which returns `&stacks_common::types::chainstate::StacksBlockId` instead of cloning the inner type [INFO] [stdout] --> src/clarity_vm/database/marf.rs:90:46 [INFO] [stdout] | [INFO] [stdout] 90 | Some(ref miner_tip) => *miner_tip.clone(), [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: using `.clone()` on a double reference, which returns `&stacks_common::types::chainstate::StacksBlockId` instead of cloning the inner type [INFO] [stdout] --> src/clarity_vm/database/marf.rs:104:46 [INFO] [stdout] | [INFO] [stdout] 104 | Some(ref miner_tip) => *miner_tip.clone(), [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 2m 16s [INFO] running `Command { std: "docker" "inspect" "c39a757d8678ff7899cdba89d8d0b3fef274d2715e81b490ceeb940a69c2c9ab", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "c39a757d8678ff7899cdba89d8d0b3fef274d2715e81b490ceeb940a69c2c9ab", kill_on_drop: false }` [INFO] [stdout] c39a757d8678ff7899cdba89d8d0b3fef274d2715e81b490ceeb940a69c2c9ab [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-5-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=warn" "-e" "RUSTDOCFLAGS=--cap-lints=warn" "-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:eea15d5475069c3ef791f10c2c6b5af2ee421ef2da1e680ecce1cba46243983b" "/opt/rustwide/cargo-home/bin/cargo" "+44f415c1d617ebc7b931a243b7b321ef8a6ca47c" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] d31e186ad52aa40b0f23678b5254a8371c2936782494ba957923ef5c5975bf04 [INFO] running `Command { std: "docker" "start" "-a" "d31e186ad52aa40b0f23678b5254a8371c2936782494ba957923ef5c5975bf04", kill_on_drop: false }` [INFO] [stderr] Compiling syn v1.0.86 [INFO] [stderr] Compiling num-traits v0.2.14 [INFO] [stderr] Compiling crossbeam-utils v0.8.7 [INFO] [stderr] Compiling semver v1.0.5 [INFO] [stderr] Compiling crc32fast v1.3.1 [INFO] [stderr] Compiling crossbeam-epoch v0.9.7 [INFO] [stderr] Compiling proc-macro-error-attr v1.0.4 [INFO] [stderr] Compiling rle-decode-fast v1.0.3 [INFO] [stderr] Compiling scopeguard v1.1.0 [INFO] [stderr] Compiling rayon-core v1.9.1 [INFO] [stderr] Compiling libflate_lz77 v1.1.0 [INFO] [stderr] Compiling proc-macro-error v1.0.4 [INFO] [stderr] Compiling adler32 v1.2.0 [INFO] [stderr] Compiling either v1.6.1 [INFO] [stderr] Compiling libflate v1.1.2 [INFO] [stderr] Compiling rustc_version v0.4.0 [INFO] [stderr] Compiling sha2 v0.10.2 [INFO] [stderr] Compiling rayon v1.5.1 [INFO] [stderr] Compiling cast v0.2.7 [INFO] [stderr] Compiling crossbeam-channel v0.5.2 [INFO] [stderr] Compiling num_cpus v1.13.1 [INFO] [stderr] Compiling crossbeam-deque v0.8.1 [INFO] [stderr] Compiling regex-automata v0.1.10 [INFO] [stderr] Compiling plotters-backend v0.3.2 [INFO] [stderr] Compiling unicode-width v0.1.9 [INFO] [stderr] Compiling textwrap v0.11.0 [INFO] [stderr] Compiling plotters-svg v0.3.1 [INFO] [stderr] Compiling itertools v0.10.3 [INFO] [stderr] Compiling num-integer v0.1.44 [INFO] [stderr] Compiling integer-sqrt v0.1.5 [INFO] [stderr] Compiling csv-core v0.1.10 [INFO] [stderr] Compiling half v1.8.2 [INFO] [stderr] Compiling itoa v0.4.8 [INFO] [stderr] Compiling same-file v1.0.6 [INFO] [stderr] Compiling stx-genesis v0.1.0 (/opt/rustwide/workdir/stx-genesis) [INFO] [stderr] Compiling chrono v0.4.19 [INFO] [stderr] Compiling walkdir v2.3.2 [INFO] [stderr] Compiling plotters v0.3.1 [INFO] [stderr] Compiling clap v2.34.0 [INFO] [stderr] Compiling oorandom v11.1.3 [INFO] [stderr] Compiling slog-term v2.8.0 [INFO] [stderr] Compiling criterion-plot v0.4.4 [INFO] [stderr] Compiling serde_derive v1.0.136 [INFO] [stderr] Compiling time-macros-impl v0.1.2 [INFO] [stderr] Compiling extend v0.1.2 [INFO] [stderr] Compiling time-macros v0.1.1 [INFO] [stderr] Compiling time v0.2.27 [INFO] [stderr] Compiling serde v1.0.136 [INFO] [stderr] Compiling serde_json v1.0.78 [INFO] [stderr] Compiling curve25519-dalek v2.0.0 [INFO] [stderr] Compiling serde_stacker v0.1.4 [INFO] [stderr] Compiling secp256k1 v0.21.2 [INFO] [stderr] Compiling bstr v0.2.17 [INFO] [stderr] Compiling serde_cbor v0.11.2 [INFO] [stderr] Compiling ed25519-dalek v1.0.0-pre.3 [INFO] [stderr] Compiling csv v1.1.6 [INFO] [stderr] Compiling rusqlite v0.24.2 [INFO] [stderr] Compiling tinytemplate v1.2.1 [INFO] [stderr] Compiling assert-json-diff v1.1.0 [INFO] [stderr] Compiling criterion v0.3.5 [INFO] [stderr] Compiling stacks-common v0.0.1 (/opt/rustwide/workdir/stacks-common) [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/util/macros.rs:353:20 [INFO] [stdout] | [INFO] [stdout] 353 | #[cfg_attr(feature = "clippy", allow(expl_impl_clone_on_copy))] // we don't define the `struct`, we have to explicitly impl [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/util/hash.rs:98:1 [INFO] [stdout] | [INFO] [stdout] 98 | impl_array_newtype!(Hash160, u8, 20); [INFO] [stdout] | ------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [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 `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/util/macros.rs:353:20 [INFO] [stdout] | [INFO] [stdout] 353 | #[cfg_attr(feature = "clippy", allow(expl_impl_clone_on_copy))] // we don't define the `struct`, we have to explicitly impl [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/util/hash.rs:111:1 [INFO] [stdout] | [INFO] [stdout] 111 | impl_array_newtype!(Keccak256Hash, u8, 32); [INFO] [stdout] | ------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/util/macros.rs:353:20 [INFO] [stdout] | [INFO] [stdout] 353 | #[cfg_attr(feature = "clippy", allow(expl_impl_clone_on_copy))] // we don't define the `struct`, we have to explicitly impl [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/util/hash.rs:123:1 [INFO] [stdout] | [INFO] [stdout] 123 | impl_array_newtype!(Sha256Sum, u8, 32); [INFO] [stdout] | -------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/util/macros.rs:353:20 [INFO] [stdout] | [INFO] [stdout] 353 | #[cfg_attr(feature = "clippy", allow(expl_impl_clone_on_copy))] // we don't define the `struct`, we have to explicitly impl [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/util/hash.rs:141:1 [INFO] [stdout] | [INFO] [stdout] 141 | impl_array_newtype!(Sha512Sum, u8, 64); [INFO] [stdout] | -------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/util/macros.rs:353:20 [INFO] [stdout] | [INFO] [stdout] 353 | #[cfg_attr(feature = "clippy", allow(expl_impl_clone_on_copy))] // we don't define the `struct`, we have to explicitly impl [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/util/hash.rs:153:1 [INFO] [stdout] | [INFO] [stdout] 153 | impl_array_newtype!(Sha512Trunc256Sum, u8, 32); [INFO] [stdout] | ---------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/util/macros.rs:353:20 [INFO] [stdout] | [INFO] [stdout] 353 | #[cfg_attr(feature = "clippy", allow(expl_impl_clone_on_copy))] // we don't define the `struct`, we have to explicitly impl [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/util/hash.rs:165:1 [INFO] [stdout] | [INFO] [stdout] 165 | impl_array_newtype!(DoubleSha256, u8, 32); [INFO] [stdout] | ----------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unnecessary parentheses around index expression [INFO] [stdout] --> stacks-common/src/util/hash.rs:428:61 [INFO] [stdout] | [INFO] [stdout] 428 | let h = MerkleTree::get_node_hash(&nodes[i][(2 * j)], &nodes[i][2 * j + 1]); [INFO] [stdout] | ^ ^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(unused_parens)]` on by default [INFO] [stdout] help: remove these parentheses [INFO] [stdout] | [INFO] [stdout] 428 - let h = MerkleTree::get_node_hash(&nodes[i][(2 * j)], &nodes[i][2 * j + 1]); [INFO] [stdout] 428 + let h = MerkleTree::get_node_hash(&nodes[i][2 * j], &nodes[i][2 * j + 1]); [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/util/macros.rs:353:20 [INFO] [stdout] | [INFO] [stdout] 353 | #[cfg_attr(feature = "clippy", allow(expl_impl_clone_on_copy))] // we don't define the `struct`, we have to explicitly impl [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/util/secp256k1.rs:66:1 [INFO] [stdout] | [INFO] [stdout] 66 | impl_array_newtype!(MessageSignature, u8, 65); [INFO] [stdout] | --------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/util/macros.rs:353:20 [INFO] [stdout] | [INFO] [stdout] 353 | #[cfg_attr(feature = "clippy", allow(expl_impl_clone_on_copy))] // we don't define the `struct`, we have to explicitly impl [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/util/uint.rs:475:1 [INFO] [stdout] | [INFO] [stdout] 475 | construct_uint!(Uint256, 4); [INFO] [stdout] | --------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/util/macros.rs:353:20 [INFO] [stdout] | [INFO] [stdout] 353 | #[cfg_attr(feature = "clippy", allow(expl_impl_clone_on_copy))] // we don't define the `struct`, we have to explicitly impl [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/util/uint.rs:476:1 [INFO] [stdout] | [INFO] [stdout] 476 | construct_uint!(Uint512, 8); [INFO] [stdout] | --------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` which comes from the expansion of the macro `construct_uint` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/util/macros.rs:353:20 [INFO] [stdout] | [INFO] [stdout] 353 | #[cfg_attr(feature = "clippy", allow(expl_impl_clone_on_copy))] // we don't define the `struct`, we have to explicitly impl [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/types/mod.rs:25:1 [INFO] [stdout] | [INFO] [stdout] 25 | impl_array_newtype!(StacksPublicKeyBuffer, u8, 33); [INFO] [stdout] | -------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/util/macros.rs:353:20 [INFO] [stdout] | [INFO] [stdout] 353 | #[cfg_attr(feature = "clippy", allow(expl_impl_clone_on_copy))] // we don't define the `struct`, we have to explicitly impl [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/types/chainstate.rs:32:1 [INFO] [stdout] | [INFO] [stdout] 32 | impl_array_newtype!(TrieHash, u8, 32); [INFO] [stdout] | ------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/util/macros.rs:353:20 [INFO] [stdout] | [INFO] [stdout] 353 | #[cfg_attr(feature = "clippy", allow(expl_impl_clone_on_copy))] // we don't define the `struct`, we have to explicitly impl [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/types/chainstate.rs:47:1 [INFO] [stdout] | [INFO] [stdout] 47 | impl_array_newtype!(BurnchainHeaderHash, u8, 32); [INFO] [stdout] | ------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/util/macros.rs:353:20 [INFO] [stdout] | [INFO] [stdout] 353 | #[cfg_attr(feature = "clippy", allow(expl_impl_clone_on_copy))] // we don't define the `struct`, we have to explicitly impl [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/types/chainstate.rs:52:1 [INFO] [stdout] | [INFO] [stdout] 52 | impl_array_newtype!(BlockHeaderHash, u8, 32); [INFO] [stdout] | -------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/util/macros.rs:353:20 [INFO] [stdout] | [INFO] [stdout] 353 | #[cfg_attr(feature = "clippy", allow(expl_impl_clone_on_copy))] // we don't define the `struct`, we have to explicitly impl [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/types/chainstate.rs:64:1 [INFO] [stdout] | [INFO] [stdout] 64 | impl_array_newtype!(SortitionId, u8, 32); [INFO] [stdout] | ---------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/util/macros.rs:353:20 [INFO] [stdout] | [INFO] [stdout] 353 | #[cfg_attr(feature = "clippy", allow(expl_impl_clone_on_copy))] // we don't define the `struct`, we have to explicitly impl [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/types/chainstate.rs:70:1 [INFO] [stdout] | [INFO] [stdout] 70 | impl_array_newtype!(VRFSeed, u8, 32); [INFO] [stdout] | ------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/util/macros.rs:353:20 [INFO] [stdout] | [INFO] [stdout] 353 | #[cfg_attr(feature = "clippy", allow(expl_impl_clone_on_copy))] // we don't define the `struct`, we have to explicitly impl [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/types/chainstate.rs:225:1 [INFO] [stdout] | [INFO] [stdout] 225 | impl_array_newtype!(StacksBlockId, u8, 32); [INFO] [stdout] | ------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/util/macros.rs:353:20 [INFO] [stdout] | [INFO] [stdout] 353 | #[cfg_attr(feature = "clippy", allow(expl_impl_clone_on_copy))] // we don't define the `struct`, we have to explicitly impl [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/types/chainstate.rs:232:1 [INFO] [stdout] | [INFO] [stdout] 232 | impl_array_newtype!(ConsensusHash, u8, 20); [INFO] [stdout] | ------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/mod.rs:29:13 [INFO] [stdout] | [INFO] [stdout] 29 | #![cfg_attr(feature = "clippy", allow(needless_range_loop))] // suggests making a big mess of array newtypes [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/mod.rs:30:13 [INFO] [stdout] | [INFO] [stdout] 30 | #![cfg_attr(feature = "clippy", allow(extend_from_slice))] // `extend_from_slice` only available since 1.6 [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `serde` [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/blockdata/opcodes.rs:23:7 [INFO] [stdout] | [INFO] [stdout] 23 | #[cfg(feature = "serde")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `serde` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `serde` [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/blockdata/opcodes.rs:637:7 [INFO] [stdout] | [INFO] [stdout] 637 | #[cfg(feature = "serde")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `serde` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `serde` [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/blockdata/opcodes.rs:675:7 [INFO] [stdout] | [INFO] [stdout] 675 | #[cfg(feature = "serde")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `serde` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `serde` [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/blockdata/script.rs:634:7 [INFO] [stdout] | [INFO] [stdout] 634 | #[cfg(feature = "serde")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `serde` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `serde` [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/blockdata/script.rs:677:7 [INFO] [stdout] | [INFO] [stdout] 677 | #[cfg(feature = "serde")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `serde` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `serde` [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/internal_macros.rs:224:15 [INFO] [stdout] | [INFO] [stdout] 224 | #[cfg(feature = "serde")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/deps_common/bitcoin/blockdata/transaction.rs:47:1 [INFO] [stdout] | [INFO] [stdout] 47 | serde_struct_impl!(OutPoint, txid, vout); [INFO] [stdout] | ---------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `serde` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `serde_struct_impl` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `serde` [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/internal_macros.rs:319:15 [INFO] [stdout] | [INFO] [stdout] 319 | #[cfg(feature = "serde")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/deps_common/bitcoin/blockdata/transaction.rs:47:1 [INFO] [stdout] | [INFO] [stdout] 47 | serde_struct_impl!(OutPoint, txid, vout); [INFO] [stdout] | ---------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `serde` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `serde_struct_impl` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `serde` [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/internal_macros.rs:224:15 [INFO] [stdout] | [INFO] [stdout] 224 | #[cfg(feature = "serde")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/deps_common/bitcoin/blockdata/transaction.rs:114:1 [INFO] [stdout] | [INFO] [stdout] 114 | serde_struct_impl!(TxIn, previous_output, script_sig, sequence, witness); [INFO] [stdout] | ------------------------------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `serde` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `serde_struct_impl` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `serde` [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/internal_macros.rs:319:15 [INFO] [stdout] | [INFO] [stdout] 319 | #[cfg(feature = "serde")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/deps_common/bitcoin/blockdata/transaction.rs:114:1 [INFO] [stdout] | [INFO] [stdout] 114 | serde_struct_impl!(TxIn, previous_output, script_sig, sequence, witness); [INFO] [stdout] | ------------------------------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `serde` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `serde_struct_impl` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `serde` [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/internal_macros.rs:224:15 [INFO] [stdout] | [INFO] [stdout] 224 | #[cfg(feature = "serde")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/deps_common/bitcoin/blockdata/transaction.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | serde_struct_impl!(TxOut, value, script_pubkey); [INFO] [stdout] | ----------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `serde` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `serde_struct_impl` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `serde` [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/internal_macros.rs:319:15 [INFO] [stdout] | [INFO] [stdout] 319 | #[cfg(feature = "serde")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/deps_common/bitcoin/blockdata/transaction.rs:124:1 [INFO] [stdout] | [INFO] [stdout] 124 | serde_struct_impl!(TxOut, value, script_pubkey); [INFO] [stdout] | ----------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `serde` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `serde_struct_impl` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `serde` [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/internal_macros.rs:224:15 [INFO] [stdout] | [INFO] [stdout] 224 | #[cfg(feature = "serde")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/deps_common/bitcoin/blockdata/transaction.rs:149:1 [INFO] [stdout] | [INFO] [stdout] 149 | serde_struct_impl!(Transaction, version, lock_time, input, output); [INFO] [stdout] | ------------------------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `serde` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `serde_struct_impl` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `serde` [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/internal_macros.rs:319:15 [INFO] [stdout] | [INFO] [stdout] 319 | #[cfg(feature = "serde")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/deps_common/bitcoin/blockdata/transaction.rs:149:1 [INFO] [stdout] | [INFO] [stdout] 149 | serde_struct_impl!(Transaction, version, lock_time, input, output); [INFO] [stdout] | ------------------------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `serde` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `serde_struct_impl` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `serde` [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/internal_macros.rs:108:15 [INFO] [stdout] | [INFO] [stdout] 108 | #[cfg(feature = "serde")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/deps_common/bitcoin/network/constants.rs:50:1 [INFO] [stdout] | [INFO] [stdout] 50 | / user_enum! { [INFO] [stdout] 51 | | /// The cryptocurrency to act on [INFO] [stdout] 52 | | #[derive(Copy, PartialEq, Eq, PartialOrd, Ord, Clone, Hash)] [INFO] [stdout] 53 | | pub enum Network { [INFO] [stdout] ... | [INFO] [stdout] 61 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `serde` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `user_enum` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `serde` [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/internal_macros.rs:157:15 [INFO] [stdout] | [INFO] [stdout] 157 | #[cfg(feature = "serde")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/deps_common/bitcoin/network/constants.rs:50:1 [INFO] [stdout] | [INFO] [stdout] 50 | / user_enum! { [INFO] [stdout] 51 | | /// The cryptocurrency to act on [INFO] [stdout] 52 | | #[derive(Copy, PartialEq, Eq, PartialOrd, Ord, Clone, Hash)] [INFO] [stdout] 53 | | pub enum Network { [INFO] [stdout] ... | [INFO] [stdout] 61 | | } [INFO] [stdout] | |_- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `serde` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `user_enum` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `serde` [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/util/hash.rs:18:7 [INFO] [stdout] | [INFO] [stdout] 18 | #[cfg(feature = "serde")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `serde` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `serde` [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/util/hash.rs:255:7 [INFO] [stdout] | [INFO] [stdout] 255 | #[cfg(feature = "serde")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `serde` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `serde` [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/util/hash.rs:298:7 [INFO] [stdout] | [INFO] [stdout] 298 | #[cfg(feature = "serde")] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `serde` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/util/macros.rs:353:20 [INFO] [stdout] | [INFO] [stdout] 353 | #[cfg_attr(feature = "clippy", allow(expl_impl_clone_on_copy))] // we don't define the `struct`, we have to explicitly impl [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/deps_common/bitcoin/util/hash.rs:41:1 [INFO] [stdout] | [INFO] [stdout] 41 | impl_array_newtype!(Sha256dHash, u8, 32); [INFO] [stdout] | ---------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/util/macros.rs:353:20 [INFO] [stdout] | [INFO] [stdout] 353 | #[cfg_attr(feature = "clippy", allow(expl_impl_clone_on_copy))] // we don't define the `struct`, we have to explicitly impl [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/deps_common/bitcoin/util/hash.rs:48:1 [INFO] [stdout] | [INFO] [stdout] 48 | impl_array_newtype!(Ripemd160Hash, u8, 20); [INFO] [stdout] | ------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> stacks-common/src/util/macros.rs:353:20 [INFO] [stdout] | [INFO] [stdout] 353 | #[cfg_attr(feature = "clippy", allow(expl_impl_clone_on_copy))] // we don't define the `struct`, we have to explicitly impl [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/deps_common/bitcoin/util/hash.rs:52:1 [INFO] [stdout] | [INFO] [stdout] 52 | impl_array_newtype!(Hash160, u8, 20); [INFO] [stdout] | ------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `slog-json`, `slog_json`, and `testing` [INFO] [stdout] = help: consider adding `clippy` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> stacks-common/src/util/macros.rs:642:23 [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result { [INFO] [stdout] | ^^^^^ ---------------------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/types/chainstate.rs:67:1 [INFO] [stdout] | [INFO] [stdout] 67 | impl_byte_array_rusqlite_only!(SortitionId); [INFO] [stdout] | ------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] = note: this warning originates in the macro `impl_byte_array_rusqlite_only` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> stacks-common/src/util/macros.rs:642:23 [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result { [INFO] [stdout] | ^^^^^ ---------------------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/types/chainstate.rs:228:1 [INFO] [stdout] | [INFO] [stdout] 228 | impl_byte_array_rusqlite_only!(StacksBlockId); [INFO] [stdout] | --------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `impl_byte_array_rusqlite_only` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> stacks-common/src/util/macros.rs:642:23 [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result { [INFO] [stdout] | ^^^^^ ---------------------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/types/chainstate.rs:302:1 [INFO] [stdout] | [INFO] [stdout] 302 | impl_byte_array_rusqlite_only!(ConsensusHash); [INFO] [stdout] | --------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `impl_byte_array_rusqlite_only` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> stacks-common/src/util/macros.rs:642:23 [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result { [INFO] [stdout] | ^^^^^ ---------------------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/types/chainstate.rs:303:1 [INFO] [stdout] | [INFO] [stdout] 303 | impl_byte_array_rusqlite_only!(Hash160); [INFO] [stdout] | --------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `impl_byte_array_rusqlite_only` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> stacks-common/src/util/macros.rs:642:23 [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result { [INFO] [stdout] | ^^^^^ ---------------------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/types/chainstate.rs:304:1 [INFO] [stdout] | [INFO] [stdout] 304 | impl_byte_array_rusqlite_only!(BlockHeaderHash); [INFO] [stdout] | ----------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `impl_byte_array_rusqlite_only` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> stacks-common/src/util/macros.rs:642:23 [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result { [INFO] [stdout] | ^^^^^ ---------------------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/types/chainstate.rs:305:1 [INFO] [stdout] | [INFO] [stdout] 305 | impl_byte_array_rusqlite_only!(VRFSeed); [INFO] [stdout] | --------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `impl_byte_array_rusqlite_only` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> stacks-common/src/util/macros.rs:642:23 [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result { [INFO] [stdout] | ^^^^^ ---------------------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/types/chainstate.rs:306:1 [INFO] [stdout] | [INFO] [stdout] 306 | impl_byte_array_rusqlite_only!(BurnchainHeaderHash); [INFO] [stdout] | --------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `impl_byte_array_rusqlite_only` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> stacks-common/src/util/macros.rs:642:23 [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result { [INFO] [stdout] | ^^^^^ ---------------------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/types/chainstate.rs:307:1 [INFO] [stdout] | [INFO] [stdout] 307 | impl_byte_array_rusqlite_only!(VRFProof); [INFO] [stdout] | ---------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `impl_byte_array_rusqlite_only` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> stacks-common/src/util/macros.rs:642:23 [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result { [INFO] [stdout] | ^^^^^ ---------------------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/types/chainstate.rs:308:1 [INFO] [stdout] | [INFO] [stdout] 308 | impl_byte_array_rusqlite_only!(TrieHash); [INFO] [stdout] | ---------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `impl_byte_array_rusqlite_only` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> stacks-common/src/util/macros.rs:642:23 [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result { [INFO] [stdout] | ^^^^^ ---------------------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/types/chainstate.rs:309:1 [INFO] [stdout] | [INFO] [stdout] 309 | impl_byte_array_rusqlite_only!(Sha512Trunc256Sum); [INFO] [stdout] | ------------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `impl_byte_array_rusqlite_only` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> stacks-common/src/util/macros.rs:642:23 [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result { [INFO] [stdout] | ^^^^^ ---------------------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: stacks-common/src/types/chainstate.rs:310:1 [INFO] [stdout] | [INFO] [stdout] 310 | impl_byte_array_rusqlite_only!(MessageSignature); [INFO] [stdout] | ------------------------------------------------ in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `impl_byte_array_rusqlite_only` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 642 | fn to_sql(&self) -> rusqlite::Result> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> stacks-common/src/types/chainstate.rs:356:15 [INFO] [stdout] | [INFO] [stdout] 356 | fn to_sql(&self) -> rusqlite::Result { [INFO] [stdout] | ^^^^^ ----------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 356 | fn to_sql(&self) -> rusqlite::Result> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> stacks-common/src/deps_common/bitcoin/blockdata/script.rs:392:17 [INFO] [stdout] | [INFO] [stdout] 392 | pub fn iter(&self, enforce_minimal: bool) -> Instructions { [INFO] [stdout] | ^^^^^ ------------ the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 392 | pub fn iter(&self, enforce_minimal: bool) -> Instructions<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Compiling clarity v0.0.1 (/opt/rustwide/workdir/clarity) [INFO] [stdout] warning: unexpected `cfg` condition name: `rollback_value_check` [INFO] [stdout] --> clarity/src/vm/database/key_value_wrapper.rs:31:7 [INFO] [stdout] | [INFO] [stdout] 31 | #[cfg(rollback_value_check)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(rollback_value_check)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(rollback_value_check)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `rollback_value_check` [INFO] [stdout] --> clarity/src/vm/database/key_value_wrapper.rs:33:11 [INFO] [stdout] | [INFO] [stdout] 33 | #[cfg(not(rollback_value_check))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(rollback_value_check)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(rollback_value_check)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `rollback_value_check` [INFO] [stdout] --> clarity/src/vm/database/key_value_wrapper.rs:36:11 [INFO] [stdout] | [INFO] [stdout] 36 | #[cfg(not(rollback_value_check))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(rollback_value_check)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(rollback_value_check)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `rollback_value_check` [INFO] [stdout] --> clarity/src/vm/database/key_value_wrapper.rs:39:11 [INFO] [stdout] | [INFO] [stdout] 39 | #[cfg(not(rollback_value_check))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(rollback_value_check)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(rollback_value_check)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `rollback_value_check` [INFO] [stdout] --> clarity/src/vm/database/key_value_wrapper.rs:47:11 [INFO] [stdout] | [INFO] [stdout] 47 | #[cfg(not(rollback_value_check))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(rollback_value_check)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(rollback_value_check)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `rollback_value_check` [INFO] [stdout] --> clarity/src/vm/database/key_value_wrapper.rs:71:7 [INFO] [stdout] | [INFO] [stdout] 71 | #[cfg(rollback_value_check)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(rollback_value_check)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(rollback_value_check)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `rollback_value_check` [INFO] [stdout] --> clarity/src/vm/database/key_value_wrapper.rs:75:7 [INFO] [stdout] | [INFO] [stdout] 75 | #[cfg(rollback_value_check)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(rollback_value_check)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(rollback_value_check)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `rollback_value_check` [INFO] [stdout] --> clarity/src/vm/database/key_value_wrapper.rs:84:7 [INFO] [stdout] | [INFO] [stdout] 84 | #[cfg(rollback_value_check)] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(rollback_value_check)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(rollback_value_check)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> clarity/src/vm/costs/mod.rs:1017:15 [INFO] [stdout] | [INFO] [stdout] 1017 | fn to_sql(&self) -> rusqlite::Result { [INFO] [stdout] | ^^^^^ ----------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 1017 | fn to_sql(&self) -> rusqlite::Result> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> clarity/src/vm/contexts.rs:1600:29 [INFO] [stdout] | [INFO] [stdout] 1600 | pub fn function_context(&self) -> &LocalContext { [INFO] [stdout] | ^^^^^ ------------- [INFO] [stdout] | | || [INFO] [stdout] | | |the lifetimes get resolved as `'_` [INFO] [stdout] | | the lifetimes get resolved as `'_` [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 1600 | pub fn function_context(&self) -> &LocalContext<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> clarity/src/vm/database/key_value_wrapper.rs:194:24 [INFO] [stdout] | [INFO] [stdout] 194 | pub fn new(store: &'a mut dyn ClarityBackingStore) -> RollbackWrapper { [INFO] [stdout] | ^^ --------------- the lifetime gets resolved as `'a` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 194 | pub fn new(store: &'a mut dyn ClarityBackingStore) -> RollbackWrapper<'a> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> clarity/src/vm/database/key_value_wrapper.rs:205:17 [INFO] [stdout] | [INFO] [stdout] 205 | store: &'a mut dyn ClarityBackingStore, [INFO] [stdout] | ^^ this lifetime flows to the output [INFO] [stdout] 206 | log: RollbackWrapperPersistedLog, [INFO] [stdout] 207 | ) -> RollbackWrapper { [INFO] [stdout] | --------------- the lifetime gets resolved as `'a` [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 207 | ) -> RollbackWrapper<'a> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: call to `.clone()` on a reference in this situation does nothing [INFO] [stdout] --> clarity/src/vm/analysis/errors.rs:210:39 [INFO] [stdout] | [INFO] [stdout] 210 | self.expressions.replace(exprs.clone().to_vec()); [INFO] [stdout] | ^^^^^^^^ help: remove this redundant call [INFO] [stdout] | [INFO] [stdout] = note: the type `[SymbolicExpression]` does not implement `Clone`, so calling `clone` on `&[SymbolicExpression]` copies the reference, which does not do anything and can be removed [INFO] [stdout] = note: `#[warn(noop_method_call)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Compiling blockstack-core v0.0.1 (/opt/rustwide/workdir) [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> src/net/mod.rs:459:1 [INFO] [stdout] | [INFO] [stdout] 459 | impl_array_newtype!(PeerAddress, u8, 16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `monitoring_prom`, `prometheus`, `slog-json`, and `slog_json` [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 `impl_array_newtype` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_array_newtype` may come from an old version of the `stacks_common` crate, try updating your dependency with `cargo update -p stacks_common` [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 `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> src/chainstate/burn/mod.rs:58:1 [INFO] [stdout] | [INFO] [stdout] 58 | impl_array_newtype!(OpsHash, u8, 32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `monitoring_prom`, `prometheus`, `slog-json`, and `slog_json` [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 `impl_array_newtype` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_array_newtype` may come from an old version of the `stacks_common` crate, try updating your dependency with `cargo update -p stacks_common` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> src/chainstate/burn/mod.rs:64:1 [INFO] [stdout] | [INFO] [stdout] 64 | impl_array_newtype!(SortitionHash, u8, 32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `monitoring_prom`, `prometheus`, `slog-json`, and `slog_json` [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 `impl_array_newtype` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_array_newtype` may come from an old version of the `stacks_common` crate, try updating your dependency with `cargo update -p stacks_common` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unnecessary parentheses around match arm expression [INFO] [stdout] --> src/chainstate/burn/db/sortdb.rs:2464:39 [INFO] [stdout] | [INFO] [stdout] 2464 | StacksEpochId::Epoch20 => (version == "1" || version == "2" || version == "3"), [INFO] [stdout] | ^ ^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(unused_parens)]` on by default [INFO] [stdout] help: remove these parentheses [INFO] [stdout] | [INFO] [stdout] 2464 - StacksEpochId::Epoch20 => (version == "1" || version == "2" || version == "3"), [INFO] [stdout] 2464 + StacksEpochId::Epoch20 => version == "1" || version == "2" || version == "3", [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unnecessary parentheses around match arm expression [INFO] [stdout] --> src/chainstate/burn/db/sortdb.rs:2465:41 [INFO] [stdout] | [INFO] [stdout] 2465 | StacksEpochId::Epoch2_05 => (version == "2" || version == "3"), [INFO] [stdout] | ^ ^ [INFO] [stdout] | [INFO] [stdout] help: remove these parentheses [INFO] [stdout] | [INFO] [stdout] 2465 - StacksEpochId::Epoch2_05 => (version == "2" || version == "3"), [INFO] [stdout] 2465 + StacksEpochId::Epoch2_05 => version == "2" || version == "3", [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> src/chainstate/stacks/mod.rs:556:1 [INFO] [stdout] | [INFO] [stdout] 556 | impl_array_newtype!(CoinbasePayload, u8, 32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `monitoring_prom`, `prometheus`, `slog-json`, and `slog_json` [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 `impl_array_newtype` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_array_newtype` may come from an old version of the `stacks_common` crate, try updating your dependency with `cargo update -p stacks_common` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> src/chainstate/stacks/mod.rs:564:1 [INFO] [stdout] | [INFO] [stdout] 564 | impl_array_newtype!(TokenTransferMemo, u8, 34); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `monitoring_prom`, `prometheus`, `slog-json`, and `slog_json` [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 `impl_array_newtype` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_array_newtype` may come from an old version of the `stacks_common` crate, try updating your dependency with `cargo update -p stacks_common` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unnecessary parentheses around match arm expression [INFO] [stdout] --> src/chainstate/stacks/db/mod.rs:195:39 [INFO] [stdout] | [INFO] [stdout] 195 | StacksEpochId::Epoch20 => (self.version == "1" || self.version == "2"), [INFO] [stdout] | ^ ^ [INFO] [stdout] | [INFO] [stdout] help: remove these parentheses [INFO] [stdout] | [INFO] [stdout] 195 - StacksEpochId::Epoch20 => (self.version == "1" || self.version == "2"), [INFO] [stdout] 195 + StacksEpochId::Epoch20 => self.version == "1" || self.version == "2", [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> src/chainstate/stacks/index/mod.rs:229:1 [INFO] [stdout] | [INFO] [stdout] 229 | impl_array_newtype!(MARFValue, u8, 40); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `monitoring_prom`, `prometheus`, `slog-json`, and `slog_json` [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 `impl_array_newtype` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_array_newtype` may come from an old version of the `stacks_common` crate, try updating your dependency with `cargo update -p stacks_common` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> src/chainstate/stacks/index/node.rs:117:1 [INFO] [stdout] | [INFO] [stdout] 117 | impl_array_newtype!(TriePath, u8, 32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `monitoring_prom`, `prometheus`, `slog-json`, and `slog_json` [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 `impl_array_newtype` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_array_newtype` may come from an old version of the `stacks_common` crate, try updating your dependency with `cargo update -p stacks_common` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unnecessary parentheses around match arm expression [INFO] [stdout] --> src/chainstate/stacks/index/storage.rs:1830:21 [INFO] [stdout] | [INFO] [stdout] 1830 | None => (1024), // don't try to guess _byte_ allocation here. [INFO] [stdout] | ^ ^ [INFO] [stdout] | [INFO] [stdout] help: remove these parentheses [INFO] [stdout] | [INFO] [stdout] 1830 - None => (1024), // don't try to guess _byte_ allocation here. [INFO] [stdout] 1830 + None => 1024, // don't try to guess _byte_ allocation here. [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unnecessary parentheses around match arm expression [INFO] [stdout] --> src/chainstate/stacks/index/storage.rs:1872:29 [INFO] [stdout] | [INFO] [stdout] 1872 | None => (1024), // don't try to guess _byte_ allocation here. [INFO] [stdout] | ^ ^ [INFO] [stdout] | [INFO] [stdout] help: remove these parentheses [INFO] [stdout] | [INFO] [stdout] 1872 - None => (1024), // don't try to guess _byte_ allocation here. [INFO] [stdout] 1872 + None => 1024, // don't try to guess _byte_ allocation here. [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> src/burnchains/mod.rs:66:1 [INFO] [stdout] | [INFO] [stdout] 66 | impl_array_newtype!(Txid, u8, 32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `monitoring_prom`, `prometheus`, `slog-json`, and `slog_json` [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 `impl_array_newtype` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_array_newtype` may come from an old version of the `stacks_common` crate, try updating your dependency with `cargo update -p stacks_common` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> src/burnchains/mod.rs:75:1 [INFO] [stdout] | [INFO] [stdout] 75 | impl_array_newtype!(MagicBytes, u8, MAGIC_BYTES_LENGTH); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `monitoring_prom`, `prometheus`, `slog-json`, and `slog_json` [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 `impl_array_newtype` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_array_newtype` may come from an old version of the `stacks_common` crate, try updating your dependency with `cargo update -p stacks_common` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `httparse_min_2018` [INFO] [stdout] --> src/deps/httparse/mod.rs:25:13 [INFO] [stdout] | [INFO] [stdout] 25 | #![cfg_attr(httparse_min_2018, allow(rust_2018_idioms))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(httparse_min_2018)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(httparse_min_2018)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin` [INFO] [stdout] --> src/clarity_cli.rs:104:12 [INFO] [stdout] | [INFO] [stdout] 104 | #[cfg_attr(tarpaulin, skip)] [INFO] [stdout] | ^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tarpaulin)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tarpaulin)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin` [INFO] [stdout] --> src/clarity_cli.rs:127:12 [INFO] [stdout] | [INFO] [stdout] 127 | #[cfg_attr(tarpaulin, skip)] [INFO] [stdout] | ^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tarpaulin)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tarpaulin)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin` [INFO] [stdout] --> src/clarity_cli.rs:135:12 [INFO] [stdout] | [INFO] [stdout] 135 | #[cfg_attr(tarpaulin, skip)] [INFO] [stdout] | ^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tarpaulin)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tarpaulin)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> src/net/mod.rs:459:1 [INFO] [stdout] | [INFO] [stdout] 459 | impl_array_newtype!(PeerAddress, u8, 16); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `monitoring_prom`, `prometheus`, `slog-json`, and `slog_json` [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 `impl_array_newtype` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_array_newtype` may come from an old version of the `stacks_common` crate, try updating your dependency with `cargo update -p stacks_common` [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 `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> src/chainstate/burn/mod.rs:58:1 [INFO] [stdout] | [INFO] [stdout] 58 | impl_array_newtype!(OpsHash, u8, 32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `monitoring_prom`, `prometheus`, `slog-json`, and `slog_json` [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 `impl_array_newtype` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_array_newtype` may come from an old version of the `stacks_common` crate, try updating your dependency with `cargo update -p stacks_common` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> src/chainstate/burn/mod.rs:64:1 [INFO] [stdout] | [INFO] [stdout] 64 | impl_array_newtype!(SortitionHash, u8, 32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `monitoring_prom`, `prometheus`, `slog-json`, and `slog_json` [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 `impl_array_newtype` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_array_newtype` may come from an old version of the `stacks_common` crate, try updating your dependency with `cargo update -p stacks_common` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unnecessary parentheses around match arm expression [INFO] [stdout] --> src/chainstate/burn/db/sortdb.rs:2464:39 [INFO] [stdout] | [INFO] [stdout] 2464 | StacksEpochId::Epoch20 => (version == "1" || version == "2" || version == "3"), [INFO] [stdout] | ^ ^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(unused_parens)]` on by default [INFO] [stdout] help: remove these parentheses [INFO] [stdout] | [INFO] [stdout] 2464 - StacksEpochId::Epoch20 => (version == "1" || version == "2" || version == "3"), [INFO] [stdout] 2464 + StacksEpochId::Epoch20 => version == "1" || version == "2" || version == "3", [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unnecessary parentheses around match arm expression [INFO] [stdout] --> src/chainstate/burn/db/sortdb.rs:2465:41 [INFO] [stdout] | [INFO] [stdout] 2465 | StacksEpochId::Epoch2_05 => (version == "2" || version == "3"), [INFO] [stdout] | ^ ^ [INFO] [stdout] | [INFO] [stdout] help: remove these parentheses [INFO] [stdout] | [INFO] [stdout] 2465 - StacksEpochId::Epoch2_05 => (version == "2" || version == "3"), [INFO] [stdout] 2465 + StacksEpochId::Epoch2_05 => version == "2" || version == "3", [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> src/chainstate/stacks/mod.rs:556:1 [INFO] [stdout] | [INFO] [stdout] 556 | impl_array_newtype!(CoinbasePayload, u8, 32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `monitoring_prom`, `prometheus`, `slog-json`, and `slog_json` [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 `impl_array_newtype` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_array_newtype` may come from an old version of the `stacks_common` crate, try updating your dependency with `cargo update -p stacks_common` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> src/chainstate/stacks/mod.rs:564:1 [INFO] [stdout] | [INFO] [stdout] 564 | impl_array_newtype!(TokenTransferMemo, u8, 34); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `monitoring_prom`, `prometheus`, `slog-json`, and `slog_json` [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 `impl_array_newtype` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_array_newtype` may come from an old version of the `stacks_common` crate, try updating your dependency with `cargo update -p stacks_common` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unnecessary parentheses around match arm expression [INFO] [stdout] --> src/chainstate/stacks/db/mod.rs:195:39 [INFO] [stdout] | [INFO] [stdout] 195 | StacksEpochId::Epoch20 => (self.version == "1" || self.version == "2"), [INFO] [stdout] | ^ ^ [INFO] [stdout] | [INFO] [stdout] help: remove these parentheses [INFO] [stdout] | [INFO] [stdout] 195 - StacksEpochId::Epoch20 => (self.version == "1" || self.version == "2"), [INFO] [stdout] 195 + StacksEpochId::Epoch20 => self.version == "1" || self.version == "2", [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> src/chainstate/stacks/index/mod.rs:229:1 [INFO] [stdout] | [INFO] [stdout] 229 | impl_array_newtype!(MARFValue, u8, 40); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `monitoring_prom`, `prometheus`, `slog-json`, and `slog_json` [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 `impl_array_newtype` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_array_newtype` may come from an old version of the `stacks_common` crate, try updating your dependency with `cargo update -p stacks_common` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> src/chainstate/stacks/index/node.rs:117:1 [INFO] [stdout] | [INFO] [stdout] 117 | impl_array_newtype!(TriePath, u8, 32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `monitoring_prom`, `prometheus`, `slog-json`, and `slog_json` [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 `impl_array_newtype` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_array_newtype` may come from an old version of the `stacks_common` crate, try updating your dependency with `cargo update -p stacks_common` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unnecessary parentheses around match arm expression [INFO] [stdout] --> src/chainstate/stacks/index/storage.rs:1830:21 [INFO] [stdout] | [INFO] [stdout] 1830 | None => (1024), // don't try to guess _byte_ allocation here. [INFO] [stdout] | ^ ^ [INFO] [stdout] | [INFO] [stdout] help: remove these parentheses [INFO] [stdout] | [INFO] [stdout] 1830 - None => (1024), // don't try to guess _byte_ allocation here. [INFO] [stdout] 1830 + None => 1024, // don't try to guess _byte_ allocation here. [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unnecessary parentheses around match arm expression [INFO] [stdout] --> src/chainstate/stacks/index/storage.rs:1872:29 [INFO] [stdout] | [INFO] [stdout] 1872 | None => (1024), // don't try to guess _byte_ allocation here. [INFO] [stdout] | ^ ^ [INFO] [stdout] | [INFO] [stdout] help: remove these parentheses [INFO] [stdout] | [INFO] [stdout] 1872 - None => (1024), // don't try to guess _byte_ allocation here. [INFO] [stdout] 1872 + None => 1024, // don't try to guess _byte_ allocation here. [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> src/burnchains/mod.rs:66:1 [INFO] [stdout] | [INFO] [stdout] 66 | impl_array_newtype!(Txid, u8, 32); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `monitoring_prom`, `prometheus`, `slog-json`, and `slog_json` [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 `impl_array_newtype` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_array_newtype` may come from an old version of the `stacks_common` crate, try updating your dependency with `cargo update -p stacks_common` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `clippy` [INFO] [stdout] --> src/burnchains/mod.rs:75:1 [INFO] [stdout] | [INFO] [stdout] 75 | impl_array_newtype!(MagicBytes, u8, MAGIC_BYTES_LENGTH); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `monitoring_prom`, `prometheus`, `slog-json`, and `slog_json` [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 `impl_array_newtype` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `impl_array_newtype` may come from an old version of the `stacks_common` crate, try updating your dependency with `cargo update -p stacks_common` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `impl_array_newtype` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `httparse_min_2018` [INFO] [stdout] --> src/deps/httparse/mod.rs:25:13 [INFO] [stdout] | [INFO] [stdout] 25 | #![cfg_attr(httparse_min_2018, allow(rust_2018_idioms))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(httparse_min_2018)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(httparse_min_2018)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `std` [INFO] [stdout] --> src/deps/httparse/mod.rs:1288:11 [INFO] [stdout] | [INFO] [stdout] 1288 | #[cfg(feature = "std")] [INFO] [stdout] | ^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `default`, `developer-mode`, `monitoring_prom`, `prometheus`, `slog-json`, and `slog_json` [INFO] [stdout] = help: consider adding `std` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] note: the lint level is defined here [INFO] [stdout] --> src/deps/httparse/mod.rs:22:24 [INFO] [stdout] | [INFO] [stdout] 22 | #![cfg_attr(test, deny(warnings))] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` implied by `#[warn(warnings)]` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin` [INFO] [stdout] --> src/clarity_cli.rs:104:12 [INFO] [stdout] | [INFO] [stdout] 104 | #[cfg_attr(tarpaulin, skip)] [INFO] [stdout] | ^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tarpaulin)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tarpaulin)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin` [INFO] [stdout] --> src/clarity_cli.rs:127:12 [INFO] [stdout] | [INFO] [stdout] 127 | #[cfg_attr(tarpaulin, skip)] [INFO] [stdout] | ^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tarpaulin)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tarpaulin)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `tarpaulin` [INFO] [stdout] --> src/clarity_cli.rs:135:12 [INFO] [stdout] | [INFO] [stdout] 135 | #[cfg_attr(tarpaulin, skip)] [INFO] [stdout] | ^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: consider using a Cargo feature instead [INFO] [stdout] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stdout] [lints.rust] [INFO] [stdout] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(tarpaulin)'] } [INFO] [stdout] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(tarpaulin)");` to the top of the `build.rs` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: irrefutable `if let` pattern [INFO] [stdout] --> src/net/http.rs:2573:28 [INFO] [stdout] | [INFO] [stdout] 2573 | if let Ok(pages_indexes_value) = value.parse::() { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this pattern will always match, so the `if let` is useless [INFO] [stdout] = help: consider replacing the `if let` with a `let` [INFO] [stdout] = note: `#[warn(irrefutable_let_patterns)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: variable does not need to be mutable [INFO] [stdout] --> src/chainstate/stacks/index/storage.rs:878:21 [INFO] [stdout] | [INFO] [stdout] 878 | let mut ptrs = next_node.ptrs_mut(); [INFO] [stdout] | ----^^^^ [INFO] [stdout] | | [INFO] [stdout] | help: remove this `mut` [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(unused_mut)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: call to `.clone()` on a reference in this situation does nothing [INFO] [stdout] --> src/net/atlas/download.rs:690:39 [INFO] [stdout] | [INFO] [stdout] 690 | ... domain.clone(), [INFO] [stdout] | ^^^^^^^^ help: remove this redundant call [INFO] [stdout] | [INFO] [stdout] = note: the type `str` does not implement `Clone`, so calling `clone` on `&str` copies the reference, which does not do anything and can be removed [INFO] [stdout] = note: `#[warn(noop_method_call)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: using `.clone()` on a double reference, which returns `&stacks_common::types::chainstate::BurnchainHeaderHash` instead of cloning the inner type [INFO] [stdout] --> src/net/chat.rs:647:33 [INFO] [stdout] | [INFO] [stdout] 647 | Some(ref bhh) => bhh.clone(), [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(suspicious_double_ref_op)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: call to `.clone()` on a reference in this situation does nothing [INFO] [stdout] --> src/net/download.rs:364:31 [INFO] [stdout] | [INFO] [stdout] 364 | domain.clone(), [INFO] [stdout] | ^^^^^^^^ help: remove this redundant call [INFO] [stdout] | [INFO] [stdout] = note: the type `str` does not implement `Clone`, so calling `clone` on `&str` copies the reference, which does not do anything and can be removed [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: call to `.clone()` on a reference in this situation does nothing [INFO] [stdout] --> src/net/p2p.rs:3255:27 [INFO] [stdout] | [INFO] [stdout] 3255 | domain.clone(), [INFO] [stdout] | ^^^^^^^^ help: remove this redundant call [INFO] [stdout] | [INFO] [stdout] = note: the type `str` does not implement `Clone`, so calling `clone` on `&str` copies the reference, which does not do anything and can be removed [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/util_lib/db.rs:313:23 [INFO] [stdout] | [INFO] [stdout] 313 | fn to_sql(&self) -> rusqlite::Result { [INFO] [stdout] | ^^^^^ ---------------------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/chainstate/burn/db/mod.rs:45:1 [INFO] [stdout] | [INFO] [stdout] 45 | impl_byte_array_from_column!(Txid); [INFO] [stdout] | ---------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] = note: this warning originates in the macro `impl_byte_array_from_column` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 313 | fn to_sql(&self) -> rusqlite::Result> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/util_lib/db.rs:313:23 [INFO] [stdout] | [INFO] [stdout] 313 | fn to_sql(&self) -> rusqlite::Result { [INFO] [stdout] | ^^^^^ ---------------------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/chainstate/burn/db/mod.rs:50:1 [INFO] [stdout] | [INFO] [stdout] 50 | impl_byte_array_from_column!(OpsHash); [INFO] [stdout] | ------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `impl_byte_array_from_column` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 313 | fn to_sql(&self) -> rusqlite::Result> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/util_lib/db.rs:313:23 [INFO] [stdout] | [INFO] [stdout] 313 | fn to_sql(&self) -> rusqlite::Result { [INFO] [stdout] | ^^^^^ ---------------------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/chainstate/burn/db/mod.rs:52:1 [INFO] [stdout] | [INFO] [stdout] 52 | impl_byte_array_from_column!(SortitionHash); [INFO] [stdout] | ------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `impl_byte_array_from_column` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 313 | fn to_sql(&self) -> rusqlite::Result> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: using `.clone()` on a double reference, which returns `&stacks_common::types::chainstate::StacksBlockId` instead of cloning the inner type [INFO] [stdout] --> src/clarity_vm/database/marf.rs:90:46 [INFO] [stdout] | [INFO] [stdout] 90 | Some(ref miner_tip) => *miner_tip.clone(), [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: using `.clone()` on a double reference, which returns `&stacks_common::types::chainstate::StacksBlockId` instead of cloning the inner type [INFO] [stdout] --> src/clarity_vm/database/marf.rs:104:46 [INFO] [stdout] | [INFO] [stdout] 104 | Some(ref miner_tip) => *miner_tip.clone(), [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] error: could not compile `blockstack-core` (lib); 29 warnings emitted [INFO] [stderr] [INFO] [stderr] Caused by: [INFO] [stderr] process didn't exit successfully: `/opt/rustwide/rustup-home/toolchains/44f415c1d617ebc7b931a243b7b321ef8a6ca47c/bin/rustc --crate-name blockstack_lib --edition=2021 src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C debuginfo=2 --cfg 'feature="default"' --cfg 'feature="developer-mode"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("default", "developer-mode", "monitoring_prom", "prometheus", "slog-json", "slog_json"))' -C metadata=7f7e432df85075b5 -C extra-filename=-af63ff63b04a23d9 --out-dir /opt/rustwide/target/debug/deps -L dependency=/opt/rustwide/target/debug/deps --extern chrono=/opt/rustwide/target/debug/deps/libchrono-3a95bb4254621a84.rmeta --extern clarity=/opt/rustwide/target/debug/deps/libclarity-06b666b33dcb63bd.rmeta --extern curve25519_dalek=/opt/rustwide/target/debug/deps/libcurve25519_dalek-e54acad9b58fe7d7.rmeta --extern ed25519_dalek=/opt/rustwide/target/debug/deps/libed25519_dalek-a5dabebfcc18d66c.rmeta --extern integer_sqrt=/opt/rustwide/target/debug/deps/libinteger_sqrt-ba8c7c0500b20ca0.rmeta --extern lazy_static=/opt/rustwide/target/debug/deps/liblazy_static-ba6d9ac4e4243af3.rmeta --extern libc=/opt/rustwide/target/debug/deps/liblibc-f4f58afebe7a73e3.rmeta --extern mio=/opt/rustwide/target/debug/deps/libmio-0756ab7dcc601511.rmeta --extern nix=/opt/rustwide/target/debug/deps/libnix-7ed3660709ef8b06.rmeta --extern percent_encoding=/opt/rustwide/target/debug/deps/libpercent_encoding-772c90a786b3ee34.rmeta --extern rand=/opt/rustwide/target/debug/deps/librand-bfa25c0069dccd28.rmeta --extern rand_chacha=/opt/rustwide/target/debug/deps/librand_chacha-d6f13c19f0fd7d22.rmeta --extern regex=/opt/rustwide/target/debug/deps/libregex-a15aa221562d81a6.rmeta --extern ripemd=/opt/rustwide/target/debug/deps/libripemd-5dd754422833f3b1.rmeta --extern rusqlite=/opt/rustwide/target/debug/deps/librusqlite-b06f11edcdd49128.rmeta --extern secp256k1=/opt/rustwide/target/debug/deps/libsecp256k1-0cfecb110922873d.rmeta --extern serde=/opt/rustwide/target/debug/deps/libserde-145849f77f9f82b2.rmeta --extern serde_derive=/opt/rustwide/target/debug/deps/libserde_derive-be60c7aa77d3f635.so --extern serde_json=/opt/rustwide/target/debug/deps/libserde_json-81a1b95541e5649d.rmeta --extern serde_stacker=/opt/rustwide/target/debug/deps/libserde_stacker-728ba06acdd831bb.rmeta --extern sha2=/opt/rustwide/target/debug/deps/libsha2-fdc6d439ede37aab.rmeta --extern sha3=/opt/rustwide/target/debug/deps/libsha3-b2282ffa80608310.rmeta --extern siphasher=/opt/rustwide/target/debug/deps/libsiphasher-462cdee960a07c40.rmeta --extern slog=/opt/rustwide/target/debug/deps/libslog-cfc1f32820b601ad.rmeta --extern slog_term=/opt/rustwide/target/debug/deps/libslog_term-7de20722400fb47b.rmeta --extern stacks_common=/opt/rustwide/target/debug/deps/libstacks_common-7463ddfcd5c6f933.rmeta --extern time=/opt/rustwide/target/debug/deps/libtime-8b634e83702854e3.rmeta --extern url=/opt/rustwide/target/debug/deps/liburl-32dbfa93930dce0f.rmeta --cap-lints=warn -L native=/opt/rustwide/target/debug/build/libsqlite3-sys-d4f7517c8af8b453/out -L native=/opt/rustwide/target/debug/build/psm-19cf4901f26eef9c/out -L native=/opt/rustwide/target/debug/build/clear_on_drop-2384dfaa64504829/out -L native=/opt/rustwide/target/debug/build/secp256k1-sys-7ffd3593458202fb/out -L native=/opt/rustwide/target/debug/build/sha2-asm-c1dc542fb5b95f8b/out -L native=/opt/rustwide/target/debug/build/sha2-asm-c1dc542fb5b95f8b/out` (signal: 9, SIGKILL: kill) [INFO] [stderr] warning: build failed, waiting for other jobs to finish... [INFO] [stdout] warning: irrefutable `if let` pattern [INFO] [stdout] --> src/net/http.rs:2573:28 [INFO] [stdout] | [INFO] [stdout] 2573 | if let Ok(pages_indexes_value) = value.parse::() { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this pattern will always match, so the `if let` is useless [INFO] [stdout] = help: consider replacing the `if let` with a `let` [INFO] [stdout] = note: `#[warn(irrefutable_let_patterns)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: variable does not need to be mutable [INFO] [stdout] --> src/chainstate/stacks/index/storage.rs:878:21 [INFO] [stdout] | [INFO] [stdout] 878 | let mut ptrs = next_node.ptrs_mut(); [INFO] [stdout] | ----^^^^ [INFO] [stdout] | | [INFO] [stdout] | help: remove this `mut` [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(unused_mut)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: call to `.clone()` on a reference in this situation does nothing [INFO] [stdout] --> src/util_lib/db.rs:343:30 [INFO] [stdout] | [INFO] [stdout] 343 | let mut parts = sql_query.clone().split(" "); [INFO] [stdout] | ^^^^^^^^ help: remove this redundant call [INFO] [stdout] | [INFO] [stdout] = note: the type `str` does not implement `Clone`, so calling `clone` on `&str` copies the reference, which does not do anything and can be removed [INFO] [stdout] = note: `#[warn(noop_method_call)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: call to `.clone()` on a reference in this situation does nothing [INFO] [stdout] --> src/util_lib/strings.rs:350:50 [INFO] [stdout] | [INFO] [stdout] 350 | let clarity_str = ClarityName::try_from(s.clone()).unwrap(); [INFO] [stdout] | ^^^^^^^^ help: remove this redundant call [INFO] [stdout] | [INFO] [stdout] = note: the type `str` does not implement `Clone`, so calling `clone` on `&str` copies the reference, which does not do anything and can be removed [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: call to `.clone()` on a reference in this situation does nothing [INFO] [stdout] --> src/util_lib/strings.rs:351:52 [INFO] [stdout] | [INFO] [stdout] 351 | let contract_str = ContractName::try_from(s.clone()).unwrap(); [INFO] [stdout] | ^^^^^^^^ help: remove this redundant call [INFO] [stdout] | [INFO] [stdout] = note: the type `str` does not implement `Clone`, so calling `clone` on `&str` copies the reference, which does not do anything and can be removed [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: call to `.clone()` on a reference in this situation does nothing [INFO] [stdout] --> src/net/atlas/download.rs:690:39 [INFO] [stdout] | [INFO] [stdout] 690 | ... domain.clone(), [INFO] [stdout] | ^^^^^^^^ help: remove this redundant call [INFO] [stdout] | [INFO] [stdout] = note: the type `str` does not implement `Clone`, so calling `clone` on `&str` copies the reference, which does not do anything and can be removed [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: using `.clone()` on a double reference, which returns `&stacks_common::types::chainstate::BurnchainHeaderHash` instead of cloning the inner type [INFO] [stdout] --> src/net/chat.rs:647:33 [INFO] [stdout] | [INFO] [stdout] 647 | Some(ref bhh) => bhh.clone(), [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(suspicious_double_ref_op)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: call to `.clone()` on a reference in this situation does nothing [INFO] [stdout] --> src/net/download.rs:364:31 [INFO] [stdout] | [INFO] [stdout] 364 | domain.clone(), [INFO] [stdout] | ^^^^^^^^ help: remove this redundant call [INFO] [stdout] | [INFO] [stdout] = note: the type `str` does not implement `Clone`, so calling `clone` on `&str` copies the reference, which does not do anything and can be removed [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/net/download.rs:2799:20 [INFO] [stdout] | [INFO] [stdout] 2799 | test_name: &str, [INFO] [stdout] | ^^^^ this lifetime flows to the output [INFO] [stdout] ... [INFO] [stdout] 2807 | ) -> Vec [INFO] [stdout] | -------- the lifetime gets resolved as `'_` [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 2807 | ) -> Vec> [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/net/neighbors.rs:4980:23 [INFO] [stdout] | [INFO] [stdout] 4980 | peer_configs: &mut Vec, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ this lifetime flows to the output [INFO] [stdout] ... [INFO] [stdout] 4983 | ) -> Vec { [INFO] [stdout] | -------- the lifetime gets resolved as `'_` [INFO] [stdout] | [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 4983 | ) -> Vec> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/net/neighbors.rs:5039:23 [INFO] [stdout] | [INFO] [stdout] 5039 | peer_configs: &mut Vec, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ this lifetime flows to the output [INFO] [stdout] 5040 | neighbor_count: usize, [INFO] [stdout] 5041 | ) -> Vec { [INFO] [stdout] | -------- the lifetime gets resolved as `'_` [INFO] [stdout] | [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 5041 | ) -> Vec> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/net/neighbors.rs:5046:23 [INFO] [stdout] | [INFO] [stdout] 5046 | peer_configs: &mut Vec, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ this lifetime flows to the output [INFO] [stdout] 5047 | neighbor_count: usize, [INFO] [stdout] 5048 | ) -> Vec { [INFO] [stdout] | -------- the lifetime gets resolved as `'_` [INFO] [stdout] | [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 5048 | ) -> Vec> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/net/neighbors.rs:5186:23 [INFO] [stdout] | [INFO] [stdout] 5186 | peer_configs: &mut Vec, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ this lifetime flows to the output [INFO] [stdout] ... [INFO] [stdout] 5189 | ) -> Vec { [INFO] [stdout] | -------- the lifetime gets resolved as `'_` [INFO] [stdout] | [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 5189 | ) -> Vec> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/net/neighbors.rs:5194:23 [INFO] [stdout] | [INFO] [stdout] 5194 | peer_configs: &mut Vec, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ this lifetime flows to the output [INFO] [stdout] ... [INFO] [stdout] 5197 | ) -> Vec { [INFO] [stdout] | -------- the lifetime gets resolved as `'_` [INFO] [stdout] | [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 5197 | ) -> Vec> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/net/neighbors.rs:5202:23 [INFO] [stdout] | [INFO] [stdout] 5202 | peer_configs: &mut Vec, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ this lifetime flows to the output [INFO] [stdout] ... [INFO] [stdout] 5206 | ) -> Vec { [INFO] [stdout] | -------- the lifetime gets resolved as `'_` [INFO] [stdout] | [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 5206 | ) -> Vec> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/net/neighbors.rs:5397:23 [INFO] [stdout] | [INFO] [stdout] 5397 | peer_configs: &mut Vec, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ this lifetime flows to the output [INFO] [stdout] 5398 | neighbor_count: usize, [INFO] [stdout] 5399 | ) -> Vec { [INFO] [stdout] | -------- the lifetime gets resolved as `'_` [INFO] [stdout] | [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 5399 | ) -> Vec> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/net/neighbors.rs:5404:23 [INFO] [stdout] | [INFO] [stdout] 5404 | peer_configs: &mut Vec, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ this lifetime flows to the output [INFO] [stdout] 5405 | neighbor_count: usize, [INFO] [stdout] 5406 | ) -> Vec { [INFO] [stdout] | -------- the lifetime gets resolved as `'_` [INFO] [stdout] | [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 5406 | ) -> Vec> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/net/neighbors.rs:5411:23 [INFO] [stdout] | [INFO] [stdout] 5411 | peer_configs: &mut Vec, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ this lifetime flows to the output [INFO] [stdout] ... [INFO] [stdout] 5414 | ) -> Vec { [INFO] [stdout] | -------- the lifetime gets resolved as `'_` [INFO] [stdout] | [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 5414 | ) -> Vec> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/net/neighbors.rs:5467:23 [INFO] [stdout] | [INFO] [stdout] 5467 | peer_configs: &mut Vec, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^ this lifetime flows to the output [INFO] [stdout] 5468 | neighbor_count: usize, [INFO] [stdout] 5469 | ) -> Vec { [INFO] [stdout] | -------- the lifetime gets resolved as `'_` [INFO] [stdout] | [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 5469 | ) -> Vec> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: call to `.clone()` on a reference in this situation does nothing [INFO] [stdout] --> src/net/p2p.rs:3255:27 [INFO] [stdout] | [INFO] [stdout] 3255 | domain.clone(), [INFO] [stdout] | ^^^^^^^^ help: remove this redundant call [INFO] [stdout] | [INFO] [stdout] = note: the type `str` does not implement `Clone`, so calling `clone` on `&str` copies the reference, which does not do anything and can be removed [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: call to `.clone()` on a reference in this situation does nothing [INFO] [stdout] --> src/net/rpc.rs:3580:37 [INFO] [stdout] | [INFO] [stdout] 3580 | let contract = TEST_CONTRACT.clone(); [INFO] [stdout] | ^^^^^^^^ help: remove this redundant call [INFO] [stdout] | [INFO] [stdout] = note: the type `str` does not implement `Clone`, so calling `clone` on `&str` copies the reference, which does not do anything and can be removed [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: call to `.clone()` on a reference in this situation does nothing [INFO] [stdout] --> src/net/rpc.rs:3618:61 [INFO] [stdout] | [INFO] [stdout] 3618 | let unconfirmed_contract = TEST_CONTRACT_UNCONFIRMED.clone(); [INFO] [stdout] | ^^^^^^^^ help: remove this redundant call [INFO] [stdout] | [INFO] [stdout] = note: the type `str` does not implement `Clone`, so calling `clone` on `&str` copies the reference, which does not do anything and can be removed [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/util_lib/db.rs:313:23 [INFO] [stdout] | [INFO] [stdout] 313 | fn to_sql(&self) -> rusqlite::Result { [INFO] [stdout] | ^^^^^ ---------------------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/chainstate/burn/db/mod.rs:45:1 [INFO] [stdout] | [INFO] [stdout] 45 | impl_byte_array_from_column!(Txid); [INFO] [stdout] | ---------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `impl_byte_array_from_column` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 313 | fn to_sql(&self) -> rusqlite::Result> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/util_lib/db.rs:313:23 [INFO] [stdout] | [INFO] [stdout] 313 | fn to_sql(&self) -> rusqlite::Result { [INFO] [stdout] | ^^^^^ ---------------------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/chainstate/burn/db/mod.rs:50:1 [INFO] [stdout] | [INFO] [stdout] 50 | impl_byte_array_from_column!(OpsHash); [INFO] [stdout] | ------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `impl_byte_array_from_column` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 313 | fn to_sql(&self) -> rusqlite::Result> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/util_lib/db.rs:313:23 [INFO] [stdout] | [INFO] [stdout] 313 | fn to_sql(&self) -> rusqlite::Result { [INFO] [stdout] | ^^^^^ ---------------------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] ::: src/chainstate/burn/db/mod.rs:52:1 [INFO] [stdout] | [INFO] [stdout] 52 | impl_byte_array_from_column!(SortitionHash); [INFO] [stdout] | ------------------------------------------- in this macro invocation [INFO] [stdout] | [INFO] [stdout] = note: this warning originates in the macro `impl_byte_array_from_column` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 313 | fn to_sql(&self) -> rusqlite::Result> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: call to `.clone()` on a reference in this situation does nothing [INFO] [stdout] --> src/chainstate/stacks/db/transactions.rs:1694:29 [INFO] [stdout] | [INFO] [stdout] 1694 | contract_correct.clone(), [INFO] [stdout] | ^^^^^^^^ help: remove this redundant call [INFO] [stdout] | [INFO] [stdout] = note: the type `str` does not implement `Clone`, so calling `clone` on `&str` copies the reference, which does not do anything and can be removed [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: call to `.clone()` on a reference in this situation does nothing [INFO] [stdout] --> src/chainstate/stacks/db/transactions.rs:1695:29 [INFO] [stdout] | [INFO] [stdout] 1695 | contract_correct.clone(), [INFO] [stdout] | ^^^^^^^^ help: remove this redundant call [INFO] [stdout] | [INFO] [stdout] = note: the type `str` does not implement `Clone`, so calling `clone` on `&str` copies the reference, which does not do anything and can be removed [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/chainstate/stacks/index/marf.rs:1503:35 [INFO] [stdout] | [INFO] [stdout] 1503 | pub fn borrow_storage_backend(&mut self) -> TrieStorageConnection { [INFO] [stdout] | ^^^^^^^^^ ------------------------ the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 1503 | pub fn borrow_storage_backend(&mut self) -> TrieStorageConnection<'_, T> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> src/chainstate/stacks/index/marf.rs:1508:39 [INFO] [stdout] | [INFO] [stdout] 1508 | pub fn borrow_storage_transaction(&mut self) -> TrieStorageTransaction { [INFO] [stdout] | ^^^^^^^^^ ------------------------- the lifetime gets resolved as `'_` [INFO] [stdout] | | [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to remove the lifetime for references and use the anonymous lifetime for paths [INFO] [stdout] | [INFO] [stdout] 1508 | pub fn borrow_storage_transaction(&mut self) -> TrieStorageTransaction<'_, T> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: using `.clone()` on a double reference, which returns `&std::string::String` instead of cloning the inner type [INFO] [stdout] --> src/chainstate/stacks/miner.rs:2405:60 [INFO] [stdout] | [INFO] [stdout] 2405 | ... all_test_names.insert(test_name.clone()); [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: using `.clone()` on a double reference, which returns `&stacks_common::types::chainstate::StacksBlockId` instead of cloning the inner type [INFO] [stdout] --> src/clarity_vm/database/marf.rs:90:46 [INFO] [stdout] | [INFO] [stdout] 90 | Some(ref miner_tip) => *miner_tip.clone(), [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: using `.clone()` on a double reference, which returns `&stacks_common::types::chainstate::StacksBlockId` instead of cloning the inner type [INFO] [stdout] --> src/clarity_vm/database/marf.rs:104:46 [INFO] [stdout] | [INFO] [stdout] 104 | Some(ref miner_tip) => *miner_tip.clone(), [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] error: could not compile `blockstack-core` (lib test); 51 warnings emitted [INFO] [stderr] [INFO] [stderr] Caused by: [INFO] [stderr] process didn't exit successfully: `/opt/rustwide/rustup-home/toolchains/44f415c1d617ebc7b931a243b7b321ef8a6ca47c/bin/rustc --crate-name blockstack_lib --edition=2021 src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --emit=dep-info,link -C embed-bitcode=no -C debuginfo=2 --test --cfg 'feature="default"' --cfg 'feature="developer-mode"' --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values("default", "developer-mode", "monitoring_prom", "prometheus", "slog-json", "slog_json"))' -C metadata=0fb4dd1d2d810c23 -C extra-filename=-841e76f1a147d88d --out-dir /opt/rustwide/target/debug/deps -L dependency=/opt/rustwide/target/debug/deps --extern assert_json_diff=/opt/rustwide/target/debug/deps/libassert_json_diff-628ec28d0ee6d988.rlib --extern chrono=/opt/rustwide/target/debug/deps/libchrono-3a95bb4254621a84.rlib --extern clarity=/opt/rustwide/target/debug/deps/libclarity-06b666b33dcb63bd.rlib --extern criterion=/opt/rustwide/target/debug/deps/libcriterion-bb9b6db49dd11ecf.rlib --extern curve25519_dalek=/opt/rustwide/target/debug/deps/libcurve25519_dalek-e54acad9b58fe7d7.rlib --extern ed25519_dalek=/opt/rustwide/target/debug/deps/libed25519_dalek-a5dabebfcc18d66c.rlib --extern integer_sqrt=/opt/rustwide/target/debug/deps/libinteger_sqrt-ba8c7c0500b20ca0.rlib --extern lazy_static=/opt/rustwide/target/debug/deps/liblazy_static-ba6d9ac4e4243af3.rlib --extern libc=/opt/rustwide/target/debug/deps/liblibc-f4f58afebe7a73e3.rlib --extern mio=/opt/rustwide/target/debug/deps/libmio-0756ab7dcc601511.rlib --extern nix=/opt/rustwide/target/debug/deps/libnix-7ed3660709ef8b06.rlib --extern percent_encoding=/opt/rustwide/target/debug/deps/libpercent_encoding-772c90a786b3ee34.rlib --extern rand=/opt/rustwide/target/debug/deps/librand-bfa25c0069dccd28.rlib --extern rand_chacha=/opt/rustwide/target/debug/deps/librand_chacha-d6f13c19f0fd7d22.rlib --extern regex=/opt/rustwide/target/debug/deps/libregex-a15aa221562d81a6.rlib --extern ripemd=/opt/rustwide/target/debug/deps/libripemd-5dd754422833f3b1.rlib --extern rusqlite=/opt/rustwide/target/debug/deps/librusqlite-b06f11edcdd49128.rlib --extern secp256k1=/opt/rustwide/target/debug/deps/libsecp256k1-0cfecb110922873d.rlib --extern serde=/opt/rustwide/target/debug/deps/libserde-145849f77f9f82b2.rlib --extern serde_derive=/opt/rustwide/target/debug/deps/libserde_derive-be60c7aa77d3f635.so --extern serde_json=/opt/rustwide/target/debug/deps/libserde_json-81a1b95541e5649d.rlib --extern serde_stacker=/opt/rustwide/target/debug/deps/libserde_stacker-728ba06acdd831bb.rlib --extern sha2=/opt/rustwide/target/debug/deps/libsha2-fdc6d439ede37aab.rlib --extern sha3=/opt/rustwide/target/debug/deps/libsha3-b2282ffa80608310.rlib --extern siphasher=/opt/rustwide/target/debug/deps/libsiphasher-462cdee960a07c40.rlib --extern slog=/opt/rustwide/target/debug/deps/libslog-cfc1f32820b601ad.rlib --extern slog_term=/opt/rustwide/target/debug/deps/libslog_term-7de20722400fb47b.rlib --extern stacks_common=/opt/rustwide/target/debug/deps/libstacks_common-7463ddfcd5c6f933.rlib --extern stx_genesis=/opt/rustwide/target/debug/deps/libstx_genesis-8d11f2b587c43880.rlib --extern time=/opt/rustwide/target/debug/deps/libtime-8b634e83702854e3.rlib --extern url=/opt/rustwide/target/debug/deps/liburl-32dbfa93930dce0f.rlib --cap-lints=warn -L native=/opt/rustwide/target/debug/build/libsqlite3-sys-d4f7517c8af8b453/out -L native=/opt/rustwide/target/debug/build/psm-19cf4901f26eef9c/out -L native=/opt/rustwide/target/debug/build/clear_on_drop-2384dfaa64504829/out -L native=/opt/rustwide/target/debug/build/secp256k1-sys-7ffd3593458202fb/out -L native=/opt/rustwide/target/debug/build/sha2-asm-c1dc542fb5b95f8b/out -L native=/opt/rustwide/target/debug/build/sha2-asm-c1dc542fb5b95f8b/out` (signal: 9, SIGKILL: kill) [INFO] running `Command { std: "docker" "inspect" "d31e186ad52aa40b0f23678b5254a8371c2936782494ba957923ef5c5975bf04", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "d31e186ad52aa40b0f23678b5254a8371c2936782494ba957923ef5c5975bf04", kill_on_drop: false }` [INFO] [stdout] d31e186ad52aa40b0f23678b5254a8371c2936782494ba957923ef5c5975bf04