# rustc version rustc 1.100.0-nightly (0dfb098f3 2026-08-31)
# docs.rs version docsrs 0.0.0 (6c3c2ab33f39d2284fd26cea84fae0598b4cbd55 2026-08-24 )
# 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" "73a3f572fc84ef772341dd6f3f3dfb94fa7e3a54fe67171e344278719ca62c19" "/opt/rustwide/cargo-home/bin/cargo" "+nightly" "rustdoc" "--lib" "-Zrustdoc-map" "--all-features" "--config" "build.rustdocflags=[\"--cfg\", \"docsrs\", \"-Z\", \"unstable-options\", \"--emit=html-non-static-files\", \"--resource-suffix\", \"-20260831-1.100.0-nightly-0dfb098f3\", \"--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\"" "-j11" "--target" "x86_64-unknown-linux-gnu" "-Zrustdoc-scrape-examples", kill_on_drop: false }` [INFO] [stderr] warning: target filter specified, but no targets matched; this is a no-op [INFO] [stderr] Documenting rocket v0.5.1 (/opt/rustwide/workdir) [INFO] [stderr] warning: unexpected `cfg` condition name: `nightly` [INFO] [stderr] --> src/lib.rs:6:13 [INFO] [stderr] | [INFO] [stderr] 6 | #![cfg_attr(nightly, feature(doc_cfg))] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: expected names are: `docsrs`, `feature`, and `test` and 34 more [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [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: `#[warn(unexpected_cfgs)]` on by default [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `nightly` [INFO] [stderr] --> src/lib.rs:7:13 [INFO] [stderr] | [INFO] [stderr] 7 | #![cfg_attr(nightly, feature(decl_macro))] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [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 name: `nightly` [INFO] [stderr] --> src/lib.rs:167:12 [INFO] [stderr] | [INFO] [stderr] 167 | #[cfg_attr(nightly, doc(cfg(feature = "mtls")))] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [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 name: `nightly` [INFO] [stderr] --> src/outcome.rs:630:1 [INFO] [stderr] | [INFO] [stderr] 630 | / crate::export! { [INFO] [stderr] 631 | | /// Unwraps a [`Success`](Outcome::Success) or propagates a `Forward` or [INFO] [stderr] 632 | | /// `Error` by returning early. [INFO] [stderr] 633 | | /// [INFO] [stderr] ... | [INFO] [stderr] 711 | | } [INFO] [stderr] | |_^ [INFO] [stderr] | [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::export` 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::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `nightly` [INFO] [stderr] --> src/local/request.rs:191:16 [INFO] [stderr] | [INFO] [stderr] 191 | #[cfg_attr(nightly, doc(cfg(feature = "secrets")))] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/local/asynchronous/request.rs:122:5 [INFO] [stderr] | [INFO] [stderr] 122 | / pub_request_impl!("# use rocket::local::asynchronous::Client;\n\ [INFO] [stderr] 123 | | use rocket::local::asynchronous::LocalRequest;" async await); [INFO] [stderr] | |____________________________________________________________________- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [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 `pub_request_impl` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `nightly` [INFO] [stderr] --> src/local/request.rs:229:16 [INFO] [stderr] | [INFO] [stderr] 229 | #[cfg_attr(nightly, doc(cfg(feature = "mtls")))] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/local/asynchronous/request.rs:122:5 [INFO] [stderr] | [INFO] [stderr] 122 | / pub_request_impl!("# use rocket::local::asynchronous::Client;\n\ [INFO] [stderr] 123 | | use rocket::local::asynchronous::LocalRequest;" async await); [INFO] [stderr] | |____________________________________________________________________- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [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 `pub_request_impl` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `nightly` [INFO] [stderr] --> src/local/request.rs:293:16 [INFO] [stderr] | [INFO] [stderr] 293 | #[cfg_attr(nightly, doc(cfg(feature = "json")))] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/local/asynchronous/request.rs:122:5 [INFO] [stderr] | [INFO] [stderr] 122 | / pub_request_impl!("# use rocket::local::asynchronous::Client;\n\ [INFO] [stderr] 123 | | use rocket::local::asynchronous::LocalRequest;" async await); [INFO] [stderr] | |____________________________________________________________________- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [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 `pub_request_impl` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `nightly` [INFO] [stderr] --> src/local/request.rs:327:16 [INFO] [stderr] | [INFO] [stderr] 327 | #[cfg_attr(nightly, doc(cfg(feature = "msgpack")))] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/local/asynchronous/request.rs:122:5 [INFO] [stderr] | [INFO] [stderr] 122 | / pub_request_impl!("# use rocket::local::asynchronous::Client;\n\ [INFO] [stderr] 123 | | use rocket::local::asynchronous::LocalRequest;" async await); [INFO] [stderr] | |____________________________________________________________________- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [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 `pub_request_impl` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `nightly` [INFO] [stderr] --> src/local/response.rs:136:16 [INFO] [stderr] | [INFO] [stderr] 136 | #[cfg_attr(nightly, doc(cfg(feature = "json")))] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/local/asynchronous/response.rs:189:5 [INFO] [stderr] | [INFO] [stderr] 189 | / pub_response_impl!("# use rocket::local::asynchronous::Client;\n\ [INFO] [stderr] 190 | | use rocket::local::asynchronous::LocalResponse;" async await); [INFO] [stderr] | |_____________________________________________________________________- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [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 `pub_response_impl` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `nightly` [INFO] [stderr] --> src/local/response.rs:172:16 [INFO] [stderr] | [INFO] [stderr] 172 | #[cfg_attr(nightly, doc(cfg(feature = "msgpack")))] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/local/asynchronous/response.rs:189:5 [INFO] [stderr] | [INFO] [stderr] 189 | / pub_response_impl!("# use rocket::local::asynchronous::Client;\n\ [INFO] [stderr] 190 | | use rocket::local::asynchronous::LocalResponse;" async await); [INFO] [stderr] | |_____________________________________________________________________- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [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 `pub_response_impl` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `nightly` [INFO] [stderr] --> src/local/request.rs:191:16 [INFO] [stderr] | [INFO] [stderr] 191 | #[cfg_attr(nightly, doc(cfg(feature = "secrets")))] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/local/blocking/request.rs:64:5 [INFO] [stderr] | [INFO] [stderr] 64 | / pub_request_impl!("# use rocket::local::blocking::Client;\n\ [INFO] [stderr] 65 | | use rocket::local::blocking::LocalRequest;"); [INFO] [stderr] | |____________________________________________________- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [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 `pub_request_impl` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `nightly` [INFO] [stderr] --> src/local/request.rs:229:16 [INFO] [stderr] | [INFO] [stderr] 229 | #[cfg_attr(nightly, doc(cfg(feature = "mtls")))] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/local/blocking/request.rs:64:5 [INFO] [stderr] | [INFO] [stderr] 64 | / pub_request_impl!("# use rocket::local::blocking::Client;\n\ [INFO] [stderr] 65 | | use rocket::local::blocking::LocalRequest;"); [INFO] [stderr] | |____________________________________________________- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [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 `pub_request_impl` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `nightly` [INFO] [stderr] --> src/local/request.rs:293:16 [INFO] [stderr] | [INFO] [stderr] 293 | #[cfg_attr(nightly, doc(cfg(feature = "json")))] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/local/blocking/request.rs:64:5 [INFO] [stderr] | [INFO] [stderr] 64 | / pub_request_impl!("# use rocket::local::blocking::Client;\n\ [INFO] [stderr] 65 | | use rocket::local::blocking::LocalRequest;"); [INFO] [stderr] | |____________________________________________________- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [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 `pub_request_impl` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `nightly` [INFO] [stderr] --> src/local/request.rs:327:16 [INFO] [stderr] | [INFO] [stderr] 327 | #[cfg_attr(nightly, doc(cfg(feature = "msgpack")))] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/local/blocking/request.rs:64:5 [INFO] [stderr] | [INFO] [stderr] 64 | / pub_request_impl!("# use rocket::local::blocking::Client;\n\ [INFO] [stderr] 65 | | use rocket::local::blocking::LocalRequest;"); [INFO] [stderr] | |____________________________________________________- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [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 `pub_request_impl` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `nightly` [INFO] [stderr] --> src/local/response.rs:136:16 [INFO] [stderr] | [INFO] [stderr] 136 | #[cfg_attr(nightly, doc(cfg(feature = "json")))] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/local/blocking/response.rs:89:5 [INFO] [stderr] | [INFO] [stderr] 89 | / pub_response_impl!("# use rocket::local::blocking::Client;\n\ [INFO] [stderr] 90 | | use rocket::local::blocking::LocalResponse;"); [INFO] [stderr] | |_____________________________________________________- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [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 `pub_response_impl` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `nightly` [INFO] [stderr] --> src/local/response.rs:172:16 [INFO] [stderr] | [INFO] [stderr] 172 | #[cfg_attr(nightly, doc(cfg(feature = "msgpack")))] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/local/blocking/response.rs:89:5 [INFO] [stderr] | [INFO] [stderr] 89 | / pub_response_impl!("# use rocket::local::blocking::Client;\n\ [INFO] [stderr] 90 | | use rocket::local::blocking::LocalResponse;"); [INFO] [stderr] | |_____________________________________________________- in this macro invocation [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [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 `pub_response_impl` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `nightly` [INFO] [stderr] --> src/request/mod.rs:19:1 [INFO] [stderr] | [INFO] [stderr] 19 | / crate::export! { [INFO] [stderr] 20 | | /// Store and immediately retrieve a vector-like value `$v` (`String` or [INFO] [stderr] 21 | | /// `Vec<T>`) in `$request`'s local cache using a locally generated [INFO] [stderr] 22 | | /// anonymous type to avoid type conflicts. [INFO] [stderr] ... | [INFO] [stderr] 67 | | } [INFO] [stderr] | |_^ [INFO] [stderr] | [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::export` 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::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `nightly` [INFO] [stderr] --> src/request/mod.rs:69:1 [INFO] [stderr] | [INFO] [stderr] 69 | / crate::export! { [INFO] [stderr] 70 | | /// Store and immediately retrieve a value `$v` in `$request`'s local cache [INFO] [stderr] 71 | | /// using a locally generated anonymous type to avoid type conflicts. [INFO] [stderr] 72 | | /// [INFO] [stderr] ... | [INFO] [stderr] 113 | | } [INFO] [stderr] | |_^ [INFO] [stderr] | [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::export` 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::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `nightly` [INFO] [stderr] --> src/response/stream/mod.rs:206:1 [INFO] [stderr] | [INFO] [stderr] 206 | / crate::export! { [INFO] [stderr] 207 | | /// Retrofitted support for [`Stream`]s with `yield`, `for await` syntax. [INFO] [stderr] 208 | | /// [INFO] [stderr] 209 | | /// [`Stream`]: https://docs.rs/futures/0.3/futures/stream/trait.Stream.html [INFO] [stderr] ... | [INFO] [stderr] 288 | | } [INFO] [stderr] | |_^ [INFO] [stderr] | [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::export` 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::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `nightly` [INFO] [stderr] --> src/response/stream/reader.rs:196:1 [INFO] [stderr] | [INFO] [stderr] 196 | / crate::export! { [INFO] [stderr] 197 | | /// Type and stream expression macro for [`struct@ReaderStream`]. [INFO] [stderr] 198 | | /// [INFO] [stderr] 199 | | /// See [`stream!`](crate::response::stream::stream) for the syntax [INFO] [stderr] ... | [INFO] [stderr] 207 | | } [INFO] [stderr] | |_^ [INFO] [stderr] | [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::export` 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::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `nightly` [INFO] [stderr] --> src/response/stream/bytes.rs:75:1 [INFO] [stderr] | [INFO] [stderr] 75 | / crate::export! { [INFO] [stderr] 76 | | /// Type and stream expression macro for [`struct@ByteStream`]. [INFO] [stderr] 77 | | /// [INFO] [stderr] 78 | | /// See [`stream!`](crate::response::stream::stream) for the syntax [INFO] [stderr] ... | [INFO] [stderr] 86 | | } [INFO] [stderr] | |_^ [INFO] [stderr] | [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::export` 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::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `nightly` [INFO] [stderr] --> src/response/stream/text.rs:85:1 [INFO] [stderr] | [INFO] [stderr] 85 | / crate::export! { [INFO] [stderr] 86 | | /// Type and stream expression macro for [`struct@TextStream`]. [INFO] [stderr] 87 | | /// [INFO] [stderr] 88 | | /// See [`stream!`](crate::response::stream::stream) for the syntax [INFO] [stderr] ... | [INFO] [stderr] 96 | | } [INFO] [stderr] | |_^ [INFO] [stderr] | [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::export` 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::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `nightly` [INFO] [stderr] --> src/response/stream/sse.rs:588:1 [INFO] [stderr] | [INFO] [stderr] 588 | / crate::export! { [INFO] [stderr] 589 | | /// Type and stream expression macro for [`struct@EventStream`]. [INFO] [stderr] 590 | | /// [INFO] [stderr] 591 | | /// See [`stream!`](crate::response::stream::stream) for the syntax [INFO] [stderr] ... | [INFO] [stderr] 602 | | } [INFO] [stderr] | |_^ [INFO] [stderr] | [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::export` 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::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `nightly` [INFO] [stderr] --> src/response/stream/sse.rs:163:16 [INFO] [stderr] | [INFO] [stderr] 163 | #[cfg_attr(nightly, doc(cfg(feature = "json")))] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [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 name: `nightly` [INFO] [stderr] --> src/config/config.rs:105:16 [INFO] [stderr] | [INFO] [stderr] 105 | #[cfg_attr(nightly, doc(cfg(feature = "tls")))] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [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 name: `nightly` [INFO] [stderr] --> src/config/config.rs:112:16 [INFO] [stderr] | [INFO] [stderr] 112 | #[cfg_attr(nightly, doc(cfg(feature = "secrets")))] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [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 name: `nightly` [INFO] [stderr] --> src/config/shutdown.rs:21:12 [INFO] [stderr] | [INFO] [stderr] 21 | #[cfg_attr(nightly, doc(cfg(unix)))] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [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 name: `nightly` [INFO] [stderr] --> src/config/shutdown.rs:218:16 [INFO] [stderr] | [INFO] [stderr] 218 | #[cfg_attr(nightly, doc(cfg(unix)))] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [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 name: `nightly` [INFO] [stderr] --> src/config/tls.rs:80:12 [INFO] [stderr] | [INFO] [stderr] 80 | #[cfg_attr(nightly, doc(cfg(feature = "tls")))] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [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 name: `nightly` [INFO] [stderr] --> src/config/tls.rs:162:12 [INFO] [stderr] | [INFO] [stderr] 162 | #[cfg_attr(nightly, doc(cfg(feature = "mtls")))] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [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 name: `nightly` [INFO] [stderr] --> src/config/tls.rs:183:12 [INFO] [stderr] | [INFO] [stderr] 183 | #[cfg_attr(nightly, doc(cfg(feature = "tls")))] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [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 name: `nightly` [INFO] [stderr] --> src/config/tls.rs:97:16 [INFO] [stderr] | [INFO] [stderr] 97 | #[cfg_attr(nightly, doc(cfg(feature = "mtls")))] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [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 name: `nightly` [INFO] [stderr] --> src/config/tls.rs:415:16 [INFO] [stderr] | [INFO] [stderr] 415 | #[cfg_attr(nightly, doc(cfg(feature = "mtls")))] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [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 name: `nightly` [INFO] [stderr] --> src/config/tls.rs:535:16 [INFO] [stderr] | [INFO] [stderr] 535 | #[cfg_attr(nightly, doc(cfg(feature = "mtls")))] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [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 name: `nightly` [INFO] [stderr] --> src/config/secret_key.rs:77:12 [INFO] [stderr] | [INFO] [stderr] 77 | #[cfg_attr(nightly, doc(cfg(feature = "secrets")))] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [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 name: `nightly` [INFO] [stderr] --> src/form/validate.rs:90:1 [INFO] [stderr] | [INFO] [stderr] 90 | / crate::export! { [INFO] [stderr] 91 | | /// A helper macro for custom validation error messages. [INFO] [stderr] 92 | | /// [INFO] [stderr] 93 | | /// The macro works similar to [`std::format!`]. It generates a form [INFO] [stderr] ... | [INFO] [stderr] 158 | | } [INFO] [stderr] | |_^ [INFO] [stderr] | [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::export` 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::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `nightly` [INFO] [stderr] --> src/serde/mod.rs:46:12 [INFO] [stderr] | [INFO] [stderr] 46 | #[cfg_attr(nightly, doc(cfg(feature = "json")))] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [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 name: `nightly` [INFO] [stderr] --> src/serde/mod.rs:50:12 [INFO] [stderr] | [INFO] [stderr] 50 | #[cfg_attr(nightly, doc(cfg(feature = "msgpack")))] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [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 name: `nightly` [INFO] [stderr] --> src/serde/mod.rs:54:12 [INFO] [stderr] | [INFO] [stderr] 54 | #[cfg_attr(nightly, doc(cfg(feature = "uuid")))] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [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 name: `nightly` [INFO] [stderr] --> src/serde/json.rs:306:1 [INFO] [stderr] | [INFO] [stderr] 306 | / crate::export! { [INFO] [stderr] 307 | | /// A macro to create ad-hoc JSON serializable values using JSON syntax. [INFO] [stderr] 308 | | /// [INFO] [stderr] 309 | | /// The return type of a `json!` invocation is [`Value`](Value). A value [INFO] [stderr] ... | [INFO] [stderr] 389 | | } [INFO] [stderr] | |_^ [INFO] [stderr] | [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::export` 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::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `nightly` [INFO] [stderr] --> src/fs/server.rs:405:1 [INFO] [stderr] | [INFO] [stderr] 405 | / crate::export! { [INFO] [stderr] 406 | | /// Generates a crate-relative version of a path. [INFO] [stderr] 407 | | /// [INFO] [stderr] 408 | | /// This macro is primarily intended for use with [`FileServer`] to serve [INFO] [stderr] ... | [INFO] [stderr] 453 | | } [INFO] [stderr] | |_^ [INFO] [stderr] | [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::export` 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::export` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `broken_fmt` [INFO] [stderr] --> src/server.rs:76:15 [INFO] [stderr] | [INFO] [stderr] 76 | #[cfg(not(broken_fmt))] [INFO] [stderr] | ^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(broken_fmt)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(broken_fmt)");` to the top of the `build.rs` [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 name: `broken_fmt` [INFO] [stderr] --> src/server.rs:165:19 [INFO] [stderr] | [INFO] [stderr] 165 | #[cfg(not(broken_fmt))] [INFO] [stderr] | ^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(broken_fmt)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(broken_fmt)");` to the top of the `build.rs` [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 name: `nightly` [INFO] [stderr] --> src/cookies.rs:237:16 [INFO] [stderr] | [INFO] [stderr] 237 | #[cfg_attr(nightly, doc(cfg(feature = "secrets")))] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [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 name: `nightly` [INFO] [stderr] --> src/cookies.rs:346:16 [INFO] [stderr] | [INFO] [stderr] 346 | #[cfg_attr(nightly, doc(cfg(feature = "secrets")))] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [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 name: `nightly` [INFO] [stderr] --> src/cookies.rs:432:16 [INFO] [stderr] | [INFO] [stderr] 432 | #[cfg_attr(nightly, doc(cfg(feature = "secrets")))] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [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 name: `nightly` [INFO] [stderr] --> src/cookies.rs:505:16 [INFO] [stderr] | [INFO] [stderr] 505 | #[cfg_attr(nightly, doc(cfg(feature = "secrets")))] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [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 name: `nightly` [INFO] [stderr] --> src/cookies.rs:559:16 [INFO] [stderr] | [INFO] [stderr] 559 | #[cfg_attr(nightly, doc(cfg(feature = "secrets")))] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: consider using a Cargo feature instead [INFO] [stderr] = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint: [INFO] [stderr] [lints.rust] [INFO] [stderr] unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] } [INFO] [stderr] = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs` [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: redundant explicit link target [INFO] [stderr] --> src/outcome.rs:631:5 [INFO] [stderr] | [INFO] [stderr] 631 | / /// Unwraps a [`Success`](Outcome::Success) or propagates a `Forward` or [INFO] [stderr] 632 | | /// `Error` by returning early. [INFO] [stderr] 633 | | /// [INFO] [stderr] 634 | | /// # Syntax [INFO] [stderr] ... | [INFO] [stderr] 698 | | /// } [INFO] [stderr] 699 | | /// ``` [INFO] [stderr] | |___________^ explicit target `Outcome::Success` is redundant because label `Success` resolves to same destination [INFO] [stderr] | [INFO] [stderr] = note: when a link's destination is not specified, [INFO] [stderr] the label is used to resolve intra-doc links [INFO] [stderr] = note: `#[warn(rustdoc::redundant_explicit_links)]` on by default [INFO] [stderr] [INFO] [stderr] warning: redundant explicit link target [INFO] [stderr] --> src/outcome.rs:649:18 [INFO] [stderr] | [INFO] [stderr] 649 | /// [`From`](std::convert::From), allowing for the conversion between [INFO] [stderr] | ------ ^^^^^^^^^^^^^^^^^^ explicit target is redundant [INFO] [stderr] | | [INFO] [stderr] | because label contains path that resolves to same destination [INFO] [stderr] | [INFO] [stderr] = note: when a link's destination is not specified, [INFO] [stderr] the label is used to resolve intra-doc links [INFO] [stderr] help: remove explicit link target [INFO] [stderr] | [INFO] [stderr] 649 - /// [`From`](std::convert::From), allowing for the conversion between [INFO] [stderr] 649 + /// [`From`], allowing for the conversion between [INFO] [stderr] | [INFO] [stderr] [INFO] [stderr] warning: redundant explicit link target [INFO] [stderr] --> src/serde/json.rs:307:5 [INFO] [stderr] | [INFO] [stderr] 307 | / /// A macro to create ad-hoc JSON serializable values using JSON syntax. [INFO] [stderr] 308 | | /// [INFO] [stderr] 309 | | /// The return type of a `json!` invocation is [`Value`](Value). A value [INFO] [stderr] 310 | | /// created with this macro can be returned from a handler as follows: [INFO] [stderr] ... | [INFO] [stderr] 384 | | /// ]); [INFO] [stderr] 385 | | /// ``` [INFO] [stderr] | |___________^ explicit target `Value` is redundant because label `Value` resolves to same destination [INFO] [stderr] | [INFO] [stderr] = note: when a link's destination is not specified, [INFO] [stderr] the label is used to resolve intra-doc links [INFO] [stderr] [INFO] [stderr] warning: redundant explicit link target [INFO] [stderr] --> src/serde/json.rs:325:27 [INFO] [stderr] | [INFO] [stderr] 325 | /// The [`Responder`](crate::response::Responder) implementation for [INFO] [stderr] | ----------- ^^^^^^^^^^^^^^^^^^^^^^^^^^ explicit target is redundant [INFO] [stderr] | | [INFO] [stderr] | because label contains path that resolves to same destination [INFO] [stderr] | [INFO] [stderr] = note: when a link's destination is not specified, [INFO] [stderr] the label is used to resolve intra-doc links [INFO] [stderr] help: remove explicit link target [INFO] [stderr] | [INFO] [stderr] 325 - /// The [`Responder`](crate::response::Responder) implementation for [INFO] [stderr] 325 + /// The [`Responder`] implementation for [INFO] [stderr] | [INFO] [stderr] [INFO] [stderr] warning: `rocket` (lib doc) generated 52 warnings [INFO] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 5.41s [INFO] [stderr] Generated /opt/rustwide/target/x86_64-unknown-linux-gnu/doc/rocket/index.html [INFO] running `Command { std: "docker" "inspect" "73a3f572fc84ef772341dd6f3f3dfb94fa7e3a54fe67171e344278719ca62c19", kill_on_drop: false }`