[INFO] fetching crate rocket 0.5.1...
[INFO] checking rocket-0.5.1 against try#93086cfebfccb79083c59d0d3b2052944bba643c for pr-146440-1
[INFO] extracting crate rocket 0.5.1 into /workspace/builds/worker-3-tc2/source
[INFO] started tweaking crates.io crate rocket 0.5.1
[INFO] removed 0 missing tests
[INFO] finished tweaking crates.io crate rocket 0.5.1
[INFO] tweaked toml for crates.io crate rocket 0.5.1 written to /workspace/builds/worker-3-tc2/source/Cargo.toml
[INFO] validating manifest of crates.io crate rocket 0.5.1 on toolchain 93086cfebfccb79083c59d0d3b2052944bba643c
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+93086cfebfccb79083c59d0d3b2052944bba643c" "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" "+93086cfebfccb79083c59d0d3b2052944bba643c" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]      Locking 240 packages to latest compatible versions
[INFO] [stderr]       Adding atomic v0.5.3 (available: v0.6.1)
[INFO] [stderr]       Adding generic-array v0.14.7 (available: v0.14.9)
[INFO] [stderr]       Adding rand v0.8.6 (available: v0.10.1)
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+93086cfebfccb79083c59d0d3b2052944bba643c" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:d429b63d4308055ea97f60fb1d3dfca48854a00942f1bd2ad806beaf015945ec" "/opt/rustwide/cargo-home/bin/cargo" "+93086cfebfccb79083c59d0d3b2052944bba643c" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] c9f75fbdc01bc1e74595235c1f6b03856f32c0ca44c93d5a4cb82b06a709238c
[INFO] running `Command { std: "docker" "start" "-a" "c9f75fbdc01bc1e74595235c1f6b03856f32c0ca44c93d5a4cb82b06a709238c", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "c9f75fbdc01bc1e74595235c1f6b03856f32c0ca44c93d5a4cb82b06a709238c", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "c9f75fbdc01bc1e74595235c1f6b03856f32c0ca44c93d5a4cb82b06a709238c", kill_on_drop: false }`
[INFO] [stdout] c9f75fbdc01bc1e74595235c1f6b03856f32c0ca44c93d5a4cb82b06a709238c
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:d429b63d4308055ea97f60fb1d3dfca48854a00942f1bd2ad806beaf015945ec" "/opt/rustwide/cargo-home/bin/cargo" "+93086cfebfccb79083c59d0d3b2052944bba643c" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] ee9d037558ed01584b95df623d6daf0478829a971e5f91bd55589d8c5b31bc1d
[INFO] running `Command { std: "docker" "start" "-a" "ee9d037558ed01584b95df623d6daf0478829a971e5f91bd55589d8c5b31bc1d", kill_on_drop: false }`
[INFO] [stderr]    Compiling yansi v1.0.1
[INFO] [stderr]    Compiling num-conv v0.2.2
[INFO] [stderr]    Compiling proc-macro2-diagnostics v0.10.1
[INFO] [stderr]    Compiling pin-project-lite v0.2.17
[INFO] [stderr]     Checking memchr v2.8.1
[INFO] [stderr]    Compiling libc v0.2.186
[INFO] [stderr]    Compiling cookie v0.18.1
[INFO] [stderr]     Checking futures-io v0.3.32
[INFO] [stderr]    Compiling futures-core v0.3.32
[INFO] [stderr]    Compiling futures-sink v0.3.32
[INFO] [stderr]    Compiling syn v2.0.117
[INFO] [stderr]     Checking errno v0.3.14
[INFO] [stderr]     Checking socket2 v0.6.4
[INFO] [stderr]     Checking mio v1.2.1
[INFO] [stderr]     Checking indexmap v2.14.0
[INFO] [stderr]     Checking is-terminal v0.4.17
[INFO] [stderr]    Compiling zerocopy v0.8.50
[INFO] [stderr]    Compiling bytes v1.11.1
[INFO] [stderr]    Compiling futures-task v0.3.32
[INFO] [stderr]     Checking signal-hook-registry v1.4.8
[INFO] [stderr]    Compiling time-macros v0.2.27
[INFO] [stderr]     Checking http v0.2.12
[INFO] [stderr]    Compiling futures-util v0.3.32
[INFO] [stderr]    Compiling futures-channel v0.3.32
[INFO] [stderr]    Compiling tracing-core v0.1.36
[INFO] [stderr]    Compiling uncased v0.9.10
[INFO] [stderr]    Compiling rustix v1.1.4
[INFO] [stderr]    Compiling try-lock v0.2.5
[INFO] [stderr]    Compiling bitflags v2.11.1
[INFO] [stderr]    Compiling want v0.3.1
[INFO] [stderr]    Compiling tracing v0.1.44
[INFO] [stderr]    Compiling httparse v1.10.1
[INFO] [stderr]    Compiling inlinable_string v0.1.15
[INFO] [stderr]    Compiling httpdate v1.0.3
[INFO] [stderr]     Checking winnow v0.7.15
[INFO] [stderr]     Checking linux-raw-sys v0.12.1
[INFO] [stderr]    Compiling tower-service v0.3.3
[INFO] [stderr]    Compiling percent-encoding v2.3.2
[INFO] [stderr]     Checking http-body v0.4.6
[INFO] [stderr]     Checking parking_lot_core v0.9.12
[INFO] [stderr]     Checking getrandom v0.4.2
[INFO] [stderr]     Checking socket2 v0.5.10
[INFO] [stderr]    Compiling multer v3.1.0
[INFO] [stderr]    Compiling figment v0.10.19
[INFO] [stderr]    Compiling stable-pattern v0.1.0
[INFO] [stderr]    Compiling state v0.6.0
[INFO] [stderr]    Compiling either v1.16.0
[INFO] [stderr]    Compiling smallvec v1.15.1
[INFO] [stderr]    Compiling log v0.4.30
[INFO] [stderr]    Compiling time v0.3.47
[INFO] [stderr]     Checking parking_lot v0.12.5
[INFO] [stderr]    Compiling tokio v1.52.3
[INFO] [stderr]     Checking http v1.4.1
[INFO] [stderr]    Compiling rocket v0.5.1 (/opt/rustwide/workdir)
[INFO] [stderr]    Compiling glob v0.3.3
[INFO] [stderr]     Checking spin v0.9.8
[INFO] [stderr]     Checking num_cpus v1.17.0
[INFO] [stderr]     Checking binascii v0.1.4
[INFO] [stderr]     Checking diff v0.1.13
[INFO] [stderr]     Checking pretty_assertions v1.4.1
[INFO] [stderr]     Checking tempfile v3.27.0
[INFO] [stderr]    Compiling futures v0.3.32
[INFO] [stderr]     Checking ppv-lite86 v0.2.21
[INFO] [stderr]    Compiling devise_core v0.4.2
[INFO] [stderr]    Compiling serde_derive v1.0.228
[INFO] [stderr]    Compiling tokio-macros v2.7.0
[INFO] [stderr]    Compiling pear_codegen v0.2.9
[INFO] [stderr]    Compiling ref-cast-impl v1.0.25
[INFO] [stderr]    Compiling async-stream-impl v0.3.6
[INFO] [stderr]    Compiling async-trait v0.1.89
[INFO] [stderr]     Checking rand_chacha v0.3.1
[INFO] [stderr]    Compiling hyper v0.14.32
[INFO] [stderr]     Checking rand v0.8.6
[INFO] [stderr]     Checking async-stream v0.3.6
[INFO] [stderr]    Compiling ref-cast v1.0.25
[INFO] [stderr]    Compiling devise_codegen v0.4.2
[INFO] [stderr]     Checking pear v0.2.9
[INFO] [stderr]    Compiling devise v0.4.2
[INFO] [stderr]    Compiling rocket_http v0.5.1
[INFO] [stderr]     Checking serde v1.0.228
[INFO] [stderr]     Checking serde_spanned v0.6.9
[INFO] [stderr]     Checking toml_datetime v0.6.11
[INFO] [stderr]     Checking ubyte v0.10.4
[INFO] [stderr]     Checking toml_edit v0.22.27
[INFO] [stderr]    Compiling rocket_codegen v0.5.1
[INFO] [stderr]     Checking tokio-util v0.7.18
[INFO] [stderr]     Checking tokio-stream v0.1.18
[INFO] [stderr]     Checking toml v0.8.23
[INFO] [stderr]     Checking h2 v0.3.27
[INFO] [stdout] warning: unexpected `cfg` condition name: `nightly`
[INFO] [stdout]  --> src/lib.rs:6:13
[INFO] [stdout]   |
[INFO] [stdout] 6 | #![cfg_attr(nightly, feature(doc_cfg))]
[INFO] [stdout]   |             ^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = help: expected names are: `docsrs`, `feature`, and `test` and 32 more
[INFO] [stdout]   = help: consider using a Cargo feature instead
[INFO] [stdout]   = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]            [lints.rust]
[INFO] [stdout]            unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] }
[INFO] [stdout]   = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `nightly`
[INFO] [stdout]  --> src/lib.rs:7:13
[INFO] [stdout]   |
[INFO] [stdout] 7 | #![cfg_attr(nightly, feature(decl_macro))]
[INFO] [stdout]   |             ^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = help: consider using a Cargo feature instead
[INFO] [stdout]   = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]            [lints.rust]
[INFO] [stdout]            unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] }
[INFO] [stdout]   = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `nightly`
[INFO] [stdout]    --> src/outcome.rs:630:1
[INFO] [stdout]     |
[INFO] [stdout] 630 | / crate::export! {
[INFO] [stdout] 631 | |     /// Unwraps a [`Success`](Outcome::Success) or propagates a `Forward` or
[INFO] [stdout] 632 | |     /// `Error` by returning early.
[INFO] [stdout] 633 | |     ///
[INFO] [stdout] ...   |
[INFO] [stdout] 711 | | }
[INFO] [stdout]     | |_^
[INFO] [stdout]     |
[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::export` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `nightly`
[INFO] [stdout]   --> src/request/mod.rs:19:1
[INFO] [stdout]    |
[INFO] [stdout] 19 | / crate::export! {
[INFO] [stdout] 20 | |     /// Store and immediately retrieve a vector-like value `$v` (`String` or
[INFO] [stdout] 21 | |     /// `Vec<T>`) in `$request`'s local cache using a locally generated
[INFO] [stdout] 22 | |     /// anonymous type to avoid type conflicts.
[INFO] [stdout] ...  |
[INFO] [stdout] 67 | | }
[INFO] [stdout]    | |_^
[INFO] [stdout]    |
[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::export` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `nightly`
[INFO] [stdout]    --> src/request/mod.rs:69:1
[INFO] [stdout]     |
[INFO] [stdout]  69 | / crate::export! {
[INFO] [stdout]  70 | |     /// Store and immediately retrieve a value `$v` in `$request`'s local cache
[INFO] [stdout]  71 | |     /// using a locally generated anonymous type to avoid type conflicts.
[INFO] [stdout]  72 | |     ///
[INFO] [stdout] ...   |
[INFO] [stdout] 113 | | }
[INFO] [stdout]     | |_^
[INFO] [stdout]     |
[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::export` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `nightly`
[INFO] [stdout]    --> src/response/stream/mod.rs:206:1
[INFO] [stdout]     |
[INFO] [stdout] 206 | / crate::export! {
[INFO] [stdout] 207 | |     /// Retrofitted support for [`Stream`]s with `yield`, `for await` syntax.
[INFO] [stdout] 208 | |     ///
[INFO] [stdout] 209 | |     /// [`Stream`]: https://docs.rs/futures/0.3/futures/stream/trait.Stream.html
[INFO] [stdout] ...   |
[INFO] [stdout] 288 | | }
[INFO] [stdout]     | |_^
[INFO] [stdout]     |
[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::export` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `nightly`
[INFO] [stdout]    --> src/response/stream/reader.rs:196:1
[INFO] [stdout]     |
[INFO] [stdout] 196 | / crate::export! {
[INFO] [stdout] 197 | |     /// Type and stream expression macro for [`struct@ReaderStream`].
[INFO] [stdout] 198 | |     ///
[INFO] [stdout] 199 | |     /// See [`stream!`](crate::response::stream::stream) for the syntax
[INFO] [stdout] ...   |
[INFO] [stdout] 207 | | }
[INFO] [stdout]     | |_^
[INFO] [stdout]     |
[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::export` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `nightly`
[INFO] [stdout]   --> src/response/stream/bytes.rs:75:1
[INFO] [stdout]    |
[INFO] [stdout] 75 | / crate::export! {
[INFO] [stdout] 76 | |     /// Type and stream expression macro for [`struct@ByteStream`].
[INFO] [stdout] 77 | |     ///
[INFO] [stdout] 78 | |     /// See [`stream!`](crate::response::stream::stream) for the syntax
[INFO] [stdout] ...  |
[INFO] [stdout] 86 | | }
[INFO] [stdout]    | |_^
[INFO] [stdout]    |
[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::export` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `nightly`
[INFO] [stdout]   --> src/response/stream/text.rs:85:1
[INFO] [stdout]    |
[INFO] [stdout] 85 | / crate::export! {
[INFO] [stdout] 86 | |     /// Type and stream expression macro for [`struct@TextStream`].
[INFO] [stdout] 87 | |     ///
[INFO] [stdout] 88 | |     /// See [`stream!`](crate::response::stream::stream) for the syntax
[INFO] [stdout] ...  |
[INFO] [stdout] 96 | | }
[INFO] [stdout]    | |_^
[INFO] [stdout]    |
[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::export` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `nightly`
[INFO] [stdout]    --> src/response/stream/sse.rs:588:1
[INFO] [stdout]     |
[INFO] [stdout] 588 | / crate::export! {
[INFO] [stdout] 589 | |     /// Type and stream expression macro for [`struct@EventStream`].
[INFO] [stdout] 590 | |     ///
[INFO] [stdout] 591 | |     /// See [`stream!`](crate::response::stream::stream) for the syntax
[INFO] [stdout] ...   |
[INFO] [stdout] 602 | | }
[INFO] [stdout]     | |_^
[INFO] [stdout]     |
[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::export` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `nightly`
[INFO] [stdout]    --> src/config/config.rs:105:16
[INFO] [stdout]     |
[INFO] [stdout] 105 |     #[cfg_attr(nightly, doc(cfg(feature = "tls")))]
[INFO] [stdout]     |                ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `nightly`
[INFO] [stdout]    --> src/config/config.rs:112:16
[INFO] [stdout]     |
[INFO] [stdout] 112 |     #[cfg_attr(nightly, doc(cfg(feature = "secrets")))]
[INFO] [stdout]     |                ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `nightly`
[INFO] [stdout]   --> src/config/shutdown.rs:21:12
[INFO] [stdout]    |
[INFO] [stdout] 21 | #[cfg_attr(nightly, doc(cfg(unix)))]
[INFO] [stdout]    |            ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `nightly`
[INFO] [stdout]    --> src/config/shutdown.rs:218:16
[INFO] [stdout]     |
[INFO] [stdout] 218 |     #[cfg_attr(nightly, doc(cfg(unix)))]
[INFO] [stdout]     |                ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `nightly`
[INFO] [stdout]    --> src/form/validate.rs:90:1
[INFO] [stdout]     |
[INFO] [stdout]  90 | / crate::export! {
[INFO] [stdout]  91 | |     /// A helper macro for custom validation error messages.
[INFO] [stdout]  92 | |     ///
[INFO] [stdout]  93 | |     /// The macro works similar to [`std::format!`]. It generates a form
[INFO] [stdout] ...   |
[INFO] [stdout] 158 | | }
[INFO] [stdout]     | |_^
[INFO] [stdout]     |
[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::export` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `nightly`
[INFO] [stdout]    --> src/fs/server.rs:405:1
[INFO] [stdout]     |
[INFO] [stdout] 405 | / crate::export! {
[INFO] [stdout] 406 | |     /// Generates a crate-relative version of a path.
[INFO] [stdout] 407 | |     ///
[INFO] [stdout] 408 | |     /// This macro is primarily intended for use with [`FileServer`] to serve
[INFO] [stdout] ...   |
[INFO] [stdout] 453 | | }
[INFO] [stdout]     | |_^
[INFO] [stdout]     |
[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::export` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `broken_fmt`
[INFO] [stdout]   --> src/server.rs:76:15
[INFO] [stdout]    |
[INFO] [stdout] 76 |     #[cfg(not(broken_fmt))]
[INFO] [stdout]    |               ^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(broken_fmt)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(broken_fmt)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `broken_fmt`
[INFO] [stdout]    --> src/server.rs:165:19
[INFO] [stdout]     |
[INFO] [stdout] 165 |         #[cfg(not(broken_fmt))]
[INFO] [stdout]     |                   ^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(broken_fmt)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(broken_fmt)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `nightly`
[INFO] [stdout]  --> src/lib.rs:6:13
[INFO] [stdout]   |
[INFO] [stdout] 6 | #![cfg_attr(nightly, feature(doc_cfg))]
[INFO] [stdout]   |             ^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = help: expected names are: `docsrs`, `feature`, and `test` and 32 more
[INFO] [stdout]   = help: consider using a Cargo feature instead
[INFO] [stdout]   = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]            [lints.rust]
[INFO] [stdout]            unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] }
[INFO] [stdout]   = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]   = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `nightly`
[INFO] [stdout]  --> src/lib.rs:7:13
[INFO] [stdout]   |
[INFO] [stdout] 7 | #![cfg_attr(nightly, feature(decl_macro))]
[INFO] [stdout]   |             ^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = help: consider using a Cargo feature instead
[INFO] [stdout]   = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]            [lints.rust]
[INFO] [stdout]            unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] }
[INFO] [stdout]   = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs`
[INFO] [stdout]   = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `nightly`
[INFO] [stdout]    --> src/outcome.rs:630:1
[INFO] [stdout]     |
[INFO] [stdout] 630 | / crate::export! {
[INFO] [stdout] 631 | |     /// Unwraps a [`Success`](Outcome::Success) or propagates a `Forward` or
[INFO] [stdout] 632 | |     /// `Error` by returning early.
[INFO] [stdout] 633 | |     ///
[INFO] [stdout] ...   |
[INFO] [stdout] 711 | | }
[INFO] [stdout]     | |_^
[INFO] [stdout]     |
[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::export` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused import: `crate::sentinel::resolve`
[INFO] [stdout]    --> src/sentinel.rs:450:9
[INFO] [stdout]     |
[INFO] [stdout] 450 |     use crate::sentinel::resolve;
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: `#[warn(unused_imports)]` (part of `#[warn(unused)]`) on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `nightly`
[INFO] [stdout]   --> src/request/mod.rs:19:1
[INFO] [stdout]    |
[INFO] [stdout] 19 | / crate::export! {
[INFO] [stdout] 20 | |     /// Store and immediately retrieve a vector-like value `$v` (`String` or
[INFO] [stdout] 21 | |     /// `Vec<T>`) in `$request`'s local cache using a locally generated
[INFO] [stdout] 22 | |     /// anonymous type to avoid type conflicts.
[INFO] [stdout] ...  |
[INFO] [stdout] 67 | | }
[INFO] [stdout]    | |_^
[INFO] [stdout]    |
[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::export` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `nightly`
[INFO] [stdout]    --> src/request/mod.rs:69:1
[INFO] [stdout]     |
[INFO] [stdout]  69 | / crate::export! {
[INFO] [stdout]  70 | |     /// Store and immediately retrieve a value `$v` in `$request`'s local cache
[INFO] [stdout]  71 | |     /// using a locally generated anonymous type to avoid type conflicts.
[INFO] [stdout]  72 | |     ///
[INFO] [stdout] ...   |
[INFO] [stdout] 113 | | }
[INFO] [stdout]     | |_^
[INFO] [stdout]     |
[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::export` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `nightly`
[INFO] [stdout]    --> src/response/stream/mod.rs:206:1
[INFO] [stdout]     |
[INFO] [stdout] 206 | / crate::export! {
[INFO] [stdout] 207 | |     /// Retrofitted support for [`Stream`]s with `yield`, `for await` syntax.
[INFO] [stdout] 208 | |     ///
[INFO] [stdout] 209 | |     /// [`Stream`]: https://docs.rs/futures/0.3/futures/stream/trait.Stream.html
[INFO] [stdout] ...   |
[INFO] [stdout] 288 | | }
[INFO] [stdout]     | |_^
[INFO] [stdout]     |
[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::export` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `nightly`
[INFO] [stdout]    --> src/response/stream/reader.rs:196:1
[INFO] [stdout]     |
[INFO] [stdout] 196 | / crate::export! {
[INFO] [stdout] 197 | |     /// Type and stream expression macro for [`struct@ReaderStream`].
[INFO] [stdout] 198 | |     ///
[INFO] [stdout] 199 | |     /// See [`stream!`](crate::response::stream::stream) for the syntax
[INFO] [stdout] ...   |
[INFO] [stdout] 207 | | }
[INFO] [stdout]     | |_^
[INFO] [stdout]     |
[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::export` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `nightly`
[INFO] [stdout]   --> src/response/stream/bytes.rs:75:1
[INFO] [stdout]    |
[INFO] [stdout] 75 | / crate::export! {
[INFO] [stdout] 76 | |     /// Type and stream expression macro for [`struct@ByteStream`].
[INFO] [stdout] 77 | |     ///
[INFO] [stdout] 78 | |     /// See [`stream!`](crate::response::stream::stream) for the syntax
[INFO] [stdout] ...  |
[INFO] [stdout] 86 | | }
[INFO] [stdout]    | |_^
[INFO] [stdout]    |
[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::export` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `nightly`
[INFO] [stdout]   --> src/response/stream/text.rs:85:1
[INFO] [stdout]    |
[INFO] [stdout] 85 | / crate::export! {
[INFO] [stdout] 86 | |     /// Type and stream expression macro for [`struct@TextStream`].
[INFO] [stdout] 87 | |     ///
[INFO] [stdout] 88 | |     /// See [`stream!`](crate::response::stream::stream) for the syntax
[INFO] [stdout] ...  |
[INFO] [stdout] 96 | | }
[INFO] [stdout]    | |_^
[INFO] [stdout]    |
[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::export` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `nightly`
[INFO] [stdout]    --> src/response/stream/sse.rs:588:1
[INFO] [stdout]     |
[INFO] [stdout] 588 | / crate::export! {
[INFO] [stdout] 589 | |     /// Type and stream expression macro for [`struct@EventStream`].
[INFO] [stdout] 590 | |     ///
[INFO] [stdout] 591 | |     /// See [`stream!`](crate::response::stream::stream) for the syntax
[INFO] [stdout] ...   |
[INFO] [stdout] 602 | | }
[INFO] [stdout]     | |_^
[INFO] [stdout]     |
[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::export` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `nightly`
[INFO] [stdout]    --> src/config/config.rs:105:16
[INFO] [stdout]     |
[INFO] [stdout] 105 |     #[cfg_attr(nightly, doc(cfg(feature = "tls")))]
[INFO] [stdout]     |                ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `nightly`
[INFO] [stdout]    --> src/config/config.rs:112:16
[INFO] [stdout]     |
[INFO] [stdout] 112 |     #[cfg_attr(nightly, doc(cfg(feature = "secrets")))]
[INFO] [stdout]     |                ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `nightly`
[INFO] [stdout]   --> src/config/shutdown.rs:21:12
[INFO] [stdout]    |
[INFO] [stdout] 21 | #[cfg_attr(nightly, doc(cfg(unix)))]
[INFO] [stdout]    |            ^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `nightly`
[INFO] [stdout]    --> src/config/shutdown.rs:218:16
[INFO] [stdout]     |
[INFO] [stdout] 218 |     #[cfg_attr(nightly, doc(cfg(unix)))]
[INFO] [stdout]     |                ^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(nightly)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(nightly)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `nightly`
[INFO] [stdout]    --> src/form/validate.rs:90:1
[INFO] [stdout]     |
[INFO] [stdout]  90 | / crate::export! {
[INFO] [stdout]  91 | |     /// A helper macro for custom validation error messages.
[INFO] [stdout]  92 | |     ///
[INFO] [stdout]  93 | |     /// The macro works similar to [`std::format!`]. It generates a form
[INFO] [stdout] ...   |
[INFO] [stdout] 158 | | }
[INFO] [stdout]     | |_^
[INFO] [stdout]     |
[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::export` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `nightly`
[INFO] [stdout]    --> src/fs/server.rs:405:1
[INFO] [stdout]     |
[INFO] [stdout] 405 | / crate::export! {
[INFO] [stdout] 406 | |     /// Generates a crate-relative version of a path.
[INFO] [stdout] 407 | |     ///
[INFO] [stdout] 408 | |     /// This macro is primarily intended for use with [`FileServer`] to serve
[INFO] [stdout] ...   |
[INFO] [stdout] 453 | | }
[INFO] [stdout]     | |_^
[INFO] [stdout]     |
[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::export` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the macro `crate::export` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `broken_fmt`
[INFO] [stdout]   --> src/server.rs:76:15
[INFO] [stdout]    |
[INFO] [stdout] 76 |     #[cfg(not(broken_fmt))]
[INFO] [stdout]    |               ^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = help: consider using a Cargo feature instead
[INFO] [stdout]    = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]             [lints.rust]
[INFO] [stdout]             unexpected_cfgs = { level = "warn", check-cfg = ['cfg(broken_fmt)'] }
[INFO] [stdout]    = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(broken_fmt)");` to the top of the `build.rs`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition name: `broken_fmt`
[INFO] [stdout]    --> src/server.rs:165:19
[INFO] [stdout]     |
[INFO] [stdout] 165 |         #[cfg(not(broken_fmt))]
[INFO] [stdout]     |                   ^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: consider using a Cargo feature instead
[INFO] [stdout]     = help: or consider adding in `Cargo.toml` the `check-cfg` lint config for the lint:
[INFO] [stdout]              [lints.rust]
[INFO] [stdout]              unexpected_cfgs = { level = "warn", check-cfg = ['cfg(broken_fmt)'] }
[INFO] [stdout]     = help: or consider adding `println!("cargo::rustc-check-cfg=cfg(broken_fmt)");` to the top of the `build.rs`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused variable: `opts`
[INFO] [stdout]    --> src/form/from_form.rs:821:13
[INFO] [stdout]     |
[INFO] [stdout] 821 |     fn init(opts: Options) -> Self::Context {
[INFO] [stdout]     |             ^^^^ help: if this is intentional, prefix it with an underscore: `_opts`
[INFO] [stdout]     |
[INFO] [stdout]     = note: `#[warn(unused_variables)]` (part of `#[warn(unused)]`) on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused variable: `opts`
[INFO] [stdout]    --> src/form/from_form.rs:821:13
[INFO] [stdout]     |
[INFO] [stdout] 821 |     fn init(opts: Options) -> Self::Context {
[INFO] [stdout]     |             ^^^^ help: if this is intentional, prefix it with an underscore: `_opts`
[INFO] [stdout]     |
[INFO] [stdout]     = note: `#[warn(unused_variables)]` (part of `#[warn(unused)]`) on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused variable: `opts`
[INFO] [stdout]   --> src/form/strict.rs:96:13
[INFO] [stdout]    |
[INFO] [stdout] 96 |     fn init(opts: Options) -> Self::Context {
[INFO] [stdout]    |             ^^^^ help: if this is intentional, prefix it with an underscore: `_opts`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused variable: `opts`
[INFO] [stdout]   --> src/form/lenient.rs:81:13
[INFO] [stdout]    |
[INFO] [stdout] 81 |     fn init(opts: Options) -> Self::Context {
[INFO] [stdout]    |             ^^^^ help: if this is intentional, prefix it with an underscore: `_opts`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused variable: `opts`
[INFO] [stdout]   --> src/form/strict.rs:96:13
[INFO] [stdout]    |
[INFO] [stdout] 96 |     fn init(opts: Options) -> Self::Context {
[INFO] [stdout]    |             ^^^^ help: if this is intentional, prefix it with an underscore: `_opts`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused variable: `opts`
[INFO] [stdout]   --> src/form/lenient.rs:81:13
[INFO] [stdout]    |
[INFO] [stdout] 81 |     fn init(opts: Options) -> Self::Context {
[INFO] [stdout]    |             ^^^^ help: if this is intentional, prefix it with an underscore: `_opts`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: method `name` is never used
[INFO] [stdout]   --> src/shield/policy.rs:69:8
[INFO] [stdout]    |
[INFO] [stdout] 68 | pub(crate) trait SubPolicy: Send + Sync {
[INFO] [stdout]    |                  --------- method in this trait
[INFO] [stdout] 69 |     fn name(&self) -> &'static UncasedStr;
[INFO] [stdout]    |        ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: `#[warn(dead_code)]` (part of `#[warn(unused)]`) on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: field `1` is never read
[INFO] [stdout]    --> src/cookies.rs:173:29
[INFO] [stdout]     |
[INFO] [stdout] 173 |     Remove(Cookie<'static>, bool),
[INFO] [stdout]     |     ------                  ^^^^
[INFO] [stdout]     |     |
[INFO] [stdout]     |     field in this variant
[INFO] [stdout]     |
[INFO] [stdout]     = note: `Op` has a derived impl for the trait `Clone`, but this is intentionally ignored during dead code analysis
[INFO] [stdout] help: consider changing the field to be of unit type to suppress this warning while preserving the field numbering, or remove the field
[INFO] [stdout]     |
[INFO] [stdout] 173 -     Remove(Cookie<'static>, bool),
[INFO] [stdout] 173 +     Remove(Cookie<'static>, ()),
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/outcome.rs:737:9
[INFO] [stdout]     |
[INFO] [stdout] 736 |     pub(crate) fn log_display(&self) -> Display<'_, 'r> {
[INFO] [stdout]     |     --------------------------------------------------- move the `impl` block outside of this method `log_display`
[INFO] [stdout] 737 |         impl fmt::Display for Display<'_, '_> {
[INFO] [stdout]     |         ^^^^^------------^^^^^-------^^^^^^^^
[INFO] [stdout]     |              |                |
[INFO] [stdout]     |              |                `Display` is not local
[INFO] [stdout]     |              `Display` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: `#[warn(non_local_definitions)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: eliding a lifetime that's named elsewhere is confusing
[INFO] [stdout]    --> src/form/context.rs:223:75
[INFO] [stdout]     |
[INFO] [stdout] 223 |     pub fn field_errors<'a, N>(&'a self, name: N) -> impl Iterator<Item = &Error<'v>> + '_
[INFO] [stdout]     |                                 --                                        ^^^^^^^^^^    ^^ the same lifetime is elided here
[INFO] [stdout]     |                                 |                                         |
[INFO] [stdout]     |                                 the lifetime is named here                the same lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default
[INFO] [stdout] help: consistently use `'a`
[INFO] [stdout]     |
[INFO] [stdout] 223 -     pub fn field_errors<'a, N>(&'a self, name: N) -> impl Iterator<Item = &Error<'v>> + '_
[INFO] [stdout] 223 +     pub fn field_errors<'a, N>(&'a self, name: N) -> impl Iterator<Item = &'a Error<'v>> + 'a
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: eliding a lifetime that's named elsewhere is confusing
[INFO] [stdout]    --> src/form/context.rs:272:81
[INFO] [stdout]     |
[INFO] [stdout] 272 |     pub fn exact_field_errors<'a, N>(&'a self, name: N) -> impl Iterator<Item = &Error<'v>> + '_
[INFO] [stdout]     |                                       --                                        ^^^^^^^^^^    ^^ the same lifetime is elided here
[INFO] [stdout]     |                                       |                                         |
[INFO] [stdout]     |                                       the lifetime is named here                the same lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: consistently use `'a`
[INFO] [stdout]     |
[INFO] [stdout] 272 -     pub fn exact_field_errors<'a, N>(&'a self, name: N) -> impl Iterator<Item = &Error<'v>> + '_
[INFO] [stdout] 272 +     pub fn exact_field_errors<'a, N>(&'a self, name: N) -> impl Iterator<Item = &'a Error<'v>> + 'a
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: method `name` is never used
[INFO] [stdout]   --> src/shield/policy.rs:69:8
[INFO] [stdout]    |
[INFO] [stdout] 68 | pub(crate) trait SubPolicy: Send + Sync {
[INFO] [stdout]    |                  --------- method in this trait
[INFO] [stdout] 69 |     fn name(&self) -> &'static UncasedStr;
[INFO] [stdout]    |        ^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: `#[warn(dead_code)]` (part of `#[warn(unused)]`) on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: field `1` is never read
[INFO] [stdout]    --> src/cookies.rs:173:29
[INFO] [stdout]     |
[INFO] [stdout] 173 |     Remove(Cookie<'static>, bool),
[INFO] [stdout]     |     ------                  ^^^^
[INFO] [stdout]     |     |
[INFO] [stdout]     |     field in this variant
[INFO] [stdout]     |
[INFO] [stdout]     = note: `Op` has a derived impl for the trait `Clone`, but this is intentionally ignored during dead code analysis
[INFO] [stdout] help: consider changing the field to be of unit type to suppress this warning while preserving the field numbering, or remove the field
[INFO] [stdout]     |
[INFO] [stdout] 173 -     Remove(Cookie<'static>, bool),
[INFO] [stdout] 173 +     Remove(Cookie<'static>, ()),
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item
[INFO] [stdout]    --> src/outcome.rs:737:9
[INFO] [stdout]     |
[INFO] [stdout] 736 |     pub(crate) fn log_display(&self) -> Display<'_, 'r> {
[INFO] [stdout]     |     --------------------------------------------------- move the `impl` block outside of this method `log_display`
[INFO] [stdout] 737 |         impl fmt::Display for Display<'_, '_> {
[INFO] [stdout]     |         ^^^^^------------^^^^^-------^^^^^^^^
[INFO] [stdout]     |              |                |
[INFO] [stdout]     |              |                `Display` is not local
[INFO] [stdout]     |              `Display` is not local
[INFO] [stdout]     |
[INFO] [stdout]     = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl`
[INFO] [stdout]     = note: `#[warn(non_local_definitions)]` on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: eliding a lifetime that's named elsewhere is confusing
[INFO] [stdout]    --> src/form/context.rs:223:75
[INFO] [stdout]     |
[INFO] [stdout] 223 |     pub fn field_errors<'a, N>(&'a self, name: N) -> impl Iterator<Item = &Error<'v>> + '_
[INFO] [stdout]     |                                 --                                        ^^^^^^^^^^    ^^ the same lifetime is elided here
[INFO] [stdout]     |                                 |                                         |
[INFO] [stdout]     |                                 the lifetime is named here                the same lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]     = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default
[INFO] [stdout] help: consistently use `'a`
[INFO] [stdout]     |
[INFO] [stdout] 223 -     pub fn field_errors<'a, N>(&'a self, name: N) -> impl Iterator<Item = &Error<'v>> + '_
[INFO] [stdout] 223 +     pub fn field_errors<'a, N>(&'a self, name: N) -> impl Iterator<Item = &'a Error<'v>> + 'a
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: eliding a lifetime that's named elsewhere is confusing
[INFO] [stdout]    --> src/form/context.rs:272:81
[INFO] [stdout]     |
[INFO] [stdout] 272 |     pub fn exact_field_errors<'a, N>(&'a self, name: N) -> impl Iterator<Item = &Error<'v>> + '_
[INFO] [stdout]     |                                       --                                        ^^^^^^^^^^    ^^ the same lifetime is elided here
[INFO] [stdout]     |                                       |                                         |
[INFO] [stdout]     |                                       the lifetime is named here                the same lifetime is elided here
[INFO] [stdout]     |
[INFO] [stdout]     = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: consistently use `'a`
[INFO] [stdout]     |
[INFO] [stdout] 272 -     pub fn exact_field_errors<'a, N>(&'a self, name: N) -> impl Iterator<Item = &Error<'v>> + '_
[INFO] [stdout] 272 +     pub fn exact_field_errors<'a, N>(&'a self, name: N) -> impl Iterator<Item = &'a Error<'v>> + 'a
[INFO] [stdout]     |
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: missing documentation for a function
[INFO] [stdout]    --> src/catcher/handler.rs:122:1
[INFO] [stdout]     |
[INFO] [stdout] 122 | pub fn dummy_handler<'r>(_: Status, _: &'r Request<'_>) -> BoxFuture<'r> {
[INFO] [stdout]     | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout] note: the lint level is defined here
[INFO] [stdout]    --> src/lib.rs:10:9
[INFO] [stdout]     |
[INFO] [stdout]  10 | #![warn(missing_docs)]
[INFO] [stdout]     |         ^^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `macro_rules!` definition, `#[macro_export]` macro should be written at top level module
[INFO] [stdout]    --> tests/file_server.rs:122:5
[INFO] [stdout]     |
[INFO] [stdout] 122 |     #[get("/<value>", rank = 20)]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: remove the `#[macro_export]` or move this `macro_rules!` outside the of the current function `test_forwarding`
[INFO] [stdout]     = note: a `macro_rules!` definition is non-local if it is nested inside an item and has a `#[macro_export]` attribute
[INFO] [stdout]     = note: the attribute macro `get` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen`
[INFO] [stdout]     = note: `#[warn(non_local_definitions)]` on by default
[INFO] [stdout]     = note: this warning originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `macro_rules!` definition, `#[macro_export]` macro should be written at top level module
[INFO] [stdout]    --> tests/file_server.rs:125:5
[INFO] [stdout]     |
[INFO] [stdout] 125 |     #[get("/<a>/<b>", rank = 20)]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: remove the `#[macro_export]` or move this `macro_rules!` outside the of the current function `test_forwarding`
[INFO] [stdout]     = note: a `macro_rules!` definition is non-local if it is nested inside an item and has a `#[macro_export]` attribute
[INFO] [stdout]     = note: the attribute macro `get` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen`
[INFO] [stdout]     = note: this warning originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `macro_rules!` definition, `#[macro_export]` macro should be written at top level module
[INFO] [stdout]  --> tests/can-correct-bad-local-uri.rs:6:5
[INFO] [stdout]   |
[INFO] [stdout] 6 |     #[rocket::get("/")] fn f() {}
[INFO] [stdout]   |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]   |
[INFO] [stdout]   = help: remove the `#[macro_export]` or move this `macro_rules!` outside the of the current function `can_correct_bad_local_uri`
[INFO] [stdout]   = note: a `macro_rules!` definition is non-local if it is nested inside an item and has a `#[macro_export]` attribute
[INFO] [stdout]   = note: the attribute macro `rocket::get` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen`
[INFO] [stdout]   = note: `#[warn(non_local_definitions)]` on by default
[INFO] [stdout]   = note: this warning originates in the attribute macro `rocket::get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `macro_rules!` definition, `#[macro_export]` macro should be written at top level module
[INFO] [stdout]    --> tests/shutdown-fairings.rs:129:5
[INFO] [stdout]     |
[INFO] [stdout] 129 |     #[get("/")]
[INFO] [stdout]     |     ^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: remove the `#[macro_export]` or move this `macro_rules!` outside the of the current function `background_tasks_dont_prevent_terminate`
[INFO] [stdout]     = note: a `macro_rules!` definition is non-local if it is nested inside an item and has a `#[macro_export]` attribute
[INFO] [stdout]     = note: the attribute macro `get` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen`
[INFO] [stdout]     = note: `#[warn(non_local_definitions)]` on by default
[INFO] [stdout]     = note: this warning originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `macro_rules!` definition, `#[macro_export]` macro should be written at top level module
[INFO] [stdout]    --> tests/sentinel.rs:168:5
[INFO] [stdout]     |
[INFO] [stdout] 168 |     #[get("/")]
[INFO] [stdout]     |     ^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: remove the `#[macro_export]` or move this `macro_rules!` outside the of the current function `inner_sentinels_detected`
[INFO] [stdout]     = note: a `macro_rules!` definition is non-local if it is nested inside an item and has a `#[macro_export]` attribute
[INFO] [stdout]     = note: the attribute macro `get` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen`
[INFO] [stdout]     = note: `#[warn(non_local_definitions)]` on by default
[INFO] [stdout]     = note: this warning originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `macro_rules!` definition, `#[macro_export]` macro should be written at top level module
[INFO] [stdout]    --> tests/sentinel.rs:177:5
[INFO] [stdout]     |
[INFO] [stdout] 177 |     #[get("/")]
[INFO] [stdout]     |     ^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: remove the `#[macro_export]` or move this `macro_rules!` outside the of the current function `inner_sentinels_detected`
[INFO] [stdout]     = note: a `macro_rules!` definition is non-local if it is nested inside an item and has a `#[macro_export]` attribute
[INFO] [stdout]     = note: the attribute macro `get` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen`
[INFO] [stdout]     = note: this warning originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `macro_rules!` definition, `#[macro_export]` macro should be written at top level module
[INFO] [stdout]    --> tests/sentinel.rs:183:5
[INFO] [stdout]     |
[INFO] [stdout] 183 |     #[get("/")]
[INFO] [stdout]     |     ^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: remove the `#[macro_export]` or move this `macro_rules!` outside the of the current function `inner_sentinels_detected`
[INFO] [stdout]     = note: a `macro_rules!` definition is non-local if it is nested inside an item and has a `#[macro_export]` attribute
[INFO] [stdout]     = note: the attribute macro `get` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen`
[INFO] [stdout]     = note: this warning originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `macro_rules!` definition, `#[macro_export]` macro should be written at top level module
[INFO] [stdout]    --> tests/sentinel.rs:198:5
[INFO] [stdout]     |
[INFO] [stdout] 198 |     #[get("/")]
[INFO] [stdout]     |     ^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: remove the `#[macro_export]` or move this `macro_rules!` outside the of the current function `inner_sentinels_detected`
[INFO] [stdout]     = note: a `macro_rules!` definition is non-local if it is nested inside an item and has a `#[macro_export]` attribute
[INFO] [stdout]     = note: the attribute macro `get` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen`
[INFO] [stdout]     = note: this warning originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `macro_rules!` definition, `#[macro_export]` macro should be written at top level module
[INFO] [stdout]    --> tests/sentinel.rs:203:5
[INFO] [stdout]     |
[INFO] [stdout] 203 |     #[get("/a")]
[INFO] [stdout]     |     ^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: remove the `#[macro_export]` or move this `macro_rules!` outside the of the current function `inner_sentinels_detected`
[INFO] [stdout]     = note: a `macro_rules!` definition is non-local if it is nested inside an item and has a `#[macro_export]` attribute
[INFO] [stdout]     = note: the attribute macro `get` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen`
[INFO] [stdout]     = note: this warning originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `macro_rules!` definition, `#[macro_export]` macro should be written at top level module
[INFO] [stdout]    --> tests/sentinel.rs:208:5
[INFO] [stdout]     |
[INFO] [stdout] 208 |     #[get("/b")]
[INFO] [stdout]     |     ^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: remove the `#[macro_export]` or move this `macro_rules!` outside the of the current function `inner_sentinels_detected`
[INFO] [stdout]     = note: a `macro_rules!` definition is non-local if it is nested inside an item and has a `#[macro_export]` attribute
[INFO] [stdout]     = note: the attribute macro `get` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen`
[INFO] [stdout]     = note: this warning originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `macro_rules!` definition, `#[macro_export]` macro should be written at top level module
[INFO] [stdout]    --> tests/sentinel.rs:215:5
[INFO] [stdout]     |
[INFO] [stdout] 215 |     #[get("/")]
[INFO] [stdout]     |     ^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: remove the `#[macro_export]` or move this `macro_rules!` outside the of the current function `inner_sentinels_detected`
[INFO] [stdout]     = note: a `macro_rules!` definition is non-local if it is nested inside an item and has a `#[macro_export]` attribute
[INFO] [stdout]     = note: the attribute macro `get` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen`
[INFO] [stdout]     = note: this warning originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `macro_rules!` definition, `#[macro_export]` macro should be written at top level module
[INFO] [stdout]    --> tests/sentinel.rs:225:5
[INFO] [stdout]     |
[INFO] [stdout] 225 |     #[get("/")]
[INFO] [stdout]     |     ^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: remove the `#[macro_export]` or move this `macro_rules!` outside the of the current function `inner_sentinels_detected`
[INFO] [stdout]     = note: a `macro_rules!` definition is non-local if it is nested inside an item and has a `#[macro_export]` attribute
[INFO] [stdout]     = note: the attribute macro `get` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen`
[INFO] [stdout]     = note: this warning originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `macro_rules!` definition, `#[macro_export]` macro should be written at top level module
[INFO] [stdout]    --> tests/sentinel.rs:236:5
[INFO] [stdout]     |
[INFO] [stdout] 236 |     #[get("/")]
[INFO] [stdout]     |     ^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: remove the `#[macro_export]` or move this `macro_rules!` outside the of the current function `inner_sentinels_detected`
[INFO] [stdout]     = note: a `macro_rules!` definition is non-local if it is nested inside an item and has a `#[macro_export]` attribute
[INFO] [stdout]     = note: the attribute macro `get` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen`
[INFO] [stdout]     = note: this warning originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `macro_rules!` definition, `#[macro_export]` macro should be written at top level module
[INFO] [stdout]    --> tests/sentinel.rs:250:5
[INFO] [stdout]     |
[INFO] [stdout] 250 |     #[get("/")]
[INFO] [stdout]     |     ^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: remove the `#[macro_export]` or move this `macro_rules!` outside the of the current function `inner_sentinels_detected`
[INFO] [stdout]     = note: a `macro_rules!` definition is non-local if it is nested inside an item and has a `#[macro_export]` attribute
[INFO] [stdout]     = note: the attribute macro `get` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen`
[INFO] [stdout]     = note: this warning originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `macro_rules!` definition, `#[macro_export]` macro should be written at top level module
[INFO] [stdout]    --> tests/sentinel.rs:260:5
[INFO] [stdout]     |
[INFO] [stdout] 260 |     #[get("/")] fn either_route() -> Either<ResponderSentinel, ResponderSentinel> { todo!() }
[INFO] [stdout]     |     ^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: remove the `#[macro_export]` or move this `macro_rules!` outside the of the current function `inner_sentinels_detected`
[INFO] [stdout]     = note: a `macro_rules!` definition is non-local if it is nested inside an item and has a `#[macro_export]` attribute
[INFO] [stdout]     = note: the attribute macro `get` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen`
[INFO] [stdout]     = note: this warning originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `macro_rules!` definition, `#[macro_export]` macro should be written at top level module
[INFO] [stdout]    --> tests/sentinel.rs:264:5
[INFO] [stdout]     |
[INFO] [stdout] 264 |     #[get("/")] fn either_route2() -> Either<ResponderSentinel, ()> { todo!() }
[INFO] [stdout]     |     ^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: remove the `#[macro_export]` or move this `macro_rules!` outside the of the current function `inner_sentinels_detected`
[INFO] [stdout]     = note: a `macro_rules!` definition is non-local if it is nested inside an item and has a `#[macro_export]` attribute
[INFO] [stdout]     = note: the attribute macro `get` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen`
[INFO] [stdout]     = note: this warning originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `macro_rules!` definition, `#[macro_export]` macro should be written at top level module
[INFO] [stdout]    --> tests/sentinel.rs:268:5
[INFO] [stdout]     |
[INFO] [stdout] 268 |     #[get("/")] fn either_route3() -> Either<(), ResponderSentinel> { todo!() }
[INFO] [stdout]     |     ^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: remove the `#[macro_export]` or move this `macro_rules!` outside the of the current function `inner_sentinels_detected`
[INFO] [stdout]     = note: a `macro_rules!` definition is non-local if it is nested inside an item and has a `#[macro_export]` attribute
[INFO] [stdout]     = note: the attribute macro `get` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen`
[INFO] [stdout]     = note: this warning originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `macro_rules!` definition, `#[macro_export]` macro should be written at top level module
[INFO] [stdout]    --> tests/sentinel.rs:272:5
[INFO] [stdout]     |
[INFO] [stdout] 272 |     #[get("/")] fn either_route4() -> Either<(), ()> { todo!() }
[INFO] [stdout]     |     ^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: remove the `#[macro_export]` or move this `macro_rules!` outside the of the current function `inner_sentinels_detected`
[INFO] [stdout]     = note: a `macro_rules!` definition is non-local if it is nested inside an item and has a `#[macro_export]` attribute
[INFO] [stdout]     = note: the attribute macro `get` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen`
[INFO] [stdout]     = note: this warning originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `macro_rules!` definition, `#[macro_export]` macro should be written at top level module
[INFO] [stdout]    --> tests/sentinel.rs:313:5
[INFO] [stdout]     |
[INFO] [stdout] 313 |     #[get("/text")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: remove the `#[macro_export]` or move this `macro_rules!` outside the of the current async block `<unnameable>` and up 2 bodies
[INFO] [stdout]     = note: a `macro_rules!` definition is non-local if it is nested inside an item and has a `#[macro_export]` attribute
[INFO] [stdout]     = note: the attribute macro `get` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen`
[INFO] [stdout]     = note: this warning originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `macro_rules!` definition, `#[macro_export]` macro should be written at top level module
[INFO] [stdout]    --> tests/sentinel.rs:318:5
[INFO] [stdout]     |
[INFO] [stdout] 318 |     #[get("/<a>")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: remove the `#[macro_export]` or move this `macro_rules!` outside the of the current async block `<unnameable>` and up 2 bodies
[INFO] [stdout]     = note: a `macro_rules!` definition is non-local if it is nested inside an item and has a `#[macro_export]` attribute
[INFO] [stdout]     = note: the attribute macro `get` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen`
[INFO] [stdout]     = note: this warning originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `macro_rules!` definition, `#[macro_export]` macro should be written at top level module
[INFO] [stdout]    --> tests/sentinel.rs:323:5
[INFO] [stdout]     |
[INFO] [stdout] 323 |     #[get("/<_a>/<b>")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: remove the `#[macro_export]` or move this `macro_rules!` outside the of the current async block `<unnameable>` and up 2 bodies
[INFO] [stdout]     = note: a `macro_rules!` definition is non-local if it is nested inside an item and has a `#[macro_export]` attribute
[INFO] [stdout]     = note: the attribute macro `get` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen`
[INFO] [stdout]     = note: this warning originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: non-local `macro_rules!` definition, `#[macro_export]` macro should be written at top level module
[INFO] [stdout]    --> tests/sentinel.rs:332:5
[INFO] [stdout]     |
[INFO] [stdout] 332 |     #[get("/ignore")]
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = help: remove the `#[macro_export]` or move this `macro_rules!` outside the of the current async block `<unnameable>` and up 2 bodies
[INFO] [stdout]     = note: a `macro_rules!` definition is non-local if it is nested inside an item and has a `#[macro_export]` attribute
[INFO] [stdout]     = note: the attribute macro `get` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen`
[INFO] [stdout]     = note: this warning originates in the attribute macro `get` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error: struct `CustomResponder` is never constructed
[INFO] [stdout]   --> tests/responder_lifetime-issue-345.rs:10:12
[INFO] [stdout]    |
[INFO] [stdout] 10 | pub struct CustomResponder<'r, R> {
[INFO] [stdout]    |            ^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: this `pub` struct has private fields, no public constructor, and is not otherwise reachable through the external API, so consider providing a public constructor or removing it
[INFO] [stdout]    = note: `#[deny(unused_unconstructable_pub_structs)]` (part of `#[deny(unused)]`) on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]   --> tests/responder_lifetime-issue-345.rs:22:22
[INFO] [stdout]    |
[INFO] [stdout] 22 | fn unit_state(state: &State<SomeState>) -> CustomResponder<()> {
[INFO] [stdout]    |                      ^^^^^^^^^^^^^^^^^     ^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]    |                      |
[INFO] [stdout]    |                      the lifetime is elided here
[INFO] [stdout]    |
[INFO] [stdout]    = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout]    = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]    |
[INFO] [stdout] 22 | fn unit_state(state: &State<SomeState>) -> CustomResponder<'_, ()> {
[INFO] [stdout]    |                                                            +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]   --> tests/responder_lifetime-issue-345.rs:27:24
[INFO] [stdout]    |
[INFO] [stdout] 27 | fn string_state(state: &State<SomeState>) -> CustomResponder<String> {
[INFO] [stdout]    |                        ^^^^^^^^^^^^^^^^^     ^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here
[INFO] [stdout]    |                        |
[INFO] [stdout]    |                        the lifetime is elided here
[INFO] [stdout]    |
[INFO] [stdout]    = help: the same lifetime is referred to in inconsistent ways, making the signature confusing
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]    |
[INFO] [stdout] 27 | fn string_state(state: &State<SomeState>) -> CustomResponder<'_, String> {
[INFO] [stdout]    |                                                              +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `rocket` (test "responder_lifetime-issue-345") due to 1 previous error; 2 warnings emitted
[INFO] [stderr] warning: build failed, waiting for other jobs to finish...
[INFO] running `Command { std: "docker" "inspect" "ee9d037558ed01584b95df623d6daf0478829a971e5f91bd55589d8c5b31bc1d", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "ee9d037558ed01584b95df623d6daf0478829a971e5f91bd55589d8c5b31bc1d", kill_on_drop: false }`
[INFO] [stdout] ee9d037558ed01584b95df623d6daf0478829a971e5f91bd55589d8c5b31bc1d
