# rustc version rustc 1.98.0-nightly (57d06900f 2026-05-27)
# docs.rs version docsrs 0.0.0 (f16e33f3e6ac9fc9e4413728c5dd1b2ba1c6b799 2026-05-23 )
# build log [INFO] running `Command { std: "docker" "exec" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "DOCS_RS=1" "-w" "/opt/rustwide/workdir" "--user" "1001:1001" "687929b5b5b746384298016783830a22704b28ae0281c8b49e4ef2dd31b94d50" "/opt/rustwide/cargo-home/bin/cargo" "+nightly" "rustdoc" "--lib" "-Zrustdoc-map" "--config" "build.rustdocflags=[\"--cfg\", \"docsrs\", \"-Z\", \"unstable-options\", \"--emit=invocation-specific\", \"--resource-suffix\", \"-20260527-1.98.0-nightly-57d06900f\", \"--static-root-path\", \"/-/rustdoc.static/\", \"--cap-lints\", \"warn\", \"--extern-html-root-takes-precedence\"]" "--offline" "-Zunstable-options" "--config=doc.extern-map.registries.crates-io=\"https://docs.rs/{pkg_name}/{version}/x86_64-unknown-linux-gnu\"" "-Zrustdoc-scrape-examples" "-j6" "--target" "x86_64-unknown-linux-gnu", kill_on_drop: false }` [INFO] [stderr] warning: target filter specified, but no targets matched; this is a no-op [INFO] [stderr] Documenting inet2_addr v0.9.0 (/opt/rustwide/workdir) [INFO] [stderr] warning: unexpected `cfg` condition value: `serde_str_helpers` [INFO] [stderr] --> src/inet.rs:84:28 [INFO] [stderr] | [INFO] [stderr] 84 | all(feature = "serde", feature = "serde_str_helpers"), [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = 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] [stderr] = help: consider adding `serde_str_helpers` as a feature in `Cargo.toml` [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] note: the lint level is defined here [INFO] [stderr] --> src/lib.rs:18:9 [INFO] [stderr] | [INFO] [stderr] 18 | #![deny(warnings, dead_code, missing_docs)] [INFO] [stderr] | ^^^^^^^^ [INFO] [stderr] = note: `#[warn(unexpected_cfgs)]` implied by `#[warn(warnings)]` [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `serde_str_helpers` [INFO] [stderr] --> src/inet.rs:93:32 [INFO] [stderr] | [INFO] [stderr] 93 | all(feature = "serde", not(feature = "serde_str_helpers")), [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = 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] [stderr] = help: consider adding `serde_str_helpers` as a feature in `Cargo.toml` [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `serde_str_helpers` [INFO] [stderr] --> src/inet.rs:318:28 [INFO] [stderr] | [INFO] [stderr] 318 | all(feature = "serde", feature = "serde_str_helpers"), [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = 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] [stderr] = help: consider adding `serde_str_helpers` as a feature in `Cargo.toml` [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `serde_str_helpers` [INFO] [stderr] --> src/inet.rs:327:32 [INFO] [stderr] | [INFO] [stderr] 327 | all(feature = "serde", not(feature = "serde_str_helpers")), [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = 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] [stderr] = help: consider adding `serde_str_helpers` as a feature in `Cargo.toml` [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `serde_str_helpers` [INFO] [stderr] --> src/inet.rs:744:28 [INFO] [stderr] | [INFO] [stderr] 744 | all(feature = "serde", feature = "serde_str_helpers"), [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = 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] [stderr] = help: consider adding `serde_str_helpers` as a feature in `Cargo.toml` [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `serde_str_helpers` [INFO] [stderr] --> src/inet.rs:753:32 [INFO] [stderr] | [INFO] [stderr] 753 | all(feature = "serde", not(feature = "serde_str_helpers")), [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = 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] [stderr] = help: consider adding `serde_str_helpers` as a feature in `Cargo.toml` [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `serde_str_helpers` [INFO] [stderr] --> src/inet.rs:961:28 [INFO] [stderr] | [INFO] [stderr] 961 | all(feature = "serde", feature = "serde_str_helpers"), [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = 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] [stderr] = help: consider adding `serde_str_helpers` as a feature in `Cargo.toml` [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `serde_str_helpers` [INFO] [stderr] --> src/inet.rs:970:32 [INFO] [stderr] | [INFO] [stderr] 970 | all(feature = "serde", not(feature = "serde_str_helpers")), [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = 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] [stderr] = help: consider adding `serde_str_helpers` as a feature in `Cargo.toml` [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `alloc` [INFO] [stderr] --> src/inet.rs:258:1 [INFO] [stderr] | [INFO] [stderr] 258 | impl_try_from_stringly_standard!(InetAddr); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = 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] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::impl_try_from_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning 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] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `serde_str_helpers` [INFO] [stderr] --> src/inet.rs:258:1 [INFO] [stderr] | [INFO] [stderr] 258 | impl_try_from_stringly_standard!(InetAddr); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = 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] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::impl_try_from_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning 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] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `alloc` [INFO] [stderr] --> src/inet.rs:260:1 [INFO] [stderr] | [INFO] [stderr] 260 | impl_into_stringly_standard!(InetAddr); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = 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] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::impl_into_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning 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] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `alloc` [INFO] [stderr] --> src/inet.rs:629:1 [INFO] [stderr] | [INFO] [stderr] 629 | impl_try_from_stringly_standard!(PartialSocketAddr); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = 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] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::impl_try_from_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning 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] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `serde_str_helpers` [INFO] [stderr] --> src/inet.rs:629:1 [INFO] [stderr] | [INFO] [stderr] 629 | impl_try_from_stringly_standard!(PartialSocketAddr); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = 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] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::impl_try_from_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning 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] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `alloc` [INFO] [stderr] --> src/inet.rs:631:1 [INFO] [stderr] | [INFO] [stderr] 631 | impl_into_stringly_standard!(PartialSocketAddr); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = 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] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::impl_into_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning 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] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `alloc` [INFO] [stderr] --> src/inet.rs:879:1 [INFO] [stderr] | [INFO] [stderr] 879 | impl_try_from_stringly_standard!(InetSocketAddr); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = 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] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::impl_try_from_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning 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] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `serde_str_helpers` [INFO] [stderr] --> src/inet.rs:879:1 [INFO] [stderr] | [INFO] [stderr] 879 | impl_try_from_stringly_standard!(InetSocketAddr); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = 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] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::impl_try_from_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning 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] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `alloc` [INFO] [stderr] --> src/inet.rs:881:1 [INFO] [stderr] | [INFO] [stderr] 881 | impl_into_stringly_standard!(InetSocketAddr); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = 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] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::impl_into_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning 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] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `alloc` [INFO] [stderr] --> src/inet.rs:983:1 [INFO] [stderr] | [INFO] [stderr] 983 | impl_try_from_stringly_standard!(InetSocketAddrExt); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = 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] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::impl_try_from_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning 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] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `serde_str_helpers` [INFO] [stderr] --> src/inet.rs:983:1 [INFO] [stderr] | [INFO] [stderr] 983 | impl_try_from_stringly_standard!(InetSocketAddrExt); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = 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] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::impl_try_from_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning 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] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `alloc` [INFO] [stderr] --> src/inet.rs:985:1 [INFO] [stderr] | [INFO] [stderr] 985 | impl_into_stringly_standard!(InetSocketAddrExt); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = 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] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::impl_into_stringly_standard` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration [INFO] [stderr] = note: this warning 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] [stderr] [INFO] [stderr] warning: unresolved link to `TorPublicKeyV3` [INFO] [stderr] --> src/inet.rs:76:24 [INFO] [stderr] | [INFO] [stderr] 76 | /// NB: we are using [`TorPublicKeyV3`] instead of `OnionAddressV3`, since [INFO] [stderr] | ^^^^^^^^^^^^^^ no item named `TorPublicKeyV3` in scope [INFO] [stderr] | [INFO] [stderr] = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]` [INFO] [stderr] = note: `#[warn(rustdoc::broken_intra_doc_links)]` implied by `#[warn(warnings)]` [INFO] [stderr] [INFO] [stderr] warning: unresolved link to `TorPublicKeyV3` [INFO] [stderr] --> src/inet.rs:78:26 [INFO] [stderr] | [INFO] [stderr] 78 | /// reconstructed from [`TorPublicKeyV3`]. The 2-byte checksum in [INFO] [stderr] | ^^^^^^^^^^^^^^ no item named `TorPublicKeyV3` in scope [INFO] [stderr] | [INFO] [stderr] = help: to escape `[` and `]` characters, add '\' before them like `\[` or `\]` [INFO] [stderr] [INFO] [stderr] warning: `inet2_addr` (lib doc) generated 54 warnings (32 duplicates) [INFO] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.52s [INFO] [stderr] Generated /opt/rustwide/target/x86_64-unknown-linux-gnu/doc/inet2_addr/index.html [INFO] running `Command { std: "docker" "inspect" "687929b5b5b746384298016783830a22704b28ae0281c8b49e4ef2dd31b94d50", kill_on_drop: false }`