[INFO] fetching crate inet2_addr 0.9.0... [INFO] testing inet2_addr-0.9.0 against master#cdb45c87e2cd43495379f7e867e3cc15dcee9f93 for pr-145838-1 [INFO] extracting crate inet2_addr 0.9.0 into /workspace/builds/worker-2-tc1/source [INFO] started tweaking crates.io crate inet2_addr 0.9.0 [INFO] finished tweaking crates.io crate inet2_addr 0.9.0 [INFO] tweaked toml for crates.io crate inet2_addr 0.9.0 written to /workspace/builds/worker-2-tc1/source/Cargo.toml [INFO] validating manifest of crates.io crate inet2_addr 0.9.0 on toolchain cdb45c87e2cd43495379f7e867e3cc15dcee9f93 [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+cdb45c87e2cd43495379f7e867e3cc15dcee9f93" "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" "+cdb45c87e2cd43495379f7e867e3cc15dcee9f93" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Updating crates.io index [INFO] [stderr] Locking 135 packages to latest compatible versions [INFO] [stderr] Adding amplify v3.14.2 (available: v4.9.0) [INFO] [stderr] Adding parse_arg v0.1.6 (available: v1.0.1) [INFO] [stderr] Adding secp256k1 v0.24.3 (available: v0.31.1) [INFO] [stderr] Adding strict_encoding v0.9.0 (available: v2.9.1) [INFO] [stderr] Adding subtle v2.4.1 (available: v2.6.1) [INFO] [stderr] Adding toml v0.5.11 (available: v0.9.5) [INFO] [stderr] Adding zeroize v1.3.0 (available: v1.8.1) [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+cdb45c87e2cd43495379f7e867e3cc15dcee9f93" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Downloading crates ... [INFO] [stderr] Downloaded strict_encoding v0.9.0 [INFO] [stderr] Downloaded torut v0.2.1 [INFO] [stderr] Downloaded encoding_derive_helpers v0.8.1 [INFO] [stderr] Downloaded parse_arg v1.0.1 [INFO] [stderr] Downloaded stability v0.1.1 [INFO] [stderr] Downloaded amplify_syn v1.1.6 [INFO] [stderr] Downloaded parse_arg v0.1.6 [INFO] [stderr] Downloaded strict_encoding_derive v0.9.0 [INFO] [stderr] Downloaded bitcoin_scripts v0.9.1 [INFO] [stderr] Downloaded amplify v3.14.2 [INFO] [stderr] Downloaded encoding_derive_helpers v0.9.0 [INFO] [stderr] Downloaded lightning_encoding_derive v0.9.1 [INFO] [stderr] Downloaded lnpbp_chain v0.9.0 [INFO] [stderr] Downloaded lightning_encoding v0.9.3 [INFO] [stderr] Downloaded amplify_derive v2.11.3 [INFO] [stderr] Downloaded amplify_num v0.4.1 [INFO] [stderr] Downloaded stringly_conversions v0.1.1 [INFO] [stderr] Downloaded serde_str_helpers v0.1.2 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:7ad1b28ee6f5f7f699f6cf7015098d6ccdd96d6f2d78dd06228f5b4c9faf309c" "/opt/rustwide/cargo-home/bin/cargo" "+cdb45c87e2cd43495379f7e867e3cc15dcee9f93" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] b9a60b616604712cb54b25935a1da2a9a2f1d4dce176ca51fa8892840a187e2f [INFO] running `Command { std: "docker" "start" "-a" "b9a60b616604712cb54b25935a1da2a9a2f1d4dce176ca51fa8892840a187e2f", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "b9a60b616604712cb54b25935a1da2a9a2f1d4dce176ca51fa8892840a187e2f", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "b9a60b616604712cb54b25935a1da2a9a2f1d4dce176ca51fa8892840a187e2f", kill_on_drop: false }` [INFO] [stdout] b9a60b616604712cb54b25935a1da2a9a2f1d4dce176ca51fa8892840a187e2f [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:7ad1b28ee6f5f7f699f6cf7015098d6ccdd96d6f2d78dd06228f5b4c9faf309c" "/opt/rustwide/cargo-home/bin/cargo" "+cdb45c87e2cd43495379f7e867e3cc15dcee9f93" "build" "--frozen" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 107383a2171680606ee0e8621612cc280d29cd5540fbc972ac03e10bd675b1bf [INFO] running `Command { std: "docker" "start" "-a" "107383a2171680606ee0e8621612cc280d29cd5540fbc972ac03e10bd675b1bf", kill_on_drop: false }` [INFO] [stderr] Compiling syn v1.0.109 [INFO] [stderr] Compiling amplify_num v0.4.1 [INFO] [stderr] Compiling cc v1.2.34 [INFO] [stderr] Compiling stringly_conversions v0.1.1 [INFO] [stderr] Compiling secp256k1-sys v0.6.1 [INFO] [stderr] Compiling amplify_syn v1.1.6 [INFO] [stderr] Compiling amplify_derive v2.11.3 [INFO] [stderr] Compiling amplify v3.14.2 [INFO] [stderr] Compiling secp256k1 v0.24.3 [INFO] [stderr] Compiling inet2_addr v0.9.0 (/opt/rustwide/workdir) [INFO] [stdout] error: unexpected `cfg` condition value: `serde_str_helpers` [INFO] [stdout] --> src/inet.rs:84:28 [INFO] [stdout] | [INFO] [stdout] 84 | all(feature = "serde", feature = "serde_str_helpers"), [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [INFO] [stdout] = help: consider adding `serde_str_helpers` 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/lib.rs:18:9 [INFO] [stdout] | [INFO] [stdout] 18 | #![deny(warnings, dead_code, missing_docs)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = note: `#[deny(unexpected_cfgs)]` implied by `#[deny(warnings)]` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `serde_str_helpers` [INFO] [stdout] --> src/inet.rs:93:32 [INFO] [stdout] | [INFO] [stdout] 93 | all(feature = "serde", not(feature = "serde_str_helpers")), [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [INFO] [stdout] = help: consider adding `serde_str_helpers` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `serde_str_helpers` [INFO] [stdout] --> src/inet.rs:318:28 [INFO] [stdout] | [INFO] [stdout] 318 | all(feature = "serde", feature = "serde_str_helpers"), [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [INFO] [stdout] = help: consider adding `serde_str_helpers` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `serde_str_helpers` [INFO] [stdout] --> src/inet.rs:327:32 [INFO] [stdout] | [INFO] [stdout] 327 | all(feature = "serde", not(feature = "serde_str_helpers")), [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [INFO] [stdout] = help: consider adding `serde_str_helpers` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `serde_str_helpers` [INFO] [stdout] --> src/inet.rs:744:28 [INFO] [stdout] | [INFO] [stdout] 744 | all(feature = "serde", feature = "serde_str_helpers"), [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [INFO] [stdout] = help: consider adding `serde_str_helpers` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `serde_str_helpers` [INFO] [stdout] --> src/inet.rs:753:32 [INFO] [stdout] | [INFO] [stdout] 753 | all(feature = "serde", not(feature = "serde_str_helpers")), [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [INFO] [stdout] = help: consider adding `serde_str_helpers` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `serde_str_helpers` [INFO] [stdout] --> src/inet.rs:961:28 [INFO] [stdout] | [INFO] [stdout] 961 | all(feature = "serde", feature = "serde_str_helpers"), [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [INFO] [stdout] = help: consider adding `serde_str_helpers` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `serde_str_helpers` [INFO] [stdout] --> src/inet.rs:970:32 [INFO] [stdout] | [INFO] [stdout] 970 | all(feature = "serde", not(feature = "serde_str_helpers")), [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [INFO] [stdout] = help: consider adding `serde_str_helpers` as a feature in `Cargo.toml` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `alloc` [INFO] [stdout] --> src/inet.rs:258:1 [INFO] [stdout] | [INFO] [stdout] 258 | impl_try_from_stringly_standard!(InetAddr); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_try_from_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_try_from_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_try_from_stringly_standard` which comes from the expansion of the macro `impl_try_from_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `alloc` [INFO] [stdout] --> src/inet.rs:258:1 [INFO] [stdout] | [INFO] [stdout] 258 | impl_try_from_stringly_standard!(InetAddr); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_try_from_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_try_from_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_try_from_stringly_standard` which comes from the expansion of the macro `impl_try_from_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `alloc` [INFO] [stdout] --> src/inet.rs:258:1 [INFO] [stdout] | [INFO] [stdout] 258 | impl_try_from_stringly_standard!(InetAddr); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_try_from_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_try_from_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_try_from_stringly_standard` which comes from the expansion of the macro `impl_try_from_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `alloc` [INFO] [stdout] --> src/inet.rs:258:1 [INFO] [stdout] | [INFO] [stdout] 258 | impl_try_from_stringly_standard!(InetAddr); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_try_from_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_try_from_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_try_from_stringly_standard` which comes from the expansion of the macro `impl_try_from_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `alloc` [INFO] [stdout] --> src/inet.rs:258:1 [INFO] [stdout] | [INFO] [stdout] 258 | impl_try_from_stringly_standard!(InetAddr); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_try_from_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_try_from_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_try_from_stringly_standard` which comes from the expansion of the macro `impl_try_from_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `alloc` [INFO] [stdout] --> src/inet.rs:258:1 [INFO] [stdout] | [INFO] [stdout] 258 | impl_try_from_stringly_standard!(InetAddr); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_try_from_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_try_from_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_try_from_stringly_standard` which comes from the expansion of the macro `impl_try_from_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `serde_str_helpers` [INFO] [stdout] --> src/inet.rs:258:1 [INFO] [stdout] | [INFO] [stdout] 258 | impl_try_from_stringly_standard!(InetAddr); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_try_from_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_try_from_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_try_from_stringly_standard` which comes from the expansion of the macro `impl_try_from_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `alloc` [INFO] [stdout] --> src/inet.rs:260:1 [INFO] [stdout] | [INFO] [stdout] 260 | impl_into_stringly_standard!(InetAddr); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_into_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_into_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_into_stringly_standard` which comes from the expansion of the macro `impl_into_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `alloc` [INFO] [stdout] --> src/inet.rs:260:1 [INFO] [stdout] | [INFO] [stdout] 260 | impl_into_stringly_standard!(InetAddr); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_into_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_into_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_into_stringly_standard` which comes from the expansion of the macro `impl_into_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `alloc` [INFO] [stdout] --> src/inet.rs:260:1 [INFO] [stdout] | [INFO] [stdout] 260 | impl_into_stringly_standard!(InetAddr); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_into_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_into_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_into_stringly_standard` which comes from the expansion of the macro `impl_into_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `alloc` [INFO] [stdout] --> src/inet.rs:260:1 [INFO] [stdout] | [INFO] [stdout] 260 | impl_into_stringly_standard!(InetAddr); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_into_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_into_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_into_stringly_standard` which comes from the expansion of the macro `impl_into_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `alloc` [INFO] [stdout] --> src/inet.rs:629:1 [INFO] [stdout] | [INFO] [stdout] 629 | impl_try_from_stringly_standard!(PartialSocketAddr); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_try_from_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_try_from_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_try_from_stringly_standard` which comes from the expansion of the macro `impl_try_from_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `alloc` [INFO] [stdout] --> src/inet.rs:629:1 [INFO] [stdout] | [INFO] [stdout] 629 | impl_try_from_stringly_standard!(PartialSocketAddr); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_try_from_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_try_from_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_try_from_stringly_standard` which comes from the expansion of the macro `impl_try_from_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `alloc` [INFO] [stdout] --> src/inet.rs:629:1 [INFO] [stdout] | [INFO] [stdout] 629 | impl_try_from_stringly_standard!(PartialSocketAddr); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_try_from_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_try_from_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_try_from_stringly_standard` which comes from the expansion of the macro `impl_try_from_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `alloc` [INFO] [stdout] --> src/inet.rs:629:1 [INFO] [stdout] | [INFO] [stdout] 629 | impl_try_from_stringly_standard!(PartialSocketAddr); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_try_from_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_try_from_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_try_from_stringly_standard` which comes from the expansion of the macro `impl_try_from_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `alloc` [INFO] [stdout] --> src/inet.rs:629:1 [INFO] [stdout] | [INFO] [stdout] 629 | impl_try_from_stringly_standard!(PartialSocketAddr); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_try_from_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_try_from_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_try_from_stringly_standard` which comes from the expansion of the macro `impl_try_from_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `alloc` [INFO] [stdout] --> src/inet.rs:629:1 [INFO] [stdout] | [INFO] [stdout] 629 | impl_try_from_stringly_standard!(PartialSocketAddr); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_try_from_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_try_from_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_try_from_stringly_standard` which comes from the expansion of the macro `impl_try_from_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `serde_str_helpers` [INFO] [stdout] --> src/inet.rs:629:1 [INFO] [stdout] | [INFO] [stdout] 629 | impl_try_from_stringly_standard!(PartialSocketAddr); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_try_from_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_try_from_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_try_from_stringly_standard` which comes from the expansion of the macro `impl_try_from_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `alloc` [INFO] [stdout] --> src/inet.rs:631:1 [INFO] [stdout] | [INFO] [stdout] 631 | impl_into_stringly_standard!(PartialSocketAddr); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_into_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_into_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_into_stringly_standard` which comes from the expansion of the macro `impl_into_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `alloc` [INFO] [stdout] --> src/inet.rs:631:1 [INFO] [stdout] | [INFO] [stdout] 631 | impl_into_stringly_standard!(PartialSocketAddr); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_into_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_into_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_into_stringly_standard` which comes from the expansion of the macro `impl_into_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `alloc` [INFO] [stdout] --> src/inet.rs:631:1 [INFO] [stdout] | [INFO] [stdout] 631 | impl_into_stringly_standard!(PartialSocketAddr); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_into_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_into_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_into_stringly_standard` which comes from the expansion of the macro `impl_into_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `alloc` [INFO] [stdout] --> src/inet.rs:631:1 [INFO] [stdout] | [INFO] [stdout] 631 | impl_into_stringly_standard!(PartialSocketAddr); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_into_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_into_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_into_stringly_standard` which comes from the expansion of the macro `impl_into_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `alloc` [INFO] [stdout] --> src/inet.rs:879:1 [INFO] [stdout] | [INFO] [stdout] 879 | impl_try_from_stringly_standard!(InetSocketAddr); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_try_from_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_try_from_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_try_from_stringly_standard` which comes from the expansion of the macro `impl_try_from_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `alloc` [INFO] [stdout] --> src/inet.rs:879:1 [INFO] [stdout] | [INFO] [stdout] 879 | impl_try_from_stringly_standard!(InetSocketAddr); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_try_from_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_try_from_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_try_from_stringly_standard` which comes from the expansion of the macro `impl_try_from_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `alloc` [INFO] [stdout] --> src/inet.rs:879:1 [INFO] [stdout] | [INFO] [stdout] 879 | impl_try_from_stringly_standard!(InetSocketAddr); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_try_from_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_try_from_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_try_from_stringly_standard` which comes from the expansion of the macro `impl_try_from_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `alloc` [INFO] [stdout] --> src/inet.rs:879:1 [INFO] [stdout] | [INFO] [stdout] 879 | impl_try_from_stringly_standard!(InetSocketAddr); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_try_from_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_try_from_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_try_from_stringly_standard` which comes from the expansion of the macro `impl_try_from_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `alloc` [INFO] [stdout] --> src/inet.rs:879:1 [INFO] [stdout] | [INFO] [stdout] 879 | impl_try_from_stringly_standard!(InetSocketAddr); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_try_from_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_try_from_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_try_from_stringly_standard` which comes from the expansion of the macro `impl_try_from_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `alloc` [INFO] [stdout] --> src/inet.rs:879:1 [INFO] [stdout] | [INFO] [stdout] 879 | impl_try_from_stringly_standard!(InetSocketAddr); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_try_from_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_try_from_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_try_from_stringly_standard` which comes from the expansion of the macro `impl_try_from_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `serde_str_helpers` [INFO] [stdout] --> src/inet.rs:879:1 [INFO] [stdout] | [INFO] [stdout] 879 | impl_try_from_stringly_standard!(InetSocketAddr); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_try_from_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_try_from_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_try_from_stringly_standard` which comes from the expansion of the macro `impl_try_from_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `alloc` [INFO] [stdout] --> src/inet.rs:881:1 [INFO] [stdout] | [INFO] [stdout] 881 | impl_into_stringly_standard!(InetSocketAddr); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_into_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_into_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_into_stringly_standard` which comes from the expansion of the macro `impl_into_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `alloc` [INFO] [stdout] --> src/inet.rs:881:1 [INFO] [stdout] | [INFO] [stdout] 881 | impl_into_stringly_standard!(InetSocketAddr); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_into_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_into_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_into_stringly_standard` which comes from the expansion of the macro `impl_into_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `alloc` [INFO] [stdout] --> src/inet.rs:881:1 [INFO] [stdout] | [INFO] [stdout] 881 | impl_into_stringly_standard!(InetSocketAddr); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_into_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_into_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_into_stringly_standard` which comes from the expansion of the macro `impl_into_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `alloc` [INFO] [stdout] --> src/inet.rs:881:1 [INFO] [stdout] | [INFO] [stdout] 881 | impl_into_stringly_standard!(InetSocketAddr); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_into_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_into_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_into_stringly_standard` which comes from the expansion of the macro `impl_into_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `alloc` [INFO] [stdout] --> src/inet.rs:983:1 [INFO] [stdout] | [INFO] [stdout] 983 | impl_try_from_stringly_standard!(InetSocketAddrExt); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_try_from_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_try_from_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_try_from_stringly_standard` which comes from the expansion of the macro `impl_try_from_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `alloc` [INFO] [stdout] --> src/inet.rs:983:1 [INFO] [stdout] | [INFO] [stdout] 983 | impl_try_from_stringly_standard!(InetSocketAddrExt); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_try_from_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_try_from_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_try_from_stringly_standard` which comes from the expansion of the macro `impl_try_from_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `alloc` [INFO] [stdout] --> src/inet.rs:983:1 [INFO] [stdout] | [INFO] [stdout] 983 | impl_try_from_stringly_standard!(InetSocketAddrExt); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_try_from_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_try_from_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_try_from_stringly_standard` which comes from the expansion of the macro `impl_try_from_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `alloc` [INFO] [stdout] --> src/inet.rs:983:1 [INFO] [stdout] | [INFO] [stdout] 983 | impl_try_from_stringly_standard!(InetSocketAddrExt); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_try_from_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_try_from_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_try_from_stringly_standard` which comes from the expansion of the macro `impl_try_from_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `alloc` [INFO] [stdout] --> src/inet.rs:983:1 [INFO] [stdout] | [INFO] [stdout] 983 | impl_try_from_stringly_standard!(InetSocketAddrExt); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_try_from_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_try_from_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_try_from_stringly_standard` which comes from the expansion of the macro `impl_try_from_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `alloc` [INFO] [stdout] --> src/inet.rs:983:1 [INFO] [stdout] | [INFO] [stdout] 983 | impl_try_from_stringly_standard!(InetSocketAddrExt); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_try_from_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_try_from_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_try_from_stringly_standard` which comes from the expansion of the macro `impl_try_from_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `serde_str_helpers` [INFO] [stdout] --> src/inet.rs:983:1 [INFO] [stdout] | [INFO] [stdout] 983 | impl_try_from_stringly_standard!(InetSocketAddrExt); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_try_from_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_try_from_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_try_from_stringly_standard` which comes from the expansion of the macro `impl_try_from_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `alloc` [INFO] [stdout] --> src/inet.rs:985:1 [INFO] [stdout] | [INFO] [stdout] 985 | impl_into_stringly_standard!(InetSocketAddrExt); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_into_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_into_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_into_stringly_standard` which comes from the expansion of the macro `impl_into_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `alloc` [INFO] [stdout] --> src/inet.rs:985:1 [INFO] [stdout] | [INFO] [stdout] 985 | impl_into_stringly_standard!(InetSocketAddrExt); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_into_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_into_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_into_stringly_standard` which comes from the expansion of the macro `impl_into_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `alloc` [INFO] [stdout] --> src/inet.rs:985:1 [INFO] [stdout] | [INFO] [stdout] 985 | impl_into_stringly_standard!(InetSocketAddrExt); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_into_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_into_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_into_stringly_standard` which comes from the expansion of the macro `impl_into_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: unexpected `cfg` condition value: `alloc` [INFO] [stdout] --> src/inet.rs:985:1 [INFO] [stdout] | [INFO] [stdout] 985 | impl_into_stringly_standard!(InetSocketAddrExt); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `all`, `default`, `keygen`, `lightning_encoding`, `parse_arg`, `serde`, `serde_crate`, `serde_json`, `serde_yaml`, `strict_encoding`, `stringly_conversions`, `stringly_conversions_crate`, `toml`, `tor`, and `torut` [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 `$crate::impl_into_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_into_stringly_standard` may come from an old version of the `stringly_conversions` crate, try updating your dependency with `cargo update -p stringly_conversions` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this error originates in the macro `$crate::impl_into_stringly_standard` which comes from the expansion of the macro `impl_into_stringly_standard` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] error: could not compile `inet2_addr` (lib) due to 52 previous errors [INFO] running `Command { std: "docker" "inspect" "107383a2171680606ee0e8621612cc280d29cd5540fbc972ac03e10bd675b1bf", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "107383a2171680606ee0e8621612cc280d29cd5540fbc972ac03e10bd675b1bf", kill_on_drop: false }` [INFO] [stdout] 107383a2171680606ee0e8621612cc280d29cd5540fbc972ac03e10bd675b1bf