[INFO] fetching crate icann-rdap-common 0.0.22... [INFO] checking icann-rdap-common-0.0.22 against try#a4980311fb7bb9e7893708e6bd3fbbfb2819fd3d for pr-145342-1 [INFO] extracting crate icann-rdap-common 0.0.22 into /workspace/builds/worker-2-tc2/source [INFO] started tweaking crates.io crate icann-rdap-common 0.0.22 [INFO] finished tweaking crates.io crate icann-rdap-common 0.0.22 [INFO] tweaked toml for crates.io crate icann-rdap-common 0.0.22 written to /workspace/builds/worker-2-tc2/source/Cargo.toml [INFO] validating manifest of crates.io crate icann-rdap-common 0.0.22 on toolchain a4980311fb7bb9e7893708e6bd3fbbfb2819fd3d [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+a4980311fb7bb9e7893708e6bd3fbbfb2819fd3d" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+a4980311fb7bb9e7893708e6bd3fbbfb2819fd3d" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Updating crates.io index [INFO] [stderr] Locking 105 packages to latest compatible versions [INFO] [stderr] Adding buildstructor v0.5.4 (available: v0.6.0) [INFO] [stderr] Adding prefix-trie v0.2.5 (available: v0.8.1) [INFO] [stderr] Adding rstest v0.17.0 (available: v0.26.1) [INFO] [stderr] Adding strum v0.24.1 (available: v0.27.2) [INFO] [stderr] Adding strum_macros v0.24.3 (available: v0.27.2) [INFO] [stderr] Adding thiserror v1.0.69 (available: v2.0.16) [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+a4980311fb7bb9e7893708e6bd3fbbfb2819fd3d" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:7ad1b28ee6f5f7f699f6cf7015098d6ccdd96d6f2d78dd06228f5b4c9faf309c" "/opt/rustwide/cargo-home/bin/cargo" "+a4980311fb7bb9e7893708e6bd3fbbfb2819fd3d" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 61d46ddb522cf89df9e3442d63c484dd0f69928ac43485499badc23ff3d641a6 [INFO] running `Command { std: "docker" "start" "-a" "61d46ddb522cf89df9e3442d63c484dd0f69928ac43485499badc23ff3d641a6", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "61d46ddb522cf89df9e3442d63c484dd0f69928ac43485499badc23ff3d641a6", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "61d46ddb522cf89df9e3442d63c484dd0f69928ac43485499badc23ff3d641a6", kill_on_drop: false }` [INFO] [stdout] 61d46ddb522cf89df9e3442d63c484dd0f69928ac43485499badc23ff3d641a6 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:7ad1b28ee6f5f7f699f6cf7015098d6ccdd96d6f2d78dd06228f5b4c9faf309c" "/opt/rustwide/cargo-home/bin/cargo" "+a4980311fb7bb9e7893708e6bd3fbbfb2819fd3d" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 4c80337eaa6845afdc7cdd6b0762bbbf68fc5cb471795a5570e9381f37dd35f3 [INFO] running `Command { std: "docker" "start" "-a" "4c80337eaa6845afdc7cdd6b0762bbbf68fc5cb471795a5570e9381f37dd35f3", kill_on_drop: false }` [INFO] [stderr] Compiling proc-macro2 v1.0.101 [INFO] [stderr] Compiling unicode-ident v1.0.18 [INFO] [stderr] Checking stable_deref_trait v1.2.0 [INFO] [stderr] Checking memchr v2.7.5 [INFO] [stderr] Compiling serde v1.0.219 [INFO] [stderr] Checking litemap v0.8.0 [INFO] [stderr] Compiling semver v1.0.26 [INFO] [stderr] Checking writeable v0.6.1 [INFO] [stderr] Compiling serde_json v1.0.143 [INFO] [stderr] Compiling icu_normalizer_data v2.0.0 [INFO] [stderr] Compiling icu_properties_data v2.0.1 [INFO] [stderr] Compiling syn v1.0.109 [INFO] [stderr] Compiling autocfg v1.5.0 [INFO] [stderr] Checking futures-sink v0.3.31 [INFO] [stderr] Checking itoa v1.0.15 [INFO] [stderr] Checking ryu v1.0.20 [INFO] [stderr] Compiling schemars v0.8.22 [INFO] [stderr] Checking futures-core v0.3.31 [INFO] [stderr] Compiling thiserror v1.0.69 [INFO] [stderr] Compiling regex-syntax v0.8.6 [INFO] [stderr] Checking futures-task v0.3.31 [INFO] [stderr] Checking futures-channel v0.3.31 [INFO] [stderr] Checking slab v0.4.11 [INFO] [stderr] Checking pin-utils v0.1.0 [INFO] [stderr] Compiling rustversion v1.0.22 [INFO] [stderr] Checking smallvec v1.15.1 [INFO] [stderr] Checking dyn-clone v1.0.20 [INFO] [stderr] Checking futures-io v0.3.31 [INFO] [stderr] Checking pin-project-lite v0.2.16 [INFO] [stderr] Compiling unicode-xid v0.2.6 [INFO] [stderr] Compiling lazy_static v1.5.0 [INFO] [stderr] Compiling heck v0.4.1 [INFO] [stderr] Compiling num-traits v0.2.19 [INFO] [stderr] Checking utf8_iter v1.0.4 [INFO] [stderr] Checking iana-time-zone v0.1.63 [INFO] [stderr] Compiling cfg-if v1.0.3 [INFO] [stderr] Checking strum v0.24.1 [INFO] [stderr] Checking futures-timer v3.0.3 [INFO] [stderr] Checking cidr v0.3.1 [INFO] [stderr] Compiling rustc_version v0.4.1 [INFO] [stderr] Compiling quote v1.0.40 [INFO] [stderr] Compiling syn v2.0.106 [INFO] [stderr] Compiling const_format_proc_macros v0.2.34 [INFO] [stderr] Compiling rstest_macros v0.17.0 [INFO] [stderr] Compiling aho-corasick v1.1.3 [INFO] [stderr] Checking const_format v0.2.34 [INFO] [stderr] Compiling regex-automata v0.4.10 [INFO] [stderr] Compiling regex v1.11.2 [INFO] [stderr] Compiling synstructure v0.13.2 [INFO] [stderr] Compiling serde_derive_internals v0.29.1 [INFO] [stderr] Compiling str_inflector v0.12.0 [INFO] [stderr] Compiling strum_macros v0.24.3 [INFO] [stderr] Compiling zerofrom-derive v0.1.6 [INFO] [stderr] Compiling yoke-derive v0.8.0 [INFO] [stderr] Compiling zerovec-derive v0.11.1 [INFO] [stderr] Compiling displaydoc v0.2.5 [INFO] [stderr] Compiling serde_derive v1.0.219 [INFO] [stderr] Compiling futures-macro v0.3.31 [INFO] [stderr] Compiling thiserror-impl v1.0.69 [INFO] [stderr] Compiling try_match_inner v0.5.2 [INFO] [stderr] Compiling schemars_derive v0.8.22 [INFO] [stderr] Compiling try_match v0.4.2 [INFO] [stderr] Compiling buildstructor v0.5.4 [INFO] [stderr] Checking zerofrom v0.1.6 [INFO] [stderr] Checking futures-util v0.3.31 [INFO] [stderr] Checking yoke v0.8.0 [INFO] [stderr] Checking zerovec v0.11.4 [INFO] [stderr] Checking zerotrie v0.2.2 [INFO] [stderr] Checking tinystr v0.8.1 [INFO] [stderr] Checking potential_utf v0.1.2 [INFO] [stderr] Checking icu_collections v2.0.0 [INFO] [stderr] Checking icu_locale_core v2.0.0 [INFO] [stderr] Checking icu_provider v2.0.0 [INFO] [stderr] Checking icu_normalizer v2.0.0 [INFO] [stderr] Checking icu_properties v2.0.1 [INFO] [stderr] Checking futures-executor v0.3.31 [INFO] [stderr] Checking futures v0.3.31 [INFO] [stderr] Checking rstest v0.17.0 [INFO] [stderr] Checking idna_adapter v1.2.1 [INFO] [stderr] Checking idna v1.1.0 [INFO] [stderr] Checking chrono v0.4.41 [INFO] [stderr] Checking ipnet v2.11.0 [INFO] [stderr] Checking prefix-trie v0.2.5 [INFO] [stderr] Checking icann-rdap-common v0.0.22 (/opt/rustwide/workdir) [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/contact/mod.rs:147:1 [INFO] [stdout] | [INFO] [stdout] 147 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [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 attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/contact/mod.rs:256:17 [INFO] [stdout] | [INFO] [stdout] 256 | #[derive(Debug, Builder, Clone, PartialEq, Eq, PartialOrd, Ord)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/contact/mod.rs:294:1 [INFO] [stdout] | [INFO] [stdout] 294 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/contact/mod.rs:359:1 [INFO] [stdout] | [INFO] [stdout] 359 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/contact/mod.rs:403:1 [INFO] [stdout] | [INFO] [stdout] 403 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/contact/mod.rs:449:1 [INFO] [stdout] | [INFO] [stdout] 449 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/httpdata.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/autnum.rs:72:1 [INFO] [stdout] | [INFO] [stdout] 72 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/common.rs:16:1 [INFO] [stdout] | [INFO] [stdout] 16 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/domain.rs:19:34 [INFO] [stdout] | [INFO] [stdout] 19 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/domain.rs:60:1 [INFO] [stdout] | [INFO] [stdout] 60 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/domain.rs:121:1 [INFO] [stdout] | [INFO] [stdout] 121 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/domain.rs:192:1 [INFO] [stdout] | [INFO] [stdout] 192 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/domain.rs:312:1 [INFO] [stdout] | [INFO] [stdout] 312 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/domain.rs:471:1 [INFO] [stdout] | [INFO] [stdout] 471 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/entity.rs:121:1 [INFO] [stdout] | [INFO] [stdout] 121 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/error.rs:36:1 [INFO] [stdout] | [INFO] [stdout] 36 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/help.rs:16:1 [INFO] [stdout] | [INFO] [stdout] 16 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/nameserver.rs:25:1 [INFO] [stdout] | [INFO] [stdout] 25 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/nameserver.rs:143:1 [INFO] [stdout] | [INFO] [stdout] 143 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/network.rs:51:1 [INFO] [stdout] | [INFO] [stdout] 51 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/network.rs:94:1 [INFO] [stdout] | [INFO] [stdout] 94 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/network.rs:202:1 [INFO] [stdout] | [INFO] [stdout] 202 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/obj_common.rs:40:1 [INFO] [stdout] | [INFO] [stdout] 40 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/redacted.rs:59:10 [INFO] [stdout] | [INFO] [stdout] 59 | #[derive(Builder, Serialize, Deserialize, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/search.rs:19:1 [INFO] [stdout] | [INFO] [stdout] 19 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/search.rs:53:1 [INFO] [stdout] | [INFO] [stdout] 53 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/search.rs:87:1 [INFO] [stdout] | [INFO] [stdout] 87 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/types.rs:192:1 [INFO] [stdout] | [INFO] [stdout] 192 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/types.rs:359:1 [INFO] [stdout] | [INFO] [stdout] 359 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/types.rs:548:1 [INFO] [stdout] | [INFO] [stdout] 548 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/types.rs:637:1 [INFO] [stdout] | [INFO] [stdout] 637 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/contact/mod.rs:147:1 [INFO] [stdout] | [INFO] [stdout] 147 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [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 attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/contact/mod.rs:256:17 [INFO] [stdout] | [INFO] [stdout] 256 | #[derive(Debug, Builder, Clone, PartialEq, Eq, PartialOrd, Ord)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/contact/mod.rs:294:1 [INFO] [stdout] | [INFO] [stdout] 294 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/contact/mod.rs:359:1 [INFO] [stdout] | [INFO] [stdout] 359 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/contact/mod.rs:403:1 [INFO] [stdout] | [INFO] [stdout] 403 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/contact/mod.rs:449:1 [INFO] [stdout] | [INFO] [stdout] 449 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/httpdata.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/autnum.rs:72:1 [INFO] [stdout] | [INFO] [stdout] 72 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/common.rs:16:1 [INFO] [stdout] | [INFO] [stdout] 16 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/domain.rs:19:34 [INFO] [stdout] | [INFO] [stdout] 19 | #[derive(Serialize, Deserialize, Builder, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/domain.rs:60:1 [INFO] [stdout] | [INFO] [stdout] 60 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/domain.rs:121:1 [INFO] [stdout] | [INFO] [stdout] 121 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/domain.rs:192:1 [INFO] [stdout] | [INFO] [stdout] 192 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/domain.rs:312:1 [INFO] [stdout] | [INFO] [stdout] 312 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/domain.rs:471:1 [INFO] [stdout] | [INFO] [stdout] 471 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/entity.rs:121:1 [INFO] [stdout] | [INFO] [stdout] 121 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/error.rs:36:1 [INFO] [stdout] | [INFO] [stdout] 36 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/help.rs:16:1 [INFO] [stdout] | [INFO] [stdout] 16 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/nameserver.rs:25:1 [INFO] [stdout] | [INFO] [stdout] 25 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/nameserver.rs:143:1 [INFO] [stdout] | [INFO] [stdout] 143 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/network.rs:51:1 [INFO] [stdout] | [INFO] [stdout] 51 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/network.rs:94:1 [INFO] [stdout] | [INFO] [stdout] 94 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/network.rs:202:1 [INFO] [stdout] | [INFO] [stdout] 202 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/obj_common.rs:40:1 [INFO] [stdout] | [INFO] [stdout] 40 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/redacted.rs:59:10 [INFO] [stdout] | [INFO] [stdout] 59 | #[derive(Builder, Serialize, Deserialize, Clone, Debug, PartialEq, Eq)] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/search.rs:19:1 [INFO] [stdout] | [INFO] [stdout] 19 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/search.rs:53:1 [INFO] [stdout] | [INFO] [stdout] 53 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/search.rs:87:1 [INFO] [stdout] | [INFO] [stdout] 87 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/types.rs:192:1 [INFO] [stdout] | [INFO] [stdout] 192 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/types.rs:359:1 [INFO] [stdout] | [INFO] [stdout] 359 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/types.rs:548:1 [INFO] [stdout] | [INFO] [stdout] 548 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `cargo-clippy` [INFO] [stdout] --> src/response/types.rs:637:1 [INFO] [stdout] | [INFO] [stdout] 637 | #[buildstructor::buildstructor] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: no expected values for `feature` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `buildstructor::buildstructor` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the attribute macro `buildstructor::buildstructor` may come from an old version of the `buildstructor` crate, try updating your dependency with `cargo update -p buildstructor` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `buildstructor::buildstructor` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 32.66s [INFO] running `Command { std: "docker" "inspect" "4c80337eaa6845afdc7cdd6b0762bbbf68fc5cb471795a5570e9381f37dd35f3", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "4c80337eaa6845afdc7cdd6b0762bbbf68fc5cb471795a5570e9381f37dd35f3", kill_on_drop: false }` [INFO] [stdout] 4c80337eaa6845afdc7cdd6b0762bbbf68fc5cb471795a5570e9381f37dd35f3