[INFO] cloning repository https://github.com/EeroVakiparta/Leukailu [INFO] running `Command { std: "git" "-c" "credential.helper=" "-c" "credential.helper=/workspace/cargo-home/bin/git-credential-null" "clone" "--bare" "https://github.com/EeroVakiparta/Leukailu" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2FEeroVakiparta%2FLeukailu", kill_on_drop: false }` [INFO] [stderr] Cloning into bare repository '/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2FEeroVakiparta%2FLeukailu'... [INFO] running `Command { std: "git" "rev-parse" "HEAD", kill_on_drop: false }` [INFO] [stdout] 806f0e3cd115ca5df4de5fada03975ab10ac4938 [INFO] testing EeroVakiparta/Leukailu against try#8de4c7234dd9b97c9d76b58671343fdbbc9a433e+target=x86_64-unknown-linux-musl for musl_upgrade_1_2_5_with_libc_patch_0 [INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2FEeroVakiparta%2FLeukailu" "/workspace/builds/worker-2-tc1/source", kill_on_drop: false }` [INFO] [stderr] Cloning into '/workspace/builds/worker-2-tc1/source'... [INFO] [stderr] done. [INFO] started tweaking git repo https://github.com/EeroVakiparta/Leukailu [INFO] finished tweaking git repo https://github.com/EeroVakiparta/Leukailu [INFO] tweaked toml for git repo https://github.com/EeroVakiparta/Leukailu written to /workspace/builds/worker-2-tc1/source/Cargo.toml [INFO] validating manifest of git repo https://github.com/EeroVakiparta/Leukailu on toolchain 8de4c7234dd9b97c9d76b58671343fdbbc9a433e [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] crate git repo https://github.com/EeroVakiparta/Leukailu already has a lockfile, it will not be regenerated [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Downloading crates ... [INFO] [stderr] Downloaded ubyte v0.10.1 [INFO] [stderr] Downloaded tracing-core v0.1.26 [INFO] [stderr] Downloaded uncased v0.9.6 [INFO] [stderr] Downloaded tokio-stream v0.1.8 [INFO] [stderr] Downloaded spin v0.9.3 [INFO] [stderr] Downloaded socket2 v0.4.5 [INFO] [stderr] Downloaded loom v0.5.4 [INFO] [stderr] Downloaded tokio-util v0.7.1 [INFO] [stderr] Downloaded http v0.2.7 [INFO] [stderr] Downloaded h2 v0.3.13 [INFO] [stderr] Downloaded hyper v0.14.18 [INFO] [stderr] Downloaded syn v1.0.92 [INFO] [stderr] Downloaded tokio v1.18.2 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:90999bfc7ae267e83380e433d8e61a7c072ca6729e92edbae886d3423b3a6f4c" "/opt/rustwide/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 8b5c107989971be7474f2eee5bf195e5b062b6008bcd2d974df441c4c5cecddd [INFO] running `Command { std: "docker" "start" "-a" "8b5c107989971be7474f2eee5bf195e5b062b6008bcd2d974df441c4c5cecddd", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "8b5c107989971be7474f2eee5bf195e5b062b6008bcd2d974df441c4c5cecddd", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "8b5c107989971be7474f2eee5bf195e5b062b6008bcd2d974df441c4c5cecddd", kill_on_drop: false }` [INFO] [stdout] 8b5c107989971be7474f2eee5bf195e5b062b6008bcd2d974df441c4c5cecddd [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:90999bfc7ae267e83380e433d8e61a7c072ca6729e92edbae886d3423b3a6f4c" "/opt/rustwide/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "build" "--frozen" "--message-format=json" "--target" "x86_64-unknown-linux-musl", kill_on_drop: false }` [INFO] [stdout] 55d775744e0a36caa581c307002570458483c9ffa823c2b7f8ee9e762d8694d1 [INFO] running `Command { std: "docker" "start" "-a" "55d775744e0a36caa581c307002570458483c9ffa823c2b7f8ee9e762d8694d1", kill_on_drop: false }` [INFO] [stderr] Compiling typenum v1.15.0 [INFO] [stderr] Compiling libc v0.2.125 [INFO] [stderr] Compiling proc-macro2 v1.0.38 [INFO] [stderr] Compiling generic-array v0.14.5 [INFO] [stderr] Compiling unicode-xid v0.2.3 [INFO] [stderr] Compiling syn v1.0.92 [INFO] [stderr] Compiling futures-channel v0.3.21 [INFO] [stderr] Compiling futures-core v0.3.21 [INFO] [stderr] Compiling proc-macro2-diagnostics v0.9.1 [INFO] [stderr] Compiling log v0.4.17 [INFO] [stderr] Compiling pin-project-lite v0.2.9 [INFO] [stderr] Compiling subtle v2.4.1 [INFO] [stderr] Compiling yansi v0.5.1 [INFO] [stderr] Compiling serde v1.0.137 [INFO] [stderr] Compiling bytes v1.1.0 [INFO] [stderr] Compiling httparse v1.7.1 [INFO] [stderr] Compiling itoa v1.0.1 [INFO] [stderr] Compiling futures-sink v0.3.21 [INFO] [stderr] Compiling cpufeatures v0.2.2 [INFO] [stderr] Compiling futures-task v0.3.21 [INFO] [stderr] Compiling once_cell v1.10.0 [INFO] [stderr] Compiling cookie v0.16.0 [INFO] [stderr] Compiling futures-util v0.3.21 [INFO] [stderr] Compiling opaque-debug v0.3.0 [INFO] [stderr] Compiling ref-cast v1.0.7 [INFO] [stderr] Compiling time-macros v0.2.4 [INFO] [stderr] Compiling futures-io v0.3.21 [INFO] [stderr] Compiling tracing-core v0.1.26 [INFO] [stderr] Compiling http v0.2.7 [INFO] [stderr] Compiling indexmap v1.8.1 [INFO] [stderr] Compiling ppv-lite86 v0.2.16 [INFO] [stderr] Compiling lazy_static v1.4.0 [INFO] [stderr] Compiling pin-utils v0.1.0 [INFO] [stderr] Compiling uncased v0.9.6 [INFO] [stderr] Compiling signal-hook-registry v1.4.0 [INFO] [stderr] Compiling socket2 v0.4.5 [INFO] [stderr] Compiling num_cpus v1.13.1 [INFO] [stderr] Compiling mio v0.8.3 [INFO] [stderr] Compiling getrandom v0.2.6 [INFO] [stderr] Compiling quote v1.0.18 [INFO] [stderr] Compiling rand_core v0.6.3 [INFO] [stderr] Compiling num_threads v0.1.6 [INFO] [stderr] Compiling try-lock v0.2.3 [INFO] [stderr] Compiling bitflags v1.3.2 [INFO] [stderr] Compiling rand_chacha v0.3.1 [INFO] [stderr] Compiling http-body v0.4.4 [INFO] [stderr] Compiling crypto-common v0.1.3 [INFO] [stderr] Compiling block-buffer v0.10.2 [INFO] [stderr] Compiling cipher v0.3.0 [INFO] [stderr] Compiling universal-hash v0.4.1 [INFO] [stderr] Compiling aead v0.4.3 [INFO] [stderr] Compiling want v0.3.0 [INFO] [stderr] Compiling digest v0.10.3 [INFO] [stderr] Compiling polyval v0.5.3 [INFO] [stderr] Compiling tracing v0.1.34 [INFO] [stderr] Compiling ctr v0.8.0 [INFO] [stderr] Compiling aes v0.7.5 [INFO] [stderr] Compiling ghash v0.4.4 [INFO] [stderr] Compiling tokio v1.18.2 [INFO] [stderr] Compiling time v0.3.9 [INFO] [stderr] Compiling rand v0.8.5 [INFO] [stderr] Compiling hmac v0.12.1 [INFO] [stderr] Compiling sha2 v0.10.2 [INFO] [stderr] Compiling hkdf v0.12.3 [INFO] [stderr] Compiling aes-gcm v0.9.4 [INFO] [stderr] Compiling tower-service v0.3.1 [INFO] [stderr] Compiling inlinable_string v0.1.15 [INFO] [stderr] Compiling httpdate v1.0.2 [INFO] [stderr] Compiling parking_lot_core v0.9.3 [INFO] [stderr] Compiling smallvec v1.8.0 [INFO] [stderr] Compiling base64 v0.13.0 [INFO] [stderr] Compiling hashbrown v0.11.2 [INFO] [stderr] Compiling percent-encoding v2.1.0 [INFO] [stderr] Compiling encoding_rs v0.8.31 [INFO] [stderr] Compiling futures v0.3.21 [INFO] [stderr] Compiling stable-pattern v0.1.0 [INFO] [stderr] Compiling atomic v0.5.1 [INFO] [stderr] Compiling multer v2.0.2 [INFO] [stderr] Compiling figment v0.10.6 [INFO] [stderr] Compiling serde_json v1.0.81 [INFO] [stderr] Compiling either v1.6.1 [INFO] [stderr] Compiling state v0.5.3 [INFO] [stderr] Compiling async-trait v0.1.53 [INFO] [stderr] Compiling rocket v0.5.0-rc.1 (/opt/rustwide/workdir/core/lib) [INFO] [stderr] Compiling fastrand v1.7.0 [INFO] [stderr] Compiling spin v0.9.3 [INFO] [stderr] Compiling glob v0.3.0 [INFO] [stderr] Compiling ryu v1.0.9 [INFO] [stderr] Compiling remove_dir_all v0.5.3 [INFO] [stderr] Compiling tempfile v3.3.0 [INFO] [stderr] Compiling parking_lot v0.12.0 [INFO] [stderr] Compiling atty v0.2.14 [INFO] [stderr] Compiling binascii v0.1.4 [INFO] [stderr] Compiling hyper v0.14.18 [INFO] [stderr] Compiling devise_core v0.3.1 [INFO] [stderr] Compiling serde_derive v1.0.137 [INFO] [stderr] Compiling tokio-macros v1.7.0 [INFO] [stderr] Compiling pear_codegen v0.2.3 [INFO] [stderr] Compiling tracing-attributes v0.1.21 [INFO] [stderr] Compiling ref-cast-impl v1.0.7 [INFO] [stderr] Compiling async-stream-impl v0.3.3 [INFO] [stderr] Compiling devise_codegen v0.3.1 [INFO] [stderr] Compiling async-stream v0.3.3 [INFO] [stderr] Compiling pear v0.2.3 [INFO] [stderr] Compiling devise v0.3.1 [INFO] [stderr] Compiling rocket_http v0.5.0-rc.1 (/opt/rustwide/workdir/core/http) [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> core/http/src/uri/uri.rs:82:30 [INFO] [stdout] | [INFO] [stdout] 82 | pub fn parse(string: &'a str) -> Result, Error<'_>> [INFO] [stdout] | ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | [INFO] [stdout] | | the lifetimes get resolved as `'a` [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 82 - pub fn parse(string: &'a str) -> Result, Error<'_>> [INFO] [stdout] 82 + pub fn parse(string: &'a str) -> Result, Error<'a>> [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> core/http/src/uri/uri.rs:130:31 [INFO] [stdout] | [INFO] [stdout] 130 | pub fn parse_any(string: &'a str) -> Result, Error<'_>> { [INFO] [stdout] | ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | [INFO] [stdout] | | the lifetimes get resolved as `'a` [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 130 - pub fn parse_any(string: &'a str) -> Result, Error<'_>> { [INFO] [stdout] 130 + pub fn parse_any(string: &'a str) -> Result, Error<'a>> { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Compiling rocket_codegen v0.5.0-rc.1 (/opt/rustwide/workdir/core/codegen) [INFO] [stderr] Compiling tokio-util v0.7.1 [INFO] [stderr] Compiling tokio-util v0.6.9 [INFO] [stderr] Compiling tokio-stream v0.1.8 [INFO] [stdout] warning: variable does not need to be mutable [INFO] [stdout] --> core/codegen/src/bang/uri.rs:26:9 [INFO] [stdout] | [INFO] [stdout] 26 | let mut last_seg = path.segments.last_mut().expect("syn::Path has segments"); [INFO] [stdout] | ----^^^^^^^^ [INFO] [stdout] | | [INFO] [stdout] | help: remove this `mut` [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(unused_mut)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: field `0` is never read [INFO] [stdout] --> core/codegen/src/bang/uri_parsing.rs:88:18 [INFO] [stdout] | [INFO] [stdout] 88 | NamedIgnored(Vec<&'a Dynamic>), [INFO] [stdout] | ------------ ^^^^^^^^^^^^^^^^ [INFO] [stdout] | | [INFO] [stdout] | field in this variant [INFO] [stdout] | [INFO] [stdout] = note: `Validation` has a derived impl for the trait `Debug`, but this is intentionally ignored during dead code analysis [INFO] [stdout] = note: `#[warn(dead_code)]` on by default [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] 88 - NamedIgnored(Vec<&'a Dynamic>), [INFO] [stdout] 88 + NamedIgnored(()), [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: trait `TokenStreamExt` is never used [INFO] [stdout] --> core/codegen/src/syn_ext.rs:24:11 [INFO] [stdout] | [INFO] [stdout] 24 | pub trait TokenStreamExt { [INFO] [stdout] | ^^^^^^^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: method `unfold` is never used [INFO] [stdout] --> core/codegen/src/syn_ext.rs:34:8 [INFO] [stdout] | [INFO] [stdout] 33 | pub trait TypeExt { [INFO] [stdout] | ------- method in this trait [INFO] [stdout] 34 | fn unfold(&self) -> Vec>; [INFO] [stdout] | ^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Compiling toml v0.5.9 [INFO] [stderr] Compiling ubyte v0.10.1 [INFO] [stderr] Compiling h2 v0.3.13 [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> core/http/src/uri/uri.rs:82:30 [INFO] [stdout] | [INFO] [stdout] 82 | pub fn parse(string: &'a str) -> Result, Error<'_>> [INFO] [stdout] | ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | [INFO] [stdout] | | the lifetimes get resolved as `'a` [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 82 - pub fn parse(string: &'a str) -> Result, Error<'_>> [INFO] [stdout] 82 + pub fn parse(string: &'a str) -> Result, Error<'a>> [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> core/http/src/uri/uri.rs:130:31 [INFO] [stdout] | [INFO] [stdout] 130 | pub fn parse_any(string: &'a str) -> Result, Error<'_>> { [INFO] [stdout] | ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | [INFO] [stdout] | | the lifetimes get resolved as `'a` [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 130 - pub fn parse_any(string: &'a str) -> Result, Error<'_>> { [INFO] [stdout] 130 + pub fn parse_any(string: &'a str) -> Result, Error<'a>> { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> core/lib/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 31 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 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] --> core/lib/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 for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> core/lib/src/outcome.rs:676:1 [INFO] [stdout] | [INFO] [stdout] 676 | / crate::export! { [INFO] [stdout] 677 | | /// Unwraps a [`Success`](Outcome::Success) or propagates a `Forward` or [INFO] [stdout] 678 | | /// `Failure`. [INFO] [stdout] 679 | | /// [INFO] [stdout] ... | [INFO] [stdout] 757 | | } [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] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see 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] --> core/lib/src/local/request.rs:248:16 [INFO] [stdout] | [INFO] [stdout] 248 | #[cfg_attr(nightly, doc(cfg(feature = "json")))] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: core/lib/src/local/asynchronous/request.rs:122:5 [INFO] [stdout] | [INFO] [stdout] 122 | / pub_request_impl!("# use rocket::local::asynchronous::Client;\n\ [INFO] [stdout] 123 | | use rocket::local::asynchronous::LocalRequest;" async await); [INFO] [stdout] | |____________________________________________________________________- in this macro invocation [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 for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `pub_request_impl` (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] --> core/lib/src/local/response.rs:136:16 [INFO] [stdout] | [INFO] [stdout] 136 | #[cfg_attr(nightly, doc(cfg(feature = "json")))] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: core/lib/src/local/asynchronous/response.rs:189:5 [INFO] [stdout] | [INFO] [stdout] 189 | / pub_response_impl!("# use rocket::local::asynchronous::Client;\n\ [INFO] [stdout] 190 | | use rocket::local::asynchronous::LocalResponse;" async await); [INFO] [stdout] | |_____________________________________________________________________- in this macro invocation [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 for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `pub_response_impl` (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] --> core/lib/src/local/request.rs:248:16 [INFO] [stdout] | [INFO] [stdout] 248 | #[cfg_attr(nightly, doc(cfg(feature = "json")))] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: core/lib/src/local/blocking/request.rs:64:5 [INFO] [stdout] | [INFO] [stdout] 64 | / pub_request_impl!("# use rocket::local::blocking::Client;\n\ [INFO] [stdout] 65 | | use rocket::local::blocking::LocalRequest;"); [INFO] [stdout] | |____________________________________________________- in this macro invocation [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 for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `pub_request_impl` (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] --> core/lib/src/local/response.rs:136:16 [INFO] [stdout] | [INFO] [stdout] 136 | #[cfg_attr(nightly, doc(cfg(feature = "json")))] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: core/lib/src/local/blocking/response.rs:89:5 [INFO] [stdout] | [INFO] [stdout] 89 | / pub_response_impl!("# use rocket::local::blocking::Client;\n\ [INFO] [stdout] 90 | | use rocket::local::blocking::LocalResponse;"); [INFO] [stdout] | |_____________________________________________________- in this macro invocation [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 for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `pub_response_impl` (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] --> core/lib/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`) 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] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see 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] --> core/lib/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] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see 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] --> core/lib/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] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see 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] --> core/lib/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] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see 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] --> core/lib/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] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see 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] --> core/lib/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] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see 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] --> core/lib/src/response/stream/sse.rs:578:1 [INFO] [stdout] | [INFO] [stdout] 578 | / crate::export! { [INFO] [stdout] 579 | | /// Type and stream expression macro for [`struct@EventStream`]. [INFO] [stdout] 580 | | /// [INFO] [stdout] 581 | | /// See [`stream!`](crate::response::stream::stream) for the syntax [INFO] [stdout] ... | [INFO] [stdout] 592 | | } [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] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see 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] --> core/lib/src/response/stream/sse.rs:163:16 [INFO] [stdout] | [INFO] [stdout] 163 | #[cfg_attr(nightly, doc(cfg(feature = "json")))] [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 for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> core/lib/src/config/config.rs:89:16 [INFO] [stdout] | [INFO] [stdout] 89 | #[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 for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> core/lib/src/config/config.rs:96:16 [INFO] [stdout] | [INFO] [stdout] 96 | #[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 for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> core/lib/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 for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> core/lib/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 for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> core/lib/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] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see 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] --> core/lib/src/serde/mod.rs:46:12 [INFO] [stdout] | [INFO] [stdout] 46 | #[cfg_attr(nightly, doc(cfg(feature = "json")))] [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 for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> core/lib/src/serde/json.rs:306:1 [INFO] [stdout] | [INFO] [stdout] 306 | / crate::export! { [INFO] [stdout] 307 | | /// A macro to create ad-hoc JSON serializable values using JSON syntax. [INFO] [stdout] 308 | | /// [INFO] [stdout] 309 | | /// The return type of a `json!` invocation is [`Value`](Value). A value [INFO] [stdout] ... | [INFO] [stdout] 389 | | } [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] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see 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] --> core/lib/src/fs/server.rs:399:1 [INFO] [stdout] | [INFO] [stdout] 399 | / crate::export! { [INFO] [stdout] 400 | | /// Generates a crate-relative version of a path. [INFO] [stdout] 401 | | /// [INFO] [stdout] 402 | | /// This macro is primarily intended for use with [`FileServer`] to serve [INFO] [stdout] ... | [INFO] [stdout] 447 | | } [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] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see 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: method `name` is never used [INFO] [stdout] --> core/lib/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)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: field `1` is never read [INFO] [stdout] --> core/lib/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: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> core/lib/src/form/context.rs:223:33 [INFO] [stdout] | [INFO] [stdout] 223 | pub fn field_errors<'a, N>(&'a self, name: N) -> impl Iterator> + '_ [INFO] [stdout] | ^^ ---------- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | [INFO] [stdout] | this lifetime flows to the output the lifetimes get resolved as `'a` [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 223 - pub fn field_errors<'a, N>(&'a self, name: N) -> impl Iterator> + '_ [INFO] [stdout] 223 + pub fn field_errors<'a, N>(&'a self, name: N) -> impl Iterator> + 'a [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> core/lib/src/form/context.rs:272:39 [INFO] [stdout] | [INFO] [stdout] 272 | pub fn exact_field_errors<'a, N>(&'a self, name: N) -> impl Iterator> + '_ [INFO] [stdout] | ^^ ---------- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | [INFO] [stdout] | this lifetime flows to the output the lifetimes get resolved as `'a` [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 272 - pub fn exact_field_errors<'a, N>(&'a self, name: N) -> impl Iterator> + '_ [INFO] [stdout] 272 + pub fn exact_field_errors<'a, N>(&'a self, name: N) -> impl Iterator> + 'a [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Compiling Leukailu v0.1.0 (/opt/rustwide/workdir) [INFO] [stdout] warning: lint `private_in_public` has been removed: replaced with another group of lints, see RFC for more information [INFO] [stdout] --> src/main.rs:14:1 [INFO] [stdout] | [INFO] [stdout] 14 | / #[serde(crate = "rocket::serde")] [INFO] [stdout] 15 | | struct Message { [INFO] [stdout] 16 | | #[field(validate = len(..30))] [INFO] [stdout] 17 | | pub room: String, [INFO] [stdout] ... | [INFO] [stdout] 20 | | pub message: String, [INFO] [stdout] 21 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(renamed_and_removed_lints)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 1m 13s [INFO] [stderr] warning: the following packages contain code that will be rejected by a future version of Rust: ubyte v0.10.1 [INFO] [stderr] note: to see what the problems were, use the option `--future-incompat-report`, or run `cargo report future-incompatibilities --id 1` [INFO] running `Command { std: "docker" "inspect" "55d775744e0a36caa581c307002570458483c9ffa823c2b7f8ee9e762d8694d1", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "55d775744e0a36caa581c307002570458483c9ffa823c2b7f8ee9e762d8694d1", kill_on_drop: false }` [INFO] [stdout] 55d775744e0a36caa581c307002570458483c9ffa823c2b7f8ee9e762d8694d1 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:90999bfc7ae267e83380e433d8e61a7c072ca6729e92edbae886d3423b3a6f4c" "/opt/rustwide/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "test" "--frozen" "--no-run" "--message-format=json" "--target" "x86_64-unknown-linux-musl", kill_on_drop: false }` [INFO] [stdout] 0f765aa30b552ddeba04dbd94e9225a1f3fd20683a9c8fc414414c6f7c7773a2 [INFO] running `Command { std: "docker" "start" "-a" "0f765aa30b552ddeba04dbd94e9225a1f3fd20683a9c8fc414414c6f7c7773a2", kill_on_drop: false }` [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> core/http/src/uri/uri.rs:82:30 [INFO] [stdout] | [INFO] [stdout] 82 | pub fn parse(string: &'a str) -> Result, Error<'_>> [INFO] [stdout] | ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | [INFO] [stdout] | | the lifetimes get resolved as `'a` [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 82 - pub fn parse(string: &'a str) -> Result, Error<'_>> [INFO] [stdout] 82 + pub fn parse(string: &'a str) -> Result, Error<'a>> [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> core/http/src/uri/uri.rs:130:31 [INFO] [stdout] | [INFO] [stdout] 130 | pub fn parse_any(string: &'a str) -> Result, Error<'_>> { [INFO] [stdout] | ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | [INFO] [stdout] | | the lifetimes get resolved as `'a` [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 130 - pub fn parse_any(string: &'a str) -> Result, Error<'_>> { [INFO] [stdout] 130 + pub fn parse_any(string: &'a str) -> Result, Error<'a>> { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> core/http/src/uri/uri.rs:82:30 [INFO] [stdout] | [INFO] [stdout] 82 | pub fn parse(string: &'a str) -> Result, Error<'_>> [INFO] [stdout] | ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | [INFO] [stdout] | | the lifetimes get resolved as `'a` [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 82 - pub fn parse(string: &'a str) -> Result, Error<'_>> [INFO] [stdout] 82 + pub fn parse(string: &'a str) -> Result, Error<'a>> [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> core/http/src/uri/uri.rs:130:31 [INFO] [stdout] | [INFO] [stdout] 130 | pub fn parse_any(string: &'a str) -> Result, Error<'_>> { [INFO] [stdout] | ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | [INFO] [stdout] | | the lifetimes get resolved as `'a` [INFO] [stdout] | this lifetime flows to the output [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 130 - pub fn parse_any(string: &'a str) -> Result, Error<'_>> { [INFO] [stdout] 130 + pub fn parse_any(string: &'a str) -> Result, Error<'a>> { [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: variable does not need to be mutable [INFO] [stdout] --> core/codegen/src/bang/uri.rs:26:9 [INFO] [stdout] | [INFO] [stdout] 26 | let mut last_seg = path.segments.last_mut().expect("syn::Path has segments"); [INFO] [stdout] | ----^^^^^^^^ [INFO] [stdout] | | [INFO] [stdout] | help: remove this `mut` [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(unused_mut)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: field `0` is never read [INFO] [stdout] --> core/codegen/src/bang/uri_parsing.rs:88:18 [INFO] [stdout] | [INFO] [stdout] 88 | NamedIgnored(Vec<&'a Dynamic>), [INFO] [stdout] | ------------ ^^^^^^^^^^^^^^^^ [INFO] [stdout] | | [INFO] [stdout] | field in this variant [INFO] [stdout] | [INFO] [stdout] = note: `Validation` has a derived impl for the trait `Debug`, but this is intentionally ignored during dead code analysis [INFO] [stdout] = note: `#[warn(dead_code)]` on by default [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] 88 - NamedIgnored(Vec<&'a Dynamic>), [INFO] [stdout] 88 + NamedIgnored(()), [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: trait `TokenStreamExt` is never used [INFO] [stdout] --> core/codegen/src/syn_ext.rs:24:11 [INFO] [stdout] | [INFO] [stdout] 24 | pub trait TokenStreamExt { [INFO] [stdout] | ^^^^^^^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: method `unfold` is never used [INFO] [stdout] --> core/codegen/src/syn_ext.rs:34:8 [INFO] [stdout] | [INFO] [stdout] 33 | pub trait TypeExt { [INFO] [stdout] | ------- method in this trait [INFO] [stdout] 34 | fn unfold(&self) -> Vec>; [INFO] [stdout] | ^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> core/lib/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 31 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 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] --> core/lib/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 for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> core/lib/src/outcome.rs:676:1 [INFO] [stdout] | [INFO] [stdout] 676 | / crate::export! { [INFO] [stdout] 677 | | /// Unwraps a [`Success`](Outcome::Success) or propagates a `Forward` or [INFO] [stdout] 678 | | /// `Failure`. [INFO] [stdout] 679 | | /// [INFO] [stdout] ... | [INFO] [stdout] 757 | | } [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] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see 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] --> core/lib/src/local/request.rs:248:16 [INFO] [stdout] | [INFO] [stdout] 248 | #[cfg_attr(nightly, doc(cfg(feature = "json")))] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: core/lib/src/local/asynchronous/request.rs:122:5 [INFO] [stdout] | [INFO] [stdout] 122 | / pub_request_impl!("# use rocket::local::asynchronous::Client;\n\ [INFO] [stdout] 123 | | use rocket::local::asynchronous::LocalRequest;" async await); [INFO] [stdout] | |____________________________________________________________________- in this macro invocation [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 for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `pub_request_impl` (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] --> core/lib/src/local/response.rs:136:16 [INFO] [stdout] | [INFO] [stdout] 136 | #[cfg_attr(nightly, doc(cfg(feature = "json")))] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: core/lib/src/local/asynchronous/response.rs:189:5 [INFO] [stdout] | [INFO] [stdout] 189 | / pub_response_impl!("# use rocket::local::asynchronous::Client;\n\ [INFO] [stdout] 190 | | use rocket::local::asynchronous::LocalResponse;" async await); [INFO] [stdout] | |_____________________________________________________________________- in this macro invocation [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 for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `pub_response_impl` (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] --> core/lib/src/local/request.rs:248:16 [INFO] [stdout] | [INFO] [stdout] 248 | #[cfg_attr(nightly, doc(cfg(feature = "json")))] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: core/lib/src/local/blocking/request.rs:64:5 [INFO] [stdout] | [INFO] [stdout] 64 | / pub_request_impl!("# use rocket::local::blocking::Client;\n\ [INFO] [stdout] 65 | | use rocket::local::blocking::LocalRequest;"); [INFO] [stdout] | |____________________________________________________- in this macro invocation [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 for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `pub_request_impl` (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] --> core/lib/src/local/response.rs:136:16 [INFO] [stdout] | [INFO] [stdout] 136 | #[cfg_attr(nightly, doc(cfg(feature = "json")))] [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: core/lib/src/local/blocking/response.rs:89:5 [INFO] [stdout] | [INFO] [stdout] 89 | / pub_response_impl!("# use rocket::local::blocking::Client;\n\ [INFO] [stdout] 90 | | use rocket::local::blocking::LocalResponse;"); [INFO] [stdout] | |_____________________________________________________- in this macro invocation [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 for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `pub_response_impl` (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] --> core/lib/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`) 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] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see 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] --> core/lib/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] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see 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] --> core/lib/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] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see 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] --> core/lib/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] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see 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] --> core/lib/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] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see 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] --> core/lib/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] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see 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] --> core/lib/src/response/stream/sse.rs:578:1 [INFO] [stdout] | [INFO] [stdout] 578 | / crate::export! { [INFO] [stdout] 579 | | /// Type and stream expression macro for [`struct@EventStream`]. [INFO] [stdout] 580 | | /// [INFO] [stdout] 581 | | /// See [`stream!`](crate::response::stream::stream) for the syntax [INFO] [stdout] ... | [INFO] [stdout] 592 | | } [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] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see 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] --> core/lib/src/response/stream/sse.rs:163:16 [INFO] [stdout] | [INFO] [stdout] 163 | #[cfg_attr(nightly, doc(cfg(feature = "json")))] [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 for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> core/lib/src/config/config.rs:89:16 [INFO] [stdout] | [INFO] [stdout] 89 | #[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 for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> core/lib/src/config/config.rs:96:16 [INFO] [stdout] | [INFO] [stdout] 96 | #[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 for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> core/lib/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 for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> core/lib/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 for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> core/lib/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] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see 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] --> core/lib/src/serde/mod.rs:46:12 [INFO] [stdout] | [INFO] [stdout] 46 | #[cfg_attr(nightly, doc(cfg(feature = "json")))] [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 for more information about checking conditional configuration [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `nightly` [INFO] [stdout] --> core/lib/src/serde/json.rs:306:1 [INFO] [stdout] | [INFO] [stdout] 306 | / crate::export! { [INFO] [stdout] 307 | | /// A macro to create ad-hoc JSON serializable values using JSON syntax. [INFO] [stdout] 308 | | /// [INFO] [stdout] 309 | | /// The return type of a `json!` invocation is [`Value`](Value). A value [INFO] [stdout] ... | [INFO] [stdout] 389 | | } [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] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see 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] --> core/lib/src/fs/server.rs:399:1 [INFO] [stdout] | [INFO] [stdout] 399 | / crate::export! { [INFO] [stdout] 400 | | /// Generates a crate-relative version of a path. [INFO] [stdout] 401 | | /// [INFO] [stdout] 402 | | /// This macro is primarily intended for use with [`FileServer`] to serve [INFO] [stdout] ... | [INFO] [stdout] 447 | | } [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] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stdout] = note: see 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: method `name` is never used [INFO] [stdout] --> core/lib/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)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: field `1` is never read [INFO] [stdout] --> core/lib/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] [stderr] Compiling Leukailu v0.1.0 (/opt/rustwide/workdir) [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> core/lib/src/form/context.rs:223:33 [INFO] [stdout] | [INFO] [stdout] 223 | pub fn field_errors<'a, N>(&'a self, name: N) -> impl Iterator> + '_ [INFO] [stdout] | ^^ ---------- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | [INFO] [stdout] | this lifetime flows to the output the lifetimes get resolved as `'a` [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 223 - pub fn field_errors<'a, N>(&'a self, name: N) -> impl Iterator> + '_ [INFO] [stdout] 223 + pub fn field_errors<'a, N>(&'a self, name: N) -> impl Iterator> + 'a [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stdout] --> core/lib/src/form/context.rs:272:39 [INFO] [stdout] | [INFO] [stdout] 272 | pub fn exact_field_errors<'a, N>(&'a self, name: N) -> impl Iterator> + '_ [INFO] [stdout] | ^^ ---------- -- the lifetimes get resolved as `'a` [INFO] [stdout] | | | [INFO] [stdout] | this lifetime flows to the output the lifetimes get resolved as `'a` [INFO] [stdout] | [INFO] [stdout] help: one option is to consistently use `'a` [INFO] [stdout] | [INFO] [stdout] 272 - pub fn exact_field_errors<'a, N>(&'a self, name: N) -> impl Iterator> + '_ [INFO] [stdout] 272 + pub fn exact_field_errors<'a, N>(&'a self, name: N) -> impl Iterator> + 'a [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: lint `private_in_public` has been removed: replaced with another group of lints, see RFC for more information [INFO] [stdout] --> src/main.rs:13:1 [INFO] [stdout] | [INFO] [stdout] 13 | / #[cfg_attr(test, derive(PartialEq, UriDisplayQuery))] [INFO] [stdout] 14 | | #[serde(crate = "rocket::serde")] [INFO] [stdout] 15 | | struct Message { [INFO] [stdout] 16 | | #[field(validate = len(..30))] [INFO] [stdout] ... | [INFO] [stdout] 20 | | pub message: String, [INFO] [stdout] 21 | | } [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(renamed_and_removed_lints)]` on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Finished `test` profile [unoptimized + debuginfo] target(s) in 4.63s [INFO] [stderr] warning: the following packages contain code that will be rejected by a future version of Rust: ubyte v0.10.1 [INFO] [stderr] note: to see what the problems were, use the option `--future-incompat-report`, or run `cargo report future-incompatibilities --id 1` [INFO] running `Command { std: "docker" "inspect" "0f765aa30b552ddeba04dbd94e9225a1f3fd20683a9c8fc414414c6f7c7773a2", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "0f765aa30b552ddeba04dbd94e9225a1f3fd20683a9c8fc414414c6f7c7773a2", kill_on_drop: false }` [INFO] [stdout] 0f765aa30b552ddeba04dbd94e9225a1f3fd20683a9c8fc414414c6f7c7773a2 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-2-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:90999bfc7ae267e83380e433d8e61a7c072ca6729e92edbae886d3423b3a6f4c" "/opt/rustwide/cargo-home/bin/cargo" "+8de4c7234dd9b97c9d76b58671343fdbbc9a433e" "test" "--frozen" "--target" "x86_64-unknown-linux-musl", kill_on_drop: false }` [INFO] [stdout] 0c59e1f188a24c7626989f398e3768fad4d45e9f54d43cbe979a9c879f5d49fd [INFO] running `Command { std: "docker" "start" "-a" "0c59e1f188a24c7626989f398e3768fad4d45e9f54d43cbe979a9c879f5d49fd", kill_on_drop: false }` [INFO] [stderr] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stderr] --> core/http/src/uri/uri.rs:82:30 [INFO] [stderr] | [INFO] [stderr] 82 | pub fn parse(string: &'a str) -> Result, Error<'_>> [INFO] [stderr] | ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stderr] | | | [INFO] [stderr] | | the lifetimes get resolved as `'a` [INFO] [stderr] | this lifetime flows to the output [INFO] [stderr] | [INFO] [stderr] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stderr] help: one option is to consistently use `'a` [INFO] [stderr] | [INFO] [stderr] 82 - pub fn parse(string: &'a str) -> Result, Error<'_>> [INFO] [stderr] 82 + pub fn parse(string: &'a str) -> Result, Error<'a>> [INFO] [stderr] | [INFO] [stderr] [INFO] [stderr] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stderr] --> core/http/src/uri/uri.rs:130:31 [INFO] [stderr] | [INFO] [stderr] 130 | pub fn parse_any(string: &'a str) -> Result, Error<'_>> { [INFO] [stderr] | ^^ -- -- the lifetimes get resolved as `'a` [INFO] [stderr] | | | [INFO] [stderr] | | the lifetimes get resolved as `'a` [INFO] [stderr] | this lifetime flows to the output [INFO] [stderr] | [INFO] [stderr] help: one option is to consistently use `'a` [INFO] [stderr] | [INFO] [stderr] 130 - pub fn parse_any(string: &'a str) -> Result, Error<'_>> { [INFO] [stderr] 130 + pub fn parse_any(string: &'a str) -> Result, Error<'a>> { [INFO] [stderr] | [INFO] [stderr] [INFO] [stderr] warning: `rocket_http` (lib) generated 2 warnings (run `cargo fix --lib -p rocket_http` to apply 2 suggestions) [INFO] [stderr] warning: variable does not need to be mutable [INFO] [stderr] --> core/codegen/src/bang/uri.rs:26:9 [INFO] [stderr] | [INFO] [stderr] 26 | let mut last_seg = path.segments.last_mut().expect("syn::Path has segments"); [INFO] [stderr] | ----^^^^^^^^ [INFO] [stderr] | | [INFO] [stderr] | help: remove this `mut` [INFO] [stderr] | [INFO] [stderr] = note: `#[warn(unused_mut)]` on by default [INFO] [stderr] [INFO] [stderr] warning: field `0` is never read [INFO] [stderr] --> core/codegen/src/bang/uri_parsing.rs:88:18 [INFO] [stderr] | [INFO] [stderr] 88 | NamedIgnored(Vec<&'a Dynamic>), [INFO] [stderr] | ------------ ^^^^^^^^^^^^^^^^ [INFO] [stderr] | | [INFO] [stderr] | field in this variant [INFO] [stderr] | [INFO] [stderr] = note: `Validation` has a derived impl for the trait `Debug`, but this is intentionally ignored during dead code analysis [INFO] [stderr] = note: `#[warn(dead_code)]` on by default [INFO] [stderr] help: consider changing the field to be of unit type to suppress this warning while preserving the field numbering, or remove the field [INFO] [stderr] | [INFO] [stderr] 88 - NamedIgnored(Vec<&'a Dynamic>), [INFO] [stderr] 88 + NamedIgnored(()), [INFO] [stderr] | [INFO] [stderr] [INFO] [stderr] warning: trait `TokenStreamExt` is never used [INFO] [stderr] --> core/codegen/src/syn_ext.rs:24:11 [INFO] [stderr] | [INFO] [stderr] 24 | pub trait TokenStreamExt { [INFO] [stderr] | ^^^^^^^^^^^^^^ [INFO] [stderr] [INFO] [stderr] warning: method `unfold` is never used [INFO] [stderr] --> core/codegen/src/syn_ext.rs:34:8 [INFO] [stderr] | [INFO] [stderr] 33 | pub trait TypeExt { [INFO] [stderr] | ------- method in this trait [INFO] [stderr] 34 | fn unfold(&self) -> Vec>; [INFO] [stderr] | ^^^^^^ [INFO] [stderr] [INFO] [stderr] warning: `rocket_codegen` (lib) generated 4 warnings (run `cargo fix --lib -p rocket_codegen` to apply 1 suggestion) [INFO] [stderr] warning: `rocket_http` (lib) generated 2 warnings (2 duplicates) [INFO] [stderr] warning: unexpected `cfg` condition name: `nightly` [INFO] [stderr] --> core/lib/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 31 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 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] --> core/lib/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 for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `nightly` [INFO] [stderr] --> core/lib/src/outcome.rs:676:1 [INFO] [stderr] | [INFO] [stderr] 676 | / crate::export! { [INFO] [stderr] 677 | | /// Unwraps a [`Success`](Outcome::Success) or propagates a `Forward` or [INFO] [stderr] 678 | | /// `Failure`. [INFO] [stderr] 679 | | /// [INFO] [stderr] ... | [INFO] [stderr] 757 | | } [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] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stderr] = note: see 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] --> core/lib/src/local/request.rs:248:16 [INFO] [stderr] | [INFO] [stderr] 248 | #[cfg_attr(nightly, doc(cfg(feature = "json")))] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: core/lib/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 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] --> core/lib/src/local/response.rs:136:16 [INFO] [stderr] | [INFO] [stderr] 136 | #[cfg_attr(nightly, doc(cfg(feature = "json")))] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: core/lib/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 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] --> core/lib/src/local/request.rs:248:16 [INFO] [stderr] | [INFO] [stderr] 248 | #[cfg_attr(nightly, doc(cfg(feature = "json")))] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: core/lib/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 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] --> core/lib/src/local/response.rs:136:16 [INFO] [stderr] | [INFO] [stderr] 136 | #[cfg_attr(nightly, doc(cfg(feature = "json")))] [INFO] [stderr] | ^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: core/lib/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 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] --> core/lib/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`) 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] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stderr] = note: see 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] --> core/lib/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] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stderr] = note: see 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] --> core/lib/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] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stderr] = note: see 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] --> core/lib/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] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stderr] = note: see 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] --> core/lib/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] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stderr] = note: see 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] --> core/lib/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] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stderr] = note: see 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] --> core/lib/src/response/stream/sse.rs:578:1 [INFO] [stderr] | [INFO] [stderr] 578 | / crate::export! { [INFO] [stderr] 579 | | /// Type and stream expression macro for [`struct@EventStream`]. [INFO] [stderr] 580 | | /// [INFO] [stderr] 581 | | /// See [`stream!`](crate::response::stream::stream) for the syntax [INFO] [stderr] ... | [INFO] [stderr] 592 | | } [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] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stderr] = note: see 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] --> core/lib/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 for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `nightly` [INFO] [stderr] --> core/lib/src/config/config.rs:89:16 [INFO] [stderr] | [INFO] [stderr] 89 | #[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 for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `nightly` [INFO] [stderr] --> core/lib/src/config/config.rs:96:16 [INFO] [stderr] | [INFO] [stderr] 96 | #[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 for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `nightly` [INFO] [stderr] --> core/lib/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 for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `nightly` [INFO] [stderr] --> core/lib/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 for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `nightly` [INFO] [stderr] --> core/lib/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] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stderr] = note: see 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] --> core/lib/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 for more information about checking conditional configuration [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `nightly` [INFO] [stderr] --> core/lib/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] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stderr] = note: see 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] --> core/lib/src/fs/server.rs:399:1 [INFO] [stderr] | [INFO] [stderr] 399 | / crate::export! { [INFO] [stderr] 400 | | /// Generates a crate-relative version of a path. [INFO] [stderr] 401 | | /// [INFO] [stderr] 402 | | /// This macro is primarily intended for use with [`FileServer`] to serve [INFO] [stderr] ... | [INFO] [stderr] 447 | | } [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] = help: the macro `crate::export` may come from an old version of the `rocket_codegen` crate, try updating your dependency with `cargo update -p rocket_codegen` [INFO] [stderr] = note: see 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: method `name` is never used [INFO] [stderr] --> core/lib/src/shield/policy.rs:69:8 [INFO] [stderr] | [INFO] [stderr] 68 | pub(crate) trait SubPolicy: Send + Sync { [INFO] [stderr] | --------- method in this trait [INFO] [stderr] 69 | fn name(&self) -> &'static UncasedStr; [INFO] [stderr] | ^^^^ [INFO] [stderr] | [INFO] [stderr] = note: `#[warn(dead_code)]` on by default [INFO] [stderr] [INFO] [stderr] warning: field `1` is never read [INFO] [stderr] --> core/lib/src/cookies.rs:173:29 [INFO] [stderr] | [INFO] [stderr] 173 | Remove(Cookie<'static>, bool), [INFO] [stderr] | ------ ^^^^ [INFO] [stderr] | | [INFO] [stderr] | field in this variant [INFO] [stderr] | [INFO] [stderr] = note: `Op` has a derived impl for the trait `Clone`, but this is intentionally ignored during dead code analysis [INFO] [stderr] help: consider changing the field to be of unit type to suppress this warning while preserving the field numbering, or remove the field [INFO] [stderr] | [INFO] [stderr] 173 - Remove(Cookie<'static>, bool), [INFO] [stderr] 173 + Remove(Cookie<'static>, ()), [INFO] [stderr] | [INFO] [stderr] [INFO] [stderr] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stderr] --> core/lib/src/form/context.rs:223:33 [INFO] [stderr] | [INFO] [stderr] 223 | pub fn field_errors<'a, N>(&'a self, name: N) -> impl Iterator> + '_ [INFO] [stderr] | ^^ ---------- -- the lifetimes get resolved as `'a` [INFO] [stderr] | | | [INFO] [stderr] | this lifetime flows to the output the lifetimes get resolved as `'a` [INFO] [stderr] | [INFO] [stderr] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stderr] help: one option is to consistently use `'a` [INFO] [stderr] | [INFO] [stderr] 223 - pub fn field_errors<'a, N>(&'a self, name: N) -> impl Iterator> + '_ [INFO] [stderr] 223 + pub fn field_errors<'a, N>(&'a self, name: N) -> impl Iterator> + 'a [INFO] [stderr] | [INFO] [stderr] [INFO] [stderr] warning: lifetime flowing from input to output with different syntax can be confusing [INFO] [stderr] --> core/lib/src/form/context.rs:272:39 [INFO] [stderr] | [INFO] [stderr] 272 | pub fn exact_field_errors<'a, N>(&'a self, name: N) -> impl Iterator> + '_ [INFO] [stderr] | ^^ ---------- -- the lifetimes get resolved as `'a` [INFO] [stderr] | | | [INFO] [stderr] | this lifetime flows to the output the lifetimes get resolved as `'a` [INFO] [stderr] | [INFO] [stderr] help: one option is to consistently use `'a` [INFO] [stderr] | [INFO] [stderr] 272 - pub fn exact_field_errors<'a, N>(&'a self, name: N) -> impl Iterator> + '_ [INFO] [stderr] 272 + pub fn exact_field_errors<'a, N>(&'a self, name: N) -> impl Iterator> + 'a [INFO] [stderr] | [INFO] [stderr] [INFO] [stderr] warning: `rocket` (lib) generated 27 warnings (run `cargo fix --lib -p rocket` to apply 2 suggestions) [INFO] [stderr] warning: lint `private_in_public` has been removed: replaced with another group of lints, see RFC for more information [INFO] [stderr] --> src/main.rs:13:1 [INFO] [stderr] | [INFO] [stderr] 13 | / #[cfg_attr(test, derive(PartialEq, UriDisplayQuery))] [INFO] [stderr] 14 | | #[serde(crate = "rocket::serde")] [INFO] [stderr] 15 | | struct Message { [INFO] [stderr] 16 | | #[field(validate = len(..30))] [INFO] [stderr] ... | [INFO] [stderr] 20 | | pub message: String, [INFO] [stderr] 21 | | } [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = note: `#[warn(renamed_and_removed_lints)]` on by default [INFO] [stderr] [INFO] [stderr] warning: `Leukailu` (bin "Leukailu" test) generated 1 warning [INFO] [stderr] Finished `test` profile [unoptimized + debuginfo] target(s) in 0.44s [INFO] [stderr] warning: the following packages contain code that will be rejected by a future version of Rust: ubyte v0.10.1 [INFO] [stderr] note: to see what the problems were, use the option `--future-incompat-report`, or run `cargo report future-incompatibilities --id 1` [INFO] [stderr] Running unittests src/main.rs (/opt/rustwide/target/x86_64-unknown-linux-musl/debug/deps/Leukailu-d0497b69db7ce928) [INFO] [stdout] [INFO] [stdout] running 2 tests [INFO] [stdout] test tests::bad_messages ... ok [INFO] [stdout] test tests::messages ... ok [INFO] [stdout] [INFO] [stdout] test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.08s [INFO] [stdout] [INFO] running `Command { std: "docker" "inspect" "0c59e1f188a24c7626989f398e3768fad4d45e9f54d43cbe979a9c879f5d49fd", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "0c59e1f188a24c7626989f398e3768fad4d45e9f54d43cbe979a9c879f5d49fd", kill_on_drop: false }` [INFO] [stdout] 0c59e1f188a24c7626989f398e3768fad4d45e9f54d43cbe979a9c879f5d49fd