[INFO] fetching crate puff-rs 0.1.8... [INFO] testing puff-rs-0.1.8 against beta-2025-09-21 for beta-1.91-3 [INFO] extracting crate puff-rs 0.1.8 into /workspace/builds/worker-6-tc2/source [INFO] started tweaking crates.io crate puff-rs 0.1.8 [INFO] removed 0 missing examples [INFO] finished tweaking crates.io crate puff-rs 0.1.8 [INFO] tweaked toml for crates.io crate puff-rs 0.1.8 written to /workspace/builds/worker-6-tc2/source/Cargo.toml [INFO] validating manifest of crates.io crate puff-rs 0.1.8 on toolchain beta-2025-09-21 [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+beta-2025-09-21" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] crate crates.io crate puff-rs 0.1.8 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" "+beta-2025-09-21" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+beta-2025-09-21" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 9a50b9a11d600bc725e25fcfb1a7be2bfc8e16cda0f070e3c9526e84bf7d5a6b [INFO] running `Command { std: "docker" "start" "-a" "9a50b9a11d600bc725e25fcfb1a7be2bfc8e16cda0f070e3c9526e84bf7d5a6b", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "9a50b9a11d600bc725e25fcfb1a7be2bfc8e16cda0f070e3c9526e84bf7d5a6b", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "9a50b9a11d600bc725e25fcfb1a7be2bfc8e16cda0f070e3c9526e84bf7d5a6b", kill_on_drop: false }` [INFO] [stdout] 9a50b9a11d600bc725e25fcfb1a7be2bfc8e16cda0f070e3c9526e84bf7d5a6b [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "RUSTDOCFLAGS=--cap-lints=warn" "-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:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+beta-2025-09-21" "build" "--frozen" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] c4e52b4586f09c3935aedebe8402131a08f92c3364cb4a3583020b31c6b2a26e [INFO] running `Command { std: "docker" "start" "-a" "c4e52b4586f09c3935aedebe8402131a08f92c3364cb4a3583020b31c6b2a26e", kill_on_drop: false }` [INFO] [stderr] Compiling proc-macro2 v1.0.47 [INFO] [stderr] Compiling unicode-ident v1.0.5 [INFO] [stderr] Compiling quote v1.0.21 [INFO] [stderr] Compiling syn v1.0.103 [INFO] [stderr] Compiling autocfg v1.1.0 [INFO] [stderr] Compiling libc v0.2.137 [INFO] [stderr] Compiling version_check v0.9.4 [INFO] [stderr] Compiling memchr v2.5.0 [INFO] [stderr] Compiling once_cell v1.16.0 [INFO] [stderr] Compiling log v0.4.17 [INFO] [stderr] Compiling bytes v1.2.1 [INFO] [stderr] Compiling itoa v1.0.4 [INFO] [stderr] Compiling pin-project-lite v0.2.9 [INFO] [stderr] Compiling serde_derive v1.0.147 [INFO] [stderr] Compiling futures-core v0.3.25 [INFO] [stderr] Compiling smallvec v1.10.0 [INFO] [stderr] Compiling lock_api v0.4.9 [INFO] [stderr] Compiling parking_lot_core v0.9.4 [INFO] [stderr] Compiling serde v1.0.147 [INFO] [stderr] Compiling scopeguard v1.1.0 [INFO] [stderr] Compiling futures-sink v0.3.25 [INFO] [stderr] Compiling slab v0.4.7 [INFO] [stderr] Compiling futures-task v0.3.25 [INFO] [stderr] Compiling futures-channel v0.3.25 [INFO] [stderr] Compiling tinyvec_macros v0.1.0 [INFO] [stderr] Compiling tinyvec v1.6.0 [INFO] [stderr] Compiling tokio v1.21.2 [INFO] [stderr] Compiling futures-util v0.3.25 [INFO] [stderr] Compiling futures-io v0.3.25 [INFO] [stderr] Compiling unicode-bidi v0.3.8 [INFO] [stderr] Compiling mio v0.8.5 [INFO] [stderr] Compiling signal-hook-registry v1.4.0 [INFO] [stderr] Compiling num_cpus v1.13.1 [INFO] [stderr] Compiling parking_lot v0.12.1 [INFO] [stderr] Compiling socket2 v0.4.7 [INFO] [stderr] Compiling typenum v1.15.0 [INFO] [stderr] Compiling generic-array v0.14.6 [INFO] [stderr] Compiling percent-encoding v2.2.0 [INFO] [stderr] Compiling getrandom v0.2.8 [INFO] [stderr] Compiling indexmap v1.9.1 [INFO] [stderr] Compiling tracing-core v0.1.30 [INFO] [stderr] Compiling unicode-normalization v0.1.22 [INFO] [stderr] Compiling ryu v1.0.11 [INFO] [stderr] Compiling hashbrown v0.12.3 [INFO] [stderr] Compiling rand_core v0.6.4 [INFO] [stderr] Compiling subtle v2.4.1 [INFO] [stderr] Compiling cc v1.0.74 [INFO] [stderr] Compiling ppv-lite86 v0.2.16 [INFO] [stderr] Compiling form_urlencoded v1.1.0 [INFO] [stderr] Compiling base64 v0.13.1 [INFO] [stderr] Compiling idna v0.3.0 [INFO] [stderr] Compiling rand_chacha v0.3.1 [INFO] [stderr] Compiling target-lexicon v0.12.4 [INFO] [stderr] Compiling http v0.2.8 [INFO] [stderr] Compiling num-traits v0.2.15 [INFO] [stderr] Compiling byteorder v1.4.3 [INFO] [stderr] Compiling rand v0.8.5 [INFO] [stderr] Compiling async-trait v0.1.58 [INFO] [stderr] Compiling serde_json v1.0.87 [INFO] [stderr] Compiling url v2.3.1 [INFO] [stderr] Compiling crypto-common v0.1.6 [INFO] [stderr] Compiling block-buffer v0.10.3 [INFO] [stderr] Compiling num-integer v0.1.45 [INFO] [stderr] Compiling cpufeatures v0.2.5 [INFO] [stderr] Compiling digest v0.10.5 [INFO] [stderr] Compiling pkg-config v0.3.26 [INFO] [stderr] Compiling pyo3-build-config v0.17.3 [INFO] [stderr] Compiling time v0.1.44 [INFO] [stderr] Compiling thiserror v1.0.37 [INFO] [stderr] Compiling iana-time-zone v0.1.53 [INFO] [stderr] Compiling time-core v0.1.0 [INFO] [stderr] Compiling time-macros v0.2.5 [INFO] [stderr] Compiling openssl-sys v0.9.77 [INFO] [stderr] Compiling num_threads v0.1.6 [INFO] [stderr] Compiling adler v1.0.2 [INFO] [stderr] Compiling httparse v1.8.0 [INFO] [stderr] Compiling miniz_oxide v0.5.4 [INFO] [stderr] Compiling proc-macro-error-attr v1.0.4 [INFO] [stderr] Compiling alloc-no-stdlib v2.0.4 [INFO] [stderr] Compiling tower-service v0.3.2 [INFO] [stderr] Compiling lazy_static v1.4.0 [INFO] [stderr] Compiling crc32fast v1.3.2 [INFO] [stderr] Compiling alloc-stdlib v0.2.2 [INFO] [stderr] Compiling time v0.3.16 [INFO] [stderr] Compiling http-body v0.4.5 [INFO] [stderr] Compiling ahash v0.7.6 [INFO] [stderr] Compiling proc-macro-error v1.0.4 [INFO] [stderr] Compiling unicase v2.6.0 [INFO] [stderr] Compiling openssl v0.10.42 [INFO] [stderr] Compiling foreign-types-shared v0.1.1 [INFO] [stderr] Compiling void v1.0.2 [INFO] [stderr] Compiling foreign-types v0.3.2 [INFO] [stderr] Compiling unreachable v1.0.0 [INFO] [stderr] Compiling brotli-decompressor v2.3.2 [INFO] [stderr] Compiling pyo3-ffi v0.17.3 [INFO] [stderr] Compiling smartstring v1.0.1 [INFO] [stderr] Compiling memoffset v0.6.5 [INFO] [stderr] Compiling try-lock v0.2.3 [INFO] [stderr] Compiling native-tls v0.2.10 [INFO] [stderr] Compiling mime v0.3.16 [INFO] [stderr] Compiling either v1.8.0 [INFO] [stderr] Compiling ascii v0.9.3 [INFO] [stderr] Compiling httpdate v1.0.2 [INFO] [stderr] Compiling want v0.3.0 [INFO] [stderr] Compiling flate2 v1.0.24 [INFO] [stderr] Compiling combine v3.8.1 [INFO] [stderr] Compiling pyo3 v0.17.3 [INFO] [stderr] Compiling md-5 v0.10.5 [INFO] [stderr] Compiling hmac v0.12.1 [INFO] [stderr] Compiling sha2 v0.10.6 [INFO] [stderr] Compiling stringprep v0.1.2 [INFO] [stderr] Compiling cookie v0.16.1 [INFO] [stderr] Compiling brotli v3.3.4 [INFO] [stderr] Compiling siphasher v0.3.10 [INFO] [stderr] Compiling openssl-probe v0.1.5 [INFO] [stderr] Compiling crossbeam-utils v0.8.12 [INFO] [stderr] Compiling fallible-iterator v0.2.0 [INFO] [stderr] Compiling rustversion v1.0.9 [INFO] [stderr] Compiling tower-layer v0.3.2 [INFO] [stderr] Compiling pyo3-macros-backend v0.17.3 [INFO] [stderr] Compiling derive_utils v0.11.2 [INFO] [stderr] Compiling postgres-protocol v0.6.4 [INFO] [stderr] Compiling phf_shared v0.11.1 [INFO] [stderr] Compiling mime_guess v2.0.4 [INFO] [stderr] Compiling sha-1 v0.10.0 [INFO] [stderr] Compiling backtrace v0.3.66 [INFO] [stderr] Compiling gimli v0.26.2 [INFO] [stderr] Compiling unindent v0.1.10 [INFO] [stderr] Compiling indoc v1.0.7 [INFO] [stderr] Compiling encoding_rs v0.8.31 [INFO] [stderr] Compiling proc-macro-hack v0.5.19 [INFO] [stderr] Compiling psl-types v2.0.11 [INFO] [stderr] Compiling matches v0.1.9 [INFO] [stderr] Compiling failure_derive v0.1.8 [INFO] [stderr] Compiling array-init v2.0.1 [INFO] [stderr] Compiling utf-8 v0.7.6 [INFO] [stderr] Compiling unicode-xid v0.2.4 [INFO] [stderr] Compiling idna v0.2.3 [INFO] [stderr] Compiling synstructure v0.12.6 [INFO] [stderr] Compiling publicsuffix v2.2.3 [INFO] [stderr] Compiling phf v0.11.1 [INFO] [stderr] Compiling tokio-macros v1.8.0 [INFO] [stderr] Compiling futures-macro v0.3.25 [INFO] [stderr] Compiling tracing-attributes v0.1.23 [INFO] [stderr] Compiling thiserror-impl v1.0.37 [INFO] [stderr] Compiling openssl-macros v0.1.0 [INFO] [stderr] Compiling pin-project-internal v1.0.12 [INFO] [stderr] Compiling pyo3-macros v0.17.3 [INFO] [stderr] Compiling tracing v0.1.37 [INFO] [stderr] Compiling futures-enum v0.1.17 [INFO] [stderr] Compiling juniper_codegen_puff v0.16.0-dev [INFO] [stderr] Compiling graphql-parser v0.4.0 [INFO] [stderr] Compiling pin-project v1.0.12 [INFO] [stderr] Compiling tungstenite v0.17.3 [INFO] [stderr] Compiling addr2line v0.17.0 [INFO] [stderr] Compiling futures-executor v0.3.25 [INFO] [stderr] Compiling futures v0.3.25 [INFO] [stderr] Compiling sha1 v0.10.5 [INFO] [stderr] Compiling headers-core v0.2.0 [INFO] [stderr] Compiling inotify-sys v0.1.5 [INFO] [stderr] Compiling object v0.29.0 [INFO] [stderr] Compiling rustc-demangle v0.1.21 [INFO] [stderr] Compiling http-range-header v0.3.0 [INFO] [stderr] Compiling tokio-util v0.7.4 [INFO] [stderr] Compiling async-compression v0.3.15 [INFO] [stderr] Compiling bb8 v0.8.0 [INFO] [stderr] Compiling tokio-native-tls v0.3.0 [INFO] [stderr] Compiling combine v4.6.6 [INFO] [stderr] Compiling tower v0.4.13 [INFO] [stderr] Compiling overload v0.1.1 [INFO] [stderr] Compiling os_str_bytes v6.3.1 [INFO] [stderr] Compiling same-file v1.0.6 [INFO] [stderr] Compiling anyhow v1.0.66 [INFO] [stderr] Compiling tower-http v0.3.4 [INFO] [stderr] Compiling walkdir v2.3.2 [INFO] [stderr] Compiling clap_lex v0.3.0 [INFO] [stderr] Compiling nu-ansi-term v0.46.0 [INFO] [stderr] Compiling chrono v0.4.22 [INFO] [stderr] Compiling uuid v1.2.1 [INFO] [stderr] Compiling serde_bytes v0.11.7 [INFO] [stderr] Compiling serde_urlencoded v0.7.1 [INFO] [stderr] Compiling tokio-tungstenite v0.17.2 [INFO] [stderr] Compiling inotify v0.9.6 [INFO] [stderr] Compiling h2 v0.3.15 [INFO] [stderr] Compiling headers v0.3.8 [INFO] [stderr] Compiling castaway v0.2.2 [INFO] [stderr] Compiling axum-core v0.3.0-rc.2 [INFO] [stderr] Compiling bson v2.4.0 [INFO] [stderr] Compiling postgres-types v0.2.4 [INFO] [stderr] Compiling cookie_store v0.16.1 [INFO] [stderr] Compiling crossbeam-channel v0.5.6 [INFO] [stderr] Compiling tokio-postgres v0.7.7 [INFO] [stderr] Compiling sharded-slab v0.1.4 [INFO] [stderr] Compiling tracing-log v0.1.3 [INFO] [stderr] Compiling atty v0.2.14 [INFO] [stderr] Compiling filetime v0.2.18 [INFO] [stderr] Compiling thread_local v1.1.4 [INFO] [stderr] Compiling termcolor v1.1.3 [INFO] [stderr] Compiling ipnet v2.5.0 [INFO] [stderr] Compiling juniper_puff v0.16.0-dev [INFO] [stderr] Compiling strsim v0.10.0 [INFO] [stderr] Compiling redis v0.21.6 [INFO] [stderr] Compiling stable_deref_trait v1.2.0 [INFO] [stderr] Compiling matchit v0.6.0 [INFO] [stderr] Compiling sync_wrapper v0.1.1 [INFO] [stderr] Compiling owning_ref v0.4.1 [INFO] [stderr] Compiling clap v4.0.18 [INFO] [stderr] Compiling bb8-postgres v0.8.1 [INFO] [stderr] Compiling hyper v0.14.22 [INFO] [stderr] Compiling tracing-subscriber v0.3.16 [INFO] [stderr] Compiling notify v5.0.0 [INFO] [stderr] Compiling failure v0.1.8 [INFO] [stderr] Compiling pyo3-chrono v0.5.0 [INFO] [stderr] Compiling compact_str v0.6.1 [INFO] [stderr] Compiling bincode v1.3.3 [INFO] [stderr] Compiling pythonize v0.17.0 [INFO] [stderr] Compiling toml v0.5.9 [INFO] [stderr] Compiling juniper_subscriptions_puff v0.17.0-dev [INFO] [stderr] Compiling tokio-stream v0.1.11 [INFO] [stderr] Compiling juniper_graphql_ws_puff v0.4.0-dev [INFO] [stderr] Compiling dotenvy v0.15.6 [INFO] [stderr] Compiling bb8-redis v0.11.0 [INFO] [stderr] Compiling hyper-tls v0.5.0 [INFO] [stderr] Compiling axum v0.6.0-rc.2 [INFO] [stderr] Compiling reqwest v0.11.12 [INFO] [stderr] Compiling puff-rs v0.1.8 (/opt/rustwide/workdir) [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/json/error.rs:84:1 [INFO] [stdout] | [INFO] [stdout] 84 | import_exception!(json, JSONDecodeError); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] note: the lint level is defined here [INFO] [stdout] --> src/lib.rs:2:9 [INFO] [stdout] | [INFO] [stdout] 2 | #![deny(warnings)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` implied by `#[warn(warnings)]` [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `import_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/json/error.rs:84:1 [INFO] [stdout] | [INFO] [stdout] 84 | import_exception!(json, JSONDecodeError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `import_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: private item shadows public glob re-export [INFO] [stdout] --> src/python/mod.rs:11:5 [INFO] [stdout] | [INFO] [stdout] 11 | use pyo3::wrap_pyfunction; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] note: the name `wrap_pyfunction` in the macro namespace is supposed to be publicly re-exported here [INFO] [stdout] --> src/python/mod.rs:30:9 [INFO] [stdout] | [INFO] [stdout] 30 | pub use pyo3::prelude::*; [INFO] [stdout] | ^^^^^^^^^^^^^^^^ [INFO] [stdout] note: but the private item here shadows it [INFO] [stdout] --> src/python/mod.rs:11:5 [INFO] [stdout] | [INFO] [stdout] 11 | use pyo3::wrap_pyfunction; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = note: `#[warn(hidden_glob_reexports)]` implied by `#[warn(warnings)]` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:32:1 [INFO] [stdout] | [INFO] [stdout] 32 | create_exception!(module, PgError, pyo3::exceptions::PyException); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:32:1 [INFO] [stdout] | [INFO] [stdout] 32 | create_exception!(module, PgError, pyo3::exceptions::PyException); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:33:1 [INFO] [stdout] | [INFO] [stdout] 33 | create_exception!(module, Warning, pyo3::exceptions::PyException); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:33:1 [INFO] [stdout] | [INFO] [stdout] 33 | create_exception!(module, Warning, pyo3::exceptions::PyException); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:34:1 [INFO] [stdout] | [INFO] [stdout] 34 | create_exception!(module, InterfaceError, PgError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:34:1 [INFO] [stdout] | [INFO] [stdout] 34 | create_exception!(module, InterfaceError, PgError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:35:1 [INFO] [stdout] | [INFO] [stdout] 35 | create_exception!(module, DatabaseError, PgError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:35:1 [INFO] [stdout] | [INFO] [stdout] 35 | create_exception!(module, DatabaseError, PgError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:36:1 [INFO] [stdout] | [INFO] [stdout] 36 | create_exception!(module, InternalError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:36:1 [INFO] [stdout] | [INFO] [stdout] 36 | create_exception!(module, InternalError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:37:1 [INFO] [stdout] | [INFO] [stdout] 37 | create_exception!(module, OperationalError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:37:1 [INFO] [stdout] | [INFO] [stdout] 37 | create_exception!(module, OperationalError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:38:1 [INFO] [stdout] | [INFO] [stdout] 38 | create_exception!(module, ProgrammingError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:38:1 [INFO] [stdout] | [INFO] [stdout] 38 | create_exception!(module, ProgrammingError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:39:1 [INFO] [stdout] | [INFO] [stdout] 39 | create_exception!(module, IntegrityError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:39:1 [INFO] [stdout] | [INFO] [stdout] 39 | create_exception!(module, IntegrityError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:40:1 [INFO] [stdout] | [INFO] [stdout] 40 | create_exception!(module, DataError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:40:1 [INFO] [stdout] | [INFO] [stdout] 40 | create_exception!(module, DataError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:41:1 [INFO] [stdout] | [INFO] [stdout] 41 | create_exception!(module, NotSupportedError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:41:1 [INFO] [stdout] | [INFO] [stdout] 41 | create_exception!(module, NotSupportedError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this function depends on never type fallback being `()` [INFO] [stdout] --> src/databases/pubsub.rs:375:1 [INFO] [stdout] | [INFO] [stdout] 375 | / pub async fn new_pubsub_async( [INFO] [stdout] 376 | | conn: T, [INFO] [stdout] 377 | | check: bool, [INFO] [stdout] 378 | | pool_size: u32, [INFO] [stdout] 379 | | ) -> PuffResult { [INFO] [stdout] | |_____________________________^ [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in Rust 2024 and in a future release in all editions! [INFO] [stdout] = note: for more information, see [INFO] [stdout] = help: specify the types explicitly [INFO] [stdout] note: in edition 2024, the requirement `!: FromRedisValue` will fail [INFO] [stdout] --> src/databases/pubsub.rs:388:51 [INFO] [stdout] | [INFO] [stdout] 388 | PuffResult::Ok(Cmd::new().arg("PING").query_async(&mut *conn).await?) [INFO] [stdout] | ^^^^^^^^^^^ [INFO] [stdout] = note: `#[warn(dependency_on_unit_never_type_fallback)]` implied by `#[warn(warnings)]` [INFO] [stdout] help: use `()` annotations to avoid fallback changes [INFO] [stdout] | [INFO] [stdout] 388 | PuffResult::Ok(Cmd::new().arg("PING").query_async::<_, ()>(&mut *conn).await?) [INFO] [stdout] | +++++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this function depends on never type fallback being `()` [INFO] [stdout] --> src/databases/redis.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | / pub async fn new_redis_async( [INFO] [stdout] 28 | | conn: T, [INFO] [stdout] 29 | | check: bool, [INFO] [stdout] 30 | | pool_size: u32, [INFO] [stdout] 31 | | ) -> PuffResult { [INFO] [stdout] | |____________________________^ [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in Rust 2024 and in a future release in all editions! [INFO] [stdout] = note: for more information, see [INFO] [stdout] = help: specify the types explicitly [INFO] [stdout] note: in edition 2024, the requirement `!: FromRedisValue` will fail [INFO] [stdout] --> src/databases/redis.rs:39:51 [INFO] [stdout] | [INFO] [stdout] 39 | PuffResult::Ok(Cmd::new().arg("PING").query_async(&mut *conn).await?) [INFO] [stdout] | ^^^^^^^^^^^ [INFO] [stdout] help: use `()` annotations to avoid fallback changes [INFO] [stdout] | [INFO] [stdout] 39 | PuffResult::Ok(Cmd::new().arg("PING").query_async::<_, ()>(&mut *conn).await?) [INFO] [stdout] | +++++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this function depends on never type fallback being `()` [INFO] [stdout] --> src/tasks/mod.rs:148:1 [INFO] [stdout] | [INFO] [stdout] 148 | / pub async fn add_task>( [INFO] [stdout] 149 | | task_queue: TaskQueue, [INFO] [stdout] 150 | | func_path: T, [INFO] [stdout] 151 | | params: serde_json::Value, [INFO] [stdout] ... | [INFO] [stdout] 156 | | trigger: bool, [INFO] [stdout] 157 | | ) -> PuffResult> { [INFO] [stdout] | |____________________________^ [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in Rust 2024 and in a future release in all editions! [INFO] [stdout] = note: for more information, see [INFO] [stdout] = help: specify the types explicitly [INFO] [stdout] note: in edition 2024, the requirement `!: FromRedisValue` will fail [INFO] [stdout] --> src/tasks/mod.rs:186:10 [INFO] [stdout] | [INFO] [stdout] 186 | pipe.query_async(&mut *r).await?; [INFO] [stdout] | ^^^^^^^^^^^ [INFO] [stdout] help: use `()` annotations to avoid fallback changes [INFO] [stdout] | [INFO] [stdout] 186 | pipe.query_async::<_, ()>(&mut *r).await?; [INFO] [stdout] | +++++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this function depends on never type fallback being `()` [INFO] [stdout] --> src/tasks/mod.rs:526:1 [INFO] [stdout] | [INFO] [stdout] 526 | / pub async fn new_task_queue_async( [INFO] [stdout] 527 | | conn: T, [INFO] [stdout] 528 | | check: bool, [INFO] [stdout] 529 | | pool_size: u32, [INFO] [stdout] 530 | | ) -> PuffResult { [INFO] [stdout] | |__________________________^ [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in Rust 2024 and in a future release in all editions! [INFO] [stdout] = note: for more information, see [INFO] [stdout] = help: specify the types explicitly [INFO] [stdout] note: in edition 2024, the requirement `!: FromRedisValue` will fail [INFO] [stdout] --> src/tasks/mod.rs:539:51 [INFO] [stdout] | [INFO] [stdout] 539 | PuffResult::Ok(Cmd::new().arg("PING").query_async(&mut *conn).await?) [INFO] [stdout] | ^^^^^^^^^^^ [INFO] [stdout] help: use `()` annotations to avoid fallback changes [INFO] [stdout] | [INFO] [stdout] 539 | PuffResult::Ok(Cmd::new().arg("PING").query_async::<_, ()>(&mut *conn).await?) [INFO] [stdout] | +++++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: field `0` is never read [INFO] [stdout] --> src/graphql/handlers.rs:261:10 [INFO] [stdout] | [INFO] [stdout] 261 | Axum(axum::Error), [INFO] [stdout] | ---- ^^^^^^^^^^^ [INFO] [stdout] | | [INFO] [stdout] | field in this variant [INFO] [stdout] | [INFO] [stdout] = note: `SubscriptionError` has a derived impl for the trait `Debug`, but this is intentionally ignored during dead code analysis [INFO] [stdout] = note: `#[warn(dead_code)]` implied by `#[warn(warnings)]` [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] 261 - Axum(axum::Error), [INFO] [stdout] 261 + Axum(()), [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: field `0` is never read [INFO] [stdout] --> src/graphql/handlers.rs:262:11 [INFO] [stdout] | [INFO] [stdout] 262 | Serde(serde_json::Error), [INFO] [stdout] | ----- ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | | [INFO] [stdout] | field in this variant [INFO] [stdout] | [INFO] [stdout] = note: `SubscriptionError` has a derived impl for the trait `Debug`, 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] 262 - Serde(serde_json::Error), [INFO] [stdout] 262 + Serde(()), [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: struct `AggroSqlValue` is never constructed [INFO] [stdout] --> src/graphql/scalar.rs:207:12 [INFO] [stdout] | [INFO] [stdout] 207 | pub struct AggroSqlValue(JuniperValue); [INFO] [stdout] | ^^^^^^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: struct `AggroScalarValueVisitor` is never constructed [INFO] [stdout] --> src/graphql/scalar.rs:472:12 [INFO] [stdout] | [INFO] [stdout] 472 | pub struct AggroScalarValueVisitor; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: field `0` is never read [INFO] [stdout] --> src/python/asgi/handler.rs:63:11 [INFO] [stdout] | [INFO] [stdout] 63 | PyErr(PyErr), [INFO] [stdout] | ----- ^^^^^ [INFO] [stdout] | | [INFO] [stdout] | field in this variant [INFO] [stdout] | [INFO] [stdout] = note: `AsgiError` has a derived impl for the trait `Debug`, 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] 63 - PyErr(PyErr), [INFO] [stdout] 63 + PyErr(()), [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/databases/pubsub.rs:264:9 [INFO] [stdout] | [INFO] [stdout] 264 | &self, [INFO] [stdout] | ^^^^^ the lifetime is elided here [INFO] [stdout] ... [INFO] [stdout] 268 | ) -> BoxFuture> { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` implied by `#[warn(warnings)]` [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 268 | ) -> BoxFuture<'_, PuffResult<()>> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/databases/pubsub.rs:319:37 [INFO] [stdout] | [INFO] [stdout] 319 | pub fn subscribe>(&self, channel: T) -> BoxFuture { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 319 | pub fn subscribe>(&self, channel: T) -> BoxFuture<'_, bool> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/databases/pubsub.rs:335:39 [INFO] [stdout] | [INFO] [stdout] 335 | pub fn unsubscribe>(&self, channel: T) -> BoxFuture { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 335 | pub fn unsubscribe>(&self, channel: T) -> BoxFuture<'_, bool> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/databases/pubsub.rs:352:9 [INFO] [stdout] | [INFO] [stdout] 352 | &self, [INFO] [stdout] | ^^^^^ the lifetime is elided here [INFO] [stdout] ... [INFO] [stdout] 355 | ) -> BoxFuture> { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 355 | ) -> BoxFuture<'_, PuffResult<()>> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item [INFO] [stdout] --> src/json/error.rs:31:17 [INFO] [stdout] | [INFO] [stdout] 31 | #[derive(Debug, Fail)] [INFO] [stdout] | ^--- [INFO] [stdout] | | [INFO] [stdout] | `Fail` is not local [INFO] [stdout] | move the `impl` block outside of this constant `_DERIVE_failure_Fail_FOR_HyperJsonError` [INFO] [stdout] 32 | pub enum HyperJsonError { [INFO] [stdout] | -------------- `HyperJsonError` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `Fail` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `Fail` may come from an old version of the `failure_derive` crate, try updating your dependency with `cargo update -p failure_derive` [INFO] [stdout] = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl` [INFO] [stdout] = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint [INFO] [stdout] = note: `#[warn(non_local_definitions)]` implied by `#[warn(warnings)]` [INFO] [stdout] = note: this warning originates in the derive macro `Fail` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item [INFO] [stdout] --> src/json/error.rs:31:17 [INFO] [stdout] | [INFO] [stdout] 31 | #[derive(Debug, Fail)] [INFO] [stdout] | ^--- [INFO] [stdout] | | [INFO] [stdout] | `Display` is not local [INFO] [stdout] | move the `impl` block outside of this constant `_DERIVE_failure_core_fmt_Display_FOR_HyperJsonError` [INFO] [stdout] 32 | pub enum HyperJsonError { [INFO] [stdout] | -------------- `HyperJsonError` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `Fail` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `Fail` may come from an old version of the `failure_derive` crate, try updating your dependency with `cargo update -p failure_derive` [INFO] [stdout] = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl` [INFO] [stdout] = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint [INFO] [stdout] = note: this warning originates in the derive macro `Fail` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/python/asgi/mod.rs:121:18 [INFO] [stdout] | [INFO] [stdout] 121 | pub fn start(&mut self) -> Result>> { [INFO] [stdout] | ^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 121 | pub fn start(&mut self) -> Result>> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/python/wsgi/mod.rs:74:18 [INFO] [stdout] | [INFO] [stdout] 74 | pub fn start(&mut self) -> Result>> { [INFO] [stdout] | ^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 74 | pub fn start(&mut self) -> Result>> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 3m 48s [INFO] [stderr] warning: the following packages contain code that will be rejected by a future version of Rust: puff-rs v0.1.8 (/opt/rustwide/workdir) [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" "c4e52b4586f09c3935aedebe8402131a08f92c3364cb4a3583020b31c6b2a26e", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "c4e52b4586f09c3935aedebe8402131a08f92c3364cb4a3583020b31c6b2a26e", kill_on_drop: false }` [INFO] [stdout] c4e52b4586f09c3935aedebe8402131a08f92c3364cb4a3583020b31c6b2a26e [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "RUSTDOCFLAGS=--cap-lints=warn" "-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:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+beta-2025-09-21" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 83ee2e70ffdb971c115f153ffe3dde459fdbcc30530f4ba36c61ec574eba7d7e [INFO] running `Command { std: "docker" "start" "-a" "83ee2e70ffdb971c115f153ffe3dde459fdbcc30530f4ba36c61ec574eba7d7e", kill_on_drop: false }` [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/json/error.rs:84:1 [INFO] [stdout] | [INFO] [stdout] 84 | import_exception!(json, JSONDecodeError); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] note: the lint level is defined here [INFO] [stdout] --> src/lib.rs:2:9 [INFO] [stdout] | [INFO] [stdout] 2 | #![deny(warnings)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` implied by `#[warn(warnings)]` [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `import_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/json/error.rs:84:1 [INFO] [stdout] | [INFO] [stdout] 84 | import_exception!(json, JSONDecodeError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `import_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: private item shadows public glob re-export [INFO] [stdout] --> src/python/mod.rs:11:5 [INFO] [stdout] | [INFO] [stdout] 11 | use pyo3::wrap_pyfunction; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] note: the name `wrap_pyfunction` in the macro namespace is supposed to be publicly re-exported here [INFO] [stdout] --> src/python/mod.rs:30:9 [INFO] [stdout] | [INFO] [stdout] 30 | pub use pyo3::prelude::*; [INFO] [stdout] | ^^^^^^^^^^^^^^^^ [INFO] [stdout] note: but the private item here shadows it [INFO] [stdout] --> src/python/mod.rs:11:5 [INFO] [stdout] | [INFO] [stdout] 11 | use pyo3::wrap_pyfunction; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = note: `#[warn(hidden_glob_reexports)]` implied by `#[warn(warnings)]` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:32:1 [INFO] [stdout] | [INFO] [stdout] 32 | create_exception!(module, PgError, pyo3::exceptions::PyException); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:32:1 [INFO] [stdout] | [INFO] [stdout] 32 | create_exception!(module, PgError, pyo3::exceptions::PyException); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:33:1 [INFO] [stdout] | [INFO] [stdout] 33 | create_exception!(module, Warning, pyo3::exceptions::PyException); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:33:1 [INFO] [stdout] | [INFO] [stdout] 33 | create_exception!(module, Warning, pyo3::exceptions::PyException); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:34:1 [INFO] [stdout] | [INFO] [stdout] 34 | create_exception!(module, InterfaceError, PgError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:34:1 [INFO] [stdout] | [INFO] [stdout] 34 | create_exception!(module, InterfaceError, PgError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:35:1 [INFO] [stdout] | [INFO] [stdout] 35 | create_exception!(module, DatabaseError, PgError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:35:1 [INFO] [stdout] | [INFO] [stdout] 35 | create_exception!(module, DatabaseError, PgError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:36:1 [INFO] [stdout] | [INFO] [stdout] 36 | create_exception!(module, InternalError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:36:1 [INFO] [stdout] | [INFO] [stdout] 36 | create_exception!(module, InternalError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:37:1 [INFO] [stdout] | [INFO] [stdout] 37 | create_exception!(module, OperationalError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:37:1 [INFO] [stdout] | [INFO] [stdout] 37 | create_exception!(module, OperationalError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:38:1 [INFO] [stdout] | [INFO] [stdout] 38 | create_exception!(module, ProgrammingError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:38:1 [INFO] [stdout] | [INFO] [stdout] 38 | create_exception!(module, ProgrammingError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:39:1 [INFO] [stdout] | [INFO] [stdout] 39 | create_exception!(module, IntegrityError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:39:1 [INFO] [stdout] | [INFO] [stdout] 39 | create_exception!(module, IntegrityError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:40:1 [INFO] [stdout] | [INFO] [stdout] 40 | create_exception!(module, DataError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:40:1 [INFO] [stdout] | [INFO] [stdout] 40 | create_exception!(module, DataError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:41:1 [INFO] [stdout] | [INFO] [stdout] 41 | create_exception!(module, NotSupportedError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:41:1 [INFO] [stdout] | [INFO] [stdout] 41 | create_exception!(module, NotSupportedError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this function depends on never type fallback being `()` [INFO] [stdout] --> src/databases/pubsub.rs:375:1 [INFO] [stdout] | [INFO] [stdout] 375 | / pub async fn new_pubsub_async( [INFO] [stdout] 376 | | conn: T, [INFO] [stdout] 377 | | check: bool, [INFO] [stdout] 378 | | pool_size: u32, [INFO] [stdout] 379 | | ) -> PuffResult { [INFO] [stdout] | |_____________________________^ [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in Rust 2024 and in a future release in all editions! [INFO] [stdout] = note: for more information, see [INFO] [stdout] = help: specify the types explicitly [INFO] [stdout] note: in edition 2024, the requirement `!: FromRedisValue` will fail [INFO] [stdout] --> src/databases/pubsub.rs:388:51 [INFO] [stdout] | [INFO] [stdout] 388 | PuffResult::Ok(Cmd::new().arg("PING").query_async(&mut *conn).await?) [INFO] [stdout] | ^^^^^^^^^^^ [INFO] [stdout] = note: `#[warn(dependency_on_unit_never_type_fallback)]` implied by `#[warn(warnings)]` [INFO] [stdout] help: use `()` annotations to avoid fallback changes [INFO] [stdout] | [INFO] [stdout] 388 | PuffResult::Ok(Cmd::new().arg("PING").query_async::<_, ()>(&mut *conn).await?) [INFO] [stdout] | +++++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this function depends on never type fallback being `()` [INFO] [stdout] --> src/databases/redis.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | / pub async fn new_redis_async( [INFO] [stdout] 28 | | conn: T, [INFO] [stdout] 29 | | check: bool, [INFO] [stdout] 30 | | pool_size: u32, [INFO] [stdout] 31 | | ) -> PuffResult { [INFO] [stdout] | |____________________________^ [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in Rust 2024 and in a future release in all editions! [INFO] [stdout] = note: for more information, see [INFO] [stdout] = help: specify the types explicitly [INFO] [stdout] note: in edition 2024, the requirement `!: FromRedisValue` will fail [INFO] [stdout] --> src/databases/redis.rs:39:51 [INFO] [stdout] | [INFO] [stdout] 39 | PuffResult::Ok(Cmd::new().arg("PING").query_async(&mut *conn).await?) [INFO] [stdout] | ^^^^^^^^^^^ [INFO] [stdout] help: use `()` annotations to avoid fallback changes [INFO] [stdout] | [INFO] [stdout] 39 | PuffResult::Ok(Cmd::new().arg("PING").query_async::<_, ()>(&mut *conn).await?) [INFO] [stdout] | +++++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this function depends on never type fallback being `()` [INFO] [stdout] --> src/tasks/mod.rs:148:1 [INFO] [stdout] | [INFO] [stdout] 148 | / pub async fn add_task>( [INFO] [stdout] 149 | | task_queue: TaskQueue, [INFO] [stdout] 150 | | func_path: T, [INFO] [stdout] 151 | | params: serde_json::Value, [INFO] [stdout] ... | [INFO] [stdout] 156 | | trigger: bool, [INFO] [stdout] 157 | | ) -> PuffResult> { [INFO] [stdout] | |____________________________^ [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in Rust 2024 and in a future release in all editions! [INFO] [stdout] = note: for more information, see [INFO] [stdout] = help: specify the types explicitly [INFO] [stdout] note: in edition 2024, the requirement `!: FromRedisValue` will fail [INFO] [stdout] --> src/tasks/mod.rs:186:10 [INFO] [stdout] | [INFO] [stdout] 186 | pipe.query_async(&mut *r).await?; [INFO] [stdout] | ^^^^^^^^^^^ [INFO] [stdout] help: use `()` annotations to avoid fallback changes [INFO] [stdout] | [INFO] [stdout] 186 | pipe.query_async::<_, ()>(&mut *r).await?; [INFO] [stdout] | +++++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this function depends on never type fallback being `()` [INFO] [stdout] --> src/tasks/mod.rs:526:1 [INFO] [stdout] | [INFO] [stdout] 526 | / pub async fn new_task_queue_async( [INFO] [stdout] 527 | | conn: T, [INFO] [stdout] 528 | | check: bool, [INFO] [stdout] 529 | | pool_size: u32, [INFO] [stdout] 530 | | ) -> PuffResult { [INFO] [stdout] | |__________________________^ [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in Rust 2024 and in a future release in all editions! [INFO] [stdout] = note: for more information, see [INFO] [stdout] = help: specify the types explicitly [INFO] [stdout] note: in edition 2024, the requirement `!: FromRedisValue` will fail [INFO] [stdout] --> src/tasks/mod.rs:539:51 [INFO] [stdout] | [INFO] [stdout] 539 | PuffResult::Ok(Cmd::new().arg("PING").query_async(&mut *conn).await?) [INFO] [stdout] | ^^^^^^^^^^^ [INFO] [stdout] help: use `()` annotations to avoid fallback changes [INFO] [stdout] | [INFO] [stdout] 539 | PuffResult::Ok(Cmd::new().arg("PING").query_async::<_, ()>(&mut *conn).await?) [INFO] [stdout] | +++++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: field `0` is never read [INFO] [stdout] --> src/graphql/handlers.rs:261:10 [INFO] [stdout] | [INFO] [stdout] 261 | Axum(axum::Error), [INFO] [stdout] | ---- ^^^^^^^^^^^ [INFO] [stdout] | | [INFO] [stdout] | field in this variant [INFO] [stdout] | [INFO] [stdout] = note: `SubscriptionError` has a derived impl for the trait `Debug`, but this is intentionally ignored during dead code analysis [INFO] [stdout] = note: `#[warn(dead_code)]` implied by `#[warn(warnings)]` [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] 261 - Axum(axum::Error), [INFO] [stdout] 261 + Axum(()), [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: field `0` is never read [INFO] [stdout] --> src/graphql/handlers.rs:262:11 [INFO] [stdout] | [INFO] [stdout] 262 | Serde(serde_json::Error), [INFO] [stdout] | ----- ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | | [INFO] [stdout] | field in this variant [INFO] [stdout] | [INFO] [stdout] = note: `SubscriptionError` has a derived impl for the trait `Debug`, 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] 262 - Serde(serde_json::Error), [INFO] [stdout] 262 + Serde(()), [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Compiling puff-rs v0.1.8 (/opt/rustwide/workdir) [INFO] [stdout] warning: struct `AggroSqlValue` is never constructed [INFO] [stdout] --> src/graphql/scalar.rs:207:12 [INFO] [stdout] | [INFO] [stdout] 207 | pub struct AggroSqlValue(JuniperValue); [INFO] [stdout] | ^^^^^^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: struct `AggroScalarValueVisitor` is never constructed [INFO] [stdout] --> src/graphql/scalar.rs:472:12 [INFO] [stdout] | [INFO] [stdout] 472 | pub struct AggroScalarValueVisitor; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: field `0` is never read [INFO] [stdout] --> src/python/asgi/handler.rs:63:11 [INFO] [stdout] | [INFO] [stdout] 63 | PyErr(PyErr), [INFO] [stdout] | ----- ^^^^^ [INFO] [stdout] | | [INFO] [stdout] | field in this variant [INFO] [stdout] | [INFO] [stdout] = note: `AsgiError` has a derived impl for the trait `Debug`, 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] 63 - PyErr(PyErr), [INFO] [stdout] 63 + PyErr(()), [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/databases/pubsub.rs:264:9 [INFO] [stdout] | [INFO] [stdout] 264 | &self, [INFO] [stdout] | ^^^^^ the lifetime is elided here [INFO] [stdout] ... [INFO] [stdout] 268 | ) -> BoxFuture> { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` implied by `#[warn(warnings)]` [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 268 | ) -> BoxFuture<'_, PuffResult<()>> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/databases/pubsub.rs:319:37 [INFO] [stdout] | [INFO] [stdout] 319 | pub fn subscribe>(&self, channel: T) -> BoxFuture { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 319 | pub fn subscribe>(&self, channel: T) -> BoxFuture<'_, bool> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/databases/pubsub.rs:335:39 [INFO] [stdout] | [INFO] [stdout] 335 | pub fn unsubscribe>(&self, channel: T) -> BoxFuture { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 335 | pub fn unsubscribe>(&self, channel: T) -> BoxFuture<'_, bool> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/databases/pubsub.rs:352:9 [INFO] [stdout] | [INFO] [stdout] 352 | &self, [INFO] [stdout] | ^^^^^ the lifetime is elided here [INFO] [stdout] ... [INFO] [stdout] 355 | ) -> BoxFuture> { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 355 | ) -> BoxFuture<'_, PuffResult<()>> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item [INFO] [stdout] --> src/json/error.rs:31:17 [INFO] [stdout] | [INFO] [stdout] 31 | #[derive(Debug, Fail)] [INFO] [stdout] | ^--- [INFO] [stdout] | | [INFO] [stdout] | `Fail` is not local [INFO] [stdout] | move the `impl` block outside of this constant `_DERIVE_failure_Fail_FOR_HyperJsonError` [INFO] [stdout] 32 | pub enum HyperJsonError { [INFO] [stdout] | -------------- `HyperJsonError` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `Fail` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `Fail` may come from an old version of the `failure_derive` crate, try updating your dependency with `cargo update -p failure_derive` [INFO] [stdout] = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl` [INFO] [stdout] = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint [INFO] [stdout] = note: `#[warn(non_local_definitions)]` implied by `#[warn(warnings)]` [INFO] [stdout] = note: this warning originates in the derive macro `Fail` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item [INFO] [stdout] --> src/json/error.rs:31:17 [INFO] [stdout] | [INFO] [stdout] 31 | #[derive(Debug, Fail)] [INFO] [stdout] | ^--- [INFO] [stdout] | | [INFO] [stdout] | `Display` is not local [INFO] [stdout] | move the `impl` block outside of this constant `_DERIVE_failure_core_fmt_Display_FOR_HyperJsonError` [INFO] [stdout] 32 | pub enum HyperJsonError { [INFO] [stdout] | -------------- `HyperJsonError` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `Fail` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `Fail` may come from an old version of the `failure_derive` crate, try updating your dependency with `cargo update -p failure_derive` [INFO] [stdout] = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl` [INFO] [stdout] = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint [INFO] [stdout] = note: this warning originates in the derive macro `Fail` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/python/asgi/mod.rs:121:18 [INFO] [stdout] | [INFO] [stdout] 121 | pub fn start(&mut self) -> Result>> { [INFO] [stdout] | ^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 121 | pub fn start(&mut self) -> Result>> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/python/wsgi/mod.rs:74:18 [INFO] [stdout] | [INFO] [stdout] 74 | pub fn start(&mut self) -> Result>> { [INFO] [stdout] | ^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 74 | pub fn start(&mut self) -> Result>> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this function depends on never type fallback being `()` [INFO] [stdout] --> examples/basic.rs:30:1 [INFO] [stdout] | [INFO] [stdout] 30 | async fn background_task(redis: RedisClient) -> PuffResult { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in Rust 2024 and in a future release in all editions! [INFO] [stdout] = note: for more information, see [INFO] [stdout] = help: specify the types explicitly [INFO] [stdout] note: in edition 2024, the requirement `!: FromRedisValue` will fail [INFO] [stdout] --> examples/basic.rs:33:10 [INFO] [stdout] | [INFO] [stdout] 33 | conn.set("hello", "world").await?; [INFO] [stdout] | ^^^ [INFO] [stdout] = note: `#[warn(dependency_on_unit_never_type_fallback)]` (part of `#[warn(rust_2024_compatibility)]`) on by default [INFO] [stdout] help: use `()` annotations to avoid fallback changes [INFO] [stdout] | [INFO] [stdout] 33 | conn.set::<_, _, ()>("hello", "world").await?; [INFO] [stdout] | ++++++++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/json/error.rs:84:1 [INFO] [stdout] | [INFO] [stdout] 84 | import_exception!(json, JSONDecodeError); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] note: the lint level is defined here [INFO] [stdout] --> src/lib.rs:2:9 [INFO] [stdout] | [INFO] [stdout] 2 | #![deny(warnings)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` implied by `#[warn(warnings)]` [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `import_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/json/error.rs:84:1 [INFO] [stdout] | [INFO] [stdout] 84 | import_exception!(json, JSONDecodeError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `import_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: private item shadows public glob re-export [INFO] [stdout] --> src/python/mod.rs:11:5 [INFO] [stdout] | [INFO] [stdout] 11 | use pyo3::wrap_pyfunction; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] note: the name `wrap_pyfunction` in the macro namespace is supposed to be publicly re-exported here [INFO] [stdout] --> src/python/mod.rs:30:9 [INFO] [stdout] | [INFO] [stdout] 30 | pub use pyo3::prelude::*; [INFO] [stdout] | ^^^^^^^^^^^^^^^^ [INFO] [stdout] note: but the private item here shadows it [INFO] [stdout] --> src/python/mod.rs:11:5 [INFO] [stdout] | [INFO] [stdout] 11 | use pyo3::wrap_pyfunction; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] = note: `#[warn(hidden_glob_reexports)]` implied by `#[warn(warnings)]` [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:32:1 [INFO] [stdout] | [INFO] [stdout] 32 | create_exception!(module, PgError, pyo3::exceptions::PyException); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:32:1 [INFO] [stdout] | [INFO] [stdout] 32 | create_exception!(module, PgError, pyo3::exceptions::PyException); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:33:1 [INFO] [stdout] | [INFO] [stdout] 33 | create_exception!(module, Warning, pyo3::exceptions::PyException); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:33:1 [INFO] [stdout] | [INFO] [stdout] 33 | create_exception!(module, Warning, pyo3::exceptions::PyException); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:34:1 [INFO] [stdout] | [INFO] [stdout] 34 | create_exception!(module, InterfaceError, PgError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:34:1 [INFO] [stdout] | [INFO] [stdout] 34 | create_exception!(module, InterfaceError, PgError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:35:1 [INFO] [stdout] | [INFO] [stdout] 35 | create_exception!(module, DatabaseError, PgError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:35:1 [INFO] [stdout] | [INFO] [stdout] 35 | create_exception!(module, DatabaseError, PgError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:36:1 [INFO] [stdout] | [INFO] [stdout] 36 | create_exception!(module, InternalError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:36:1 [INFO] [stdout] | [INFO] [stdout] 36 | create_exception!(module, InternalError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:37:1 [INFO] [stdout] | [INFO] [stdout] 37 | create_exception!(module, OperationalError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:37:1 [INFO] [stdout] | [INFO] [stdout] 37 | create_exception!(module, OperationalError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:38:1 [INFO] [stdout] | [INFO] [stdout] 38 | create_exception!(module, ProgrammingError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:38:1 [INFO] [stdout] | [INFO] [stdout] 38 | create_exception!(module, ProgrammingError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:39:1 [INFO] [stdout] | [INFO] [stdout] 39 | create_exception!(module, IntegrityError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:39:1 [INFO] [stdout] | [INFO] [stdout] 39 | create_exception!(module, IntegrityError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:40:1 [INFO] [stdout] | [INFO] [stdout] 40 | create_exception!(module, DataError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:40:1 [INFO] [stdout] | [INFO] [stdout] 40 | create_exception!(module, DataError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:41:1 [INFO] [stdout] | [INFO] [stdout] 41 | create_exception!(module, NotSupportedError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/python/postgres.rs:41:1 [INFO] [stdout] | [INFO] [stdout] 41 | create_exception!(module, NotSupportedError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this function depends on never type fallback being `()` [INFO] [stdout] --> src/databases/pubsub.rs:375:1 [INFO] [stdout] | [INFO] [stdout] 375 | / pub async fn new_pubsub_async( [INFO] [stdout] 376 | | conn: T, [INFO] [stdout] 377 | | check: bool, [INFO] [stdout] 378 | | pool_size: u32, [INFO] [stdout] 379 | | ) -> PuffResult { [INFO] [stdout] | |_____________________________^ [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in Rust 2024 and in a future release in all editions! [INFO] [stdout] = note: for more information, see [INFO] [stdout] = help: specify the types explicitly [INFO] [stdout] note: in edition 2024, the requirement `!: FromRedisValue` will fail [INFO] [stdout] --> src/databases/pubsub.rs:388:51 [INFO] [stdout] | [INFO] [stdout] 388 | PuffResult::Ok(Cmd::new().arg("PING").query_async(&mut *conn).await?) [INFO] [stdout] | ^^^^^^^^^^^ [INFO] [stdout] = note: `#[warn(dependency_on_unit_never_type_fallback)]` implied by `#[warn(warnings)]` [INFO] [stdout] help: use `()` annotations to avoid fallback changes [INFO] [stdout] | [INFO] [stdout] 388 | PuffResult::Ok(Cmd::new().arg("PING").query_async::<_, ()>(&mut *conn).await?) [INFO] [stdout] | +++++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this function depends on never type fallback being `()` [INFO] [stdout] --> src/databases/redis.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | / pub async fn new_redis_async( [INFO] [stdout] 28 | | conn: T, [INFO] [stdout] 29 | | check: bool, [INFO] [stdout] 30 | | pool_size: u32, [INFO] [stdout] 31 | | ) -> PuffResult { [INFO] [stdout] | |____________________________^ [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in Rust 2024 and in a future release in all editions! [INFO] [stdout] = note: for more information, see [INFO] [stdout] = help: specify the types explicitly [INFO] [stdout] note: in edition 2024, the requirement `!: FromRedisValue` will fail [INFO] [stdout] --> src/databases/redis.rs:39:51 [INFO] [stdout] | [INFO] [stdout] 39 | PuffResult::Ok(Cmd::new().arg("PING").query_async(&mut *conn).await?) [INFO] [stdout] | ^^^^^^^^^^^ [INFO] [stdout] help: use `()` annotations to avoid fallback changes [INFO] [stdout] | [INFO] [stdout] 39 | PuffResult::Ok(Cmd::new().arg("PING").query_async::<_, ()>(&mut *conn).await?) [INFO] [stdout] | +++++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this function depends on never type fallback being `()` [INFO] [stdout] --> src/tasks/mod.rs:148:1 [INFO] [stdout] | [INFO] [stdout] 148 | / pub async fn add_task>( [INFO] [stdout] 149 | | task_queue: TaskQueue, [INFO] [stdout] 150 | | func_path: T, [INFO] [stdout] 151 | | params: serde_json::Value, [INFO] [stdout] ... | [INFO] [stdout] 156 | | trigger: bool, [INFO] [stdout] 157 | | ) -> PuffResult> { [INFO] [stdout] | |____________________________^ [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in Rust 2024 and in a future release in all editions! [INFO] [stdout] = note: for more information, see [INFO] [stdout] = help: specify the types explicitly [INFO] [stdout] note: in edition 2024, the requirement `!: FromRedisValue` will fail [INFO] [stdout] --> src/tasks/mod.rs:186:10 [INFO] [stdout] | [INFO] [stdout] 186 | pipe.query_async(&mut *r).await?; [INFO] [stdout] | ^^^^^^^^^^^ [INFO] [stdout] help: use `()` annotations to avoid fallback changes [INFO] [stdout] | [INFO] [stdout] 186 | pipe.query_async::<_, ()>(&mut *r).await?; [INFO] [stdout] | +++++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: this function depends on never type fallback being `()` [INFO] [stdout] --> src/tasks/mod.rs:526:1 [INFO] [stdout] | [INFO] [stdout] 526 | / pub async fn new_task_queue_async( [INFO] [stdout] 527 | | conn: T, [INFO] [stdout] 528 | | check: bool, [INFO] [stdout] 529 | | pool_size: u32, [INFO] [stdout] 530 | | ) -> PuffResult { [INFO] [stdout] | |__________________________^ [INFO] [stdout] | [INFO] [stdout] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in Rust 2024 and in a future release in all editions! [INFO] [stdout] = note: for more information, see [INFO] [stdout] = help: specify the types explicitly [INFO] [stdout] note: in edition 2024, the requirement `!: FromRedisValue` will fail [INFO] [stdout] --> src/tasks/mod.rs:539:51 [INFO] [stdout] | [INFO] [stdout] 539 | PuffResult::Ok(Cmd::new().arg("PING").query_async(&mut *conn).await?) [INFO] [stdout] | ^^^^^^^^^^^ [INFO] [stdout] help: use `()` annotations to avoid fallback changes [INFO] [stdout] | [INFO] [stdout] 539 | PuffResult::Ok(Cmd::new().arg("PING").query_async::<_, ()>(&mut *conn).await?) [INFO] [stdout] | +++++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: field `0` is never read [INFO] [stdout] --> src/graphql/handlers.rs:261:10 [INFO] [stdout] | [INFO] [stdout] 261 | Axum(axum::Error), [INFO] [stdout] | ---- ^^^^^^^^^^^ [INFO] [stdout] | | [INFO] [stdout] | field in this variant [INFO] [stdout] | [INFO] [stdout] = note: `SubscriptionError` has a derived impl for the trait `Debug`, but this is intentionally ignored during dead code analysis [INFO] [stdout] = note: `#[warn(dead_code)]` implied by `#[warn(warnings)]` [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] 261 - Axum(axum::Error), [INFO] [stdout] 261 + Axum(()), [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: field `0` is never read [INFO] [stdout] --> src/graphql/handlers.rs:262:11 [INFO] [stdout] | [INFO] [stdout] 262 | Serde(serde_json::Error), [INFO] [stdout] | ----- ^^^^^^^^^^^^^^^^^ [INFO] [stdout] | | [INFO] [stdout] | field in this variant [INFO] [stdout] | [INFO] [stdout] = note: `SubscriptionError` has a derived impl for the trait `Debug`, 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] 262 - Serde(serde_json::Error), [INFO] [stdout] 262 + Serde(()), [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: struct `AggroSqlValue` is never constructed [INFO] [stdout] --> src/graphql/scalar.rs:207:12 [INFO] [stdout] | [INFO] [stdout] 207 | pub struct AggroSqlValue(JuniperValue); [INFO] [stdout] | ^^^^^^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: struct `AggroScalarValueVisitor` is never constructed [INFO] [stdout] --> src/graphql/scalar.rs:472:12 [INFO] [stdout] | [INFO] [stdout] 472 | pub struct AggroScalarValueVisitor; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: field `0` is never read [INFO] [stdout] --> src/python/asgi/handler.rs:63:11 [INFO] [stdout] | [INFO] [stdout] 63 | PyErr(PyErr), [INFO] [stdout] | ----- ^^^^^ [INFO] [stdout] | | [INFO] [stdout] | field in this variant [INFO] [stdout] | [INFO] [stdout] = note: `AsgiError` has a derived impl for the trait `Debug`, 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] 63 - PyErr(PyErr), [INFO] [stdout] 63 + PyErr(()), [INFO] [stdout] | [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/databases/pubsub.rs:264:9 [INFO] [stdout] | [INFO] [stdout] 264 | &self, [INFO] [stdout] | ^^^^^ the lifetime is elided here [INFO] [stdout] ... [INFO] [stdout] 268 | ) -> BoxFuture> { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` implied by `#[warn(warnings)]` [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 268 | ) -> BoxFuture<'_, PuffResult<()>> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/databases/pubsub.rs:319:37 [INFO] [stdout] | [INFO] [stdout] 319 | pub fn subscribe>(&self, channel: T) -> BoxFuture { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 319 | pub fn subscribe>(&self, channel: T) -> BoxFuture<'_, bool> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/databases/pubsub.rs:335:39 [INFO] [stdout] | [INFO] [stdout] 335 | pub fn unsubscribe>(&self, channel: T) -> BoxFuture { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 335 | pub fn unsubscribe>(&self, channel: T) -> BoxFuture<'_, bool> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/databases/pubsub.rs:352:9 [INFO] [stdout] | [INFO] [stdout] 352 | &self, [INFO] [stdout] | ^^^^^ the lifetime is elided here [INFO] [stdout] ... [INFO] [stdout] 355 | ) -> BoxFuture> { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 355 | ) -> BoxFuture<'_, PuffResult<()>> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item [INFO] [stdout] --> src/json/error.rs:31:17 [INFO] [stdout] | [INFO] [stdout] 31 | #[derive(Debug, Fail)] [INFO] [stdout] | ^--- [INFO] [stdout] | | [INFO] [stdout] | `Fail` is not local [INFO] [stdout] | move the `impl` block outside of this constant `_DERIVE_failure_Fail_FOR_HyperJsonError` [INFO] [stdout] 32 | pub enum HyperJsonError { [INFO] [stdout] | -------------- `HyperJsonError` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `Fail` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `Fail` may come from an old version of the `failure_derive` crate, try updating your dependency with `cargo update -p failure_derive` [INFO] [stdout] = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl` [INFO] [stdout] = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint [INFO] [stdout] = note: `#[warn(non_local_definitions)]` implied by `#[warn(warnings)]` [INFO] [stdout] = note: this warning originates in the derive macro `Fail` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item [INFO] [stdout] --> src/json/error.rs:31:17 [INFO] [stdout] | [INFO] [stdout] 31 | #[derive(Debug, Fail)] [INFO] [stdout] | ^--- [INFO] [stdout] | | [INFO] [stdout] | `Display` is not local [INFO] [stdout] | move the `impl` block outside of this constant `_DERIVE_failure_core_fmt_Display_FOR_HyperJsonError` [INFO] [stdout] 32 | pub enum HyperJsonError { [INFO] [stdout] | -------------- `HyperJsonError` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `Fail` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `Fail` may come from an old version of the `failure_derive` crate, try updating your dependency with `cargo update -p failure_derive` [INFO] [stdout] = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl` [INFO] [stdout] = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint [INFO] [stdout] = note: this warning originates in the derive macro `Fail` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/python/asgi/mod.rs:121:18 [INFO] [stdout] | [INFO] [stdout] 121 | pub fn start(&mut self) -> Result>> { [INFO] [stdout] | ^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 121 | pub fn start(&mut self) -> Result>> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> src/python/wsgi/mod.rs:74:18 [INFO] [stdout] | [INFO] [stdout] 74 | pub fn start(&mut self) -> Result>> { [INFO] [stdout] | ^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 74 | pub fn start(&mut self) -> Result>> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Finished `test` profile [unoptimized + debuginfo] target(s) in 44.22s [INFO] [stderr] warning: the following packages contain code that will be rejected by a future version of Rust: puff-rs v0.1.8 (/opt/rustwide/workdir) [INFO] [stderr] note: to see what the problems were, use the option `--future-incompat-report`, or run `cargo report future-incompatibilities --id 2` [INFO] running `Command { std: "docker" "inspect" "83ee2e70ffdb971c115f153ffe3dde459fdbcc30530f4ba36c61ec574eba7d7e", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "83ee2e70ffdb971c115f153ffe3dde459fdbcc30530f4ba36c61ec574eba7d7e", kill_on_drop: false }` [INFO] [stdout] 83ee2e70ffdb971c115f153ffe3dde459fdbcc30530f4ba36c61ec574eba7d7e [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "RUSTDOCFLAGS=--cap-lints=warn" "-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:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+beta-2025-09-21" "test" "--frozen", kill_on_drop: false }` [INFO] [stdout] ac5c816a7c3870f43351184f46b92d64b708d6bbb8a8f1a8301986262bf1daf2 [INFO] running `Command { std: "docker" "start" "-a" "ac5c816a7c3870f43351184f46b92d64b708d6bbb8a8f1a8301986262bf1daf2", kill_on_drop: false }` [INFO] [stderr] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stderr] --> src/json/error.rs:84:1 [INFO] [stderr] | [INFO] [stderr] 84 | import_exception!(json, JSONDecodeError); [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] note: the lint level is defined here [INFO] [stderr] --> src/lib.rs:2:9 [INFO] [stderr] | [INFO] [stderr] 2 | #![deny(warnings)] [INFO] [stderr] | ^^^^^^^^ [INFO] [stderr] = note: `#[warn(unexpected_cfgs)]` implied by `#[warn(warnings)]` [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `import_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stderr] --> src/json/error.rs:84:1 [INFO] [stderr] | [INFO] [stderr] 84 | import_exception!(json, JSONDecodeError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `import_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: private item shadows public glob re-export [INFO] [stderr] --> src/python/mod.rs:11:5 [INFO] [stderr] | [INFO] [stderr] 11 | use pyo3::wrap_pyfunction; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] note: the name `wrap_pyfunction` in the macro namespace is supposed to be publicly re-exported here [INFO] [stderr] --> src/python/mod.rs:30:9 [INFO] [stderr] | [INFO] [stderr] 30 | pub use pyo3::prelude::*; [INFO] [stderr] | ^^^^^^^^^^^^^^^^ [INFO] [stderr] note: but the private item here shadows it [INFO] [stderr] --> src/python/mod.rs:11:5 [INFO] [stderr] | [INFO] [stderr] 11 | use pyo3::wrap_pyfunction; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] = note: `#[warn(hidden_glob_reexports)]` implied by `#[warn(warnings)]` [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stderr] --> src/python/postgres.rs:32:1 [INFO] [stderr] | [INFO] [stderr] 32 | create_exception!(module, PgError, pyo3::exceptions::PyException); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stderr] --> src/python/postgres.rs:33:1 [INFO] [stderr] | [INFO] [stderr] 33 | create_exception!(module, Warning, pyo3::exceptions::PyException); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stderr] --> src/python/postgres.rs:34:1 [INFO] [stderr] | [INFO] [stderr] 34 | create_exception!(module, InterfaceError, PgError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stderr] --> src/python/postgres.rs:35:1 [INFO] [stderr] | [INFO] [stderr] 35 | create_exception!(module, DatabaseError, PgError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stderr] --> src/python/postgres.rs:36:1 [INFO] [stderr] | [INFO] [stderr] 36 | create_exception!(module, InternalError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stderr] --> src/python/postgres.rs:37:1 [INFO] [stderr] | [INFO] [stderr] 37 | create_exception!(module, OperationalError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stderr] --> src/python/postgres.rs:38:1 [INFO] [stderr] | [INFO] [stderr] 38 | create_exception!(module, ProgrammingError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stderr] --> src/python/postgres.rs:39:1 [INFO] [stderr] | [INFO] [stderr] 39 | create_exception!(module, IntegrityError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stderr] --> src/python/postgres.rs:40:1 [INFO] [stderr] | [INFO] [stderr] 40 | create_exception!(module, DataError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stderr] --> src/python/postgres.rs:41:1 [INFO] [stderr] | [INFO] [stderr] 41 | create_exception!(module, NotSupportedError, DatabaseError); [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::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: this function depends on never type fallback being `()` [INFO] [stderr] --> src/databases/pubsub.rs:375:1 [INFO] [stderr] | [INFO] [stderr] 375 | / pub async fn new_pubsub_async( [INFO] [stderr] 376 | | conn: T, [INFO] [stderr] 377 | | check: bool, [INFO] [stderr] 378 | | pool_size: u32, [INFO] [stderr] 379 | | ) -> PuffResult { [INFO] [stderr] | |_____________________________^ [INFO] [stderr] | [INFO] [stderr] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in Rust 2024 and in a future release in all editions! [INFO] [stderr] = note: for more information, see [INFO] [stderr] = help: specify the types explicitly [INFO] [stderr] note: in edition 2024, the requirement `!: FromRedisValue` will fail [INFO] [stderr] --> src/databases/pubsub.rs:388:51 [INFO] [stderr] | [INFO] [stderr] 388 | PuffResult::Ok(Cmd::new().arg("PING").query_async(&mut *conn).await?) [INFO] [stderr] | ^^^^^^^^^^^ [INFO] [stderr] = note: `#[warn(dependency_on_unit_never_type_fallback)]` implied by `#[warn(warnings)]` [INFO] [stderr] help: use `()` annotations to avoid fallback changes [INFO] [stderr] | [INFO] [stderr] 388 | PuffResult::Ok(Cmd::new().arg("PING").query_async::<_, ()>(&mut *conn).await?) [INFO] [stderr] | +++++++++ [INFO] [stderr] [INFO] [stderr] warning: this function depends on never type fallback being `()` [INFO] [stderr] --> src/databases/redis.rs:27:1 [INFO] [stderr] | [INFO] [stderr] 27 | / pub async fn new_redis_async( [INFO] [stderr] 28 | | conn: T, [INFO] [stderr] 29 | | check: bool, [INFO] [stderr] 30 | | pool_size: u32, [INFO] [stderr] 31 | | ) -> PuffResult { [INFO] [stderr] | |____________________________^ [INFO] [stderr] | [INFO] [stderr] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in Rust 2024 and in a future release in all editions! [INFO] [stderr] = note: for more information, see [INFO] [stderr] = help: specify the types explicitly [INFO] [stderr] note: in edition 2024, the requirement `!: FromRedisValue` will fail [INFO] [stderr] --> src/databases/redis.rs:39:51 [INFO] [stderr] | [INFO] [stderr] 39 | PuffResult::Ok(Cmd::new().arg("PING").query_async(&mut *conn).await?) [INFO] [stderr] | ^^^^^^^^^^^ [INFO] [stderr] help: use `()` annotations to avoid fallback changes [INFO] [stderr] | [INFO] [stderr] 39 | PuffResult::Ok(Cmd::new().arg("PING").query_async::<_, ()>(&mut *conn).await?) [INFO] [stderr] | +++++++++ [INFO] [stderr] [INFO] [stderr] warning: this function depends on never type fallback being `()` [INFO] [stderr] --> src/tasks/mod.rs:148:1 [INFO] [stderr] | [INFO] [stderr] 148 | / pub async fn add_task>( [INFO] [stderr] 149 | | task_queue: TaskQueue, [INFO] [stderr] 150 | | func_path: T, [INFO] [stderr] 151 | | params: serde_json::Value, [INFO] [stderr] ... | [INFO] [stderr] 156 | | trigger: bool, [INFO] [stderr] 157 | | ) -> PuffResult> { [INFO] [stderr] | |____________________________^ [INFO] [stderr] | [INFO] [stderr] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in Rust 2024 and in a future release in all editions! [INFO] [stderr] = note: for more information, see [INFO] [stderr] = help: specify the types explicitly [INFO] [stderr] note: in edition 2024, the requirement `!: FromRedisValue` will fail [INFO] [stderr] --> src/tasks/mod.rs:186:10 [INFO] [stderr] | [INFO] [stderr] 186 | pipe.query_async(&mut *r).await?; [INFO] [stderr] | ^^^^^^^^^^^ [INFO] [stderr] help: use `()` annotations to avoid fallback changes [INFO] [stderr] | [INFO] [stderr] 186 | pipe.query_async::<_, ()>(&mut *r).await?; [INFO] [stderr] | +++++++++ [INFO] [stderr] [INFO] [stderr] warning: this function depends on never type fallback being `()` [INFO] [stderr] --> src/tasks/mod.rs:526:1 [INFO] [stderr] | [INFO] [stderr] 526 | / pub async fn new_task_queue_async( [INFO] [stderr] 527 | | conn: T, [INFO] [stderr] 528 | | check: bool, [INFO] [stderr] 529 | | pool_size: u32, [INFO] [stderr] 530 | | ) -> PuffResult { [INFO] [stderr] | |__________________________^ [INFO] [stderr] | [INFO] [stderr] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in Rust 2024 and in a future release in all editions! [INFO] [stderr] = note: for more information, see [INFO] [stderr] = help: specify the types explicitly [INFO] [stderr] note: in edition 2024, the requirement `!: FromRedisValue` will fail [INFO] [stderr] --> src/tasks/mod.rs:539:51 [INFO] [stderr] | [INFO] [stderr] 539 | PuffResult::Ok(Cmd::new().arg("PING").query_async(&mut *conn).await?) [INFO] [stderr] | ^^^^^^^^^^^ [INFO] [stderr] help: use `()` annotations to avoid fallback changes [INFO] [stderr] | [INFO] [stderr] 539 | PuffResult::Ok(Cmd::new().arg("PING").query_async::<_, ()>(&mut *conn).await?) [INFO] [stderr] | +++++++++ [INFO] [stderr] [INFO] [stderr] warning: field `0` is never read [INFO] [stderr] --> src/graphql/handlers.rs:261:10 [INFO] [stderr] | [INFO] [stderr] 261 | Axum(axum::Error), [INFO] [stderr] | ---- ^^^^^^^^^^^ [INFO] [stderr] | | [INFO] [stderr] | field in this variant [INFO] [stderr] | [INFO] [stderr] = note: `SubscriptionError` has a derived impl for the trait `Debug`, but this is intentionally ignored during dead code analysis [INFO] [stderr] = note: `#[warn(dead_code)]` implied by `#[warn(warnings)]` [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] 261 - Axum(axum::Error), [INFO] [stderr] 261 + Axum(()), [INFO] [stderr] | [INFO] [stderr] [INFO] [stderr] warning: field `0` is never read [INFO] [stderr] --> src/graphql/handlers.rs:262:11 [INFO] [stderr] | [INFO] [stderr] 262 | Serde(serde_json::Error), [INFO] [stderr] | ----- ^^^^^^^^^^^^^^^^^ [INFO] [stderr] | | [INFO] [stderr] | field in this variant [INFO] [stderr] | [INFO] [stderr] = note: `SubscriptionError` has a derived impl for the trait `Debug`, 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] 262 - Serde(serde_json::Error), [INFO] [stderr] 262 + Serde(()), [INFO] [stderr] | [INFO] [stderr] [INFO] [stderr] warning: struct `AggroSqlValue` is never constructed [INFO] [stderr] --> src/graphql/scalar.rs:207:12 [INFO] [stderr] | [INFO] [stderr] 207 | pub struct AggroSqlValue(JuniperValue); [INFO] [stderr] | ^^^^^^^^^^^^^ [INFO] [stderr] [INFO] [stderr] warning: struct `AggroScalarValueVisitor` is never constructed [INFO] [stderr] --> src/graphql/scalar.rs:472:12 [INFO] [stderr] | [INFO] [stderr] 472 | pub struct AggroScalarValueVisitor; [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] [INFO] [stderr] warning: field `0` is never read [INFO] [stderr] --> src/python/asgi/handler.rs:63:11 [INFO] [stderr] | [INFO] [stderr] 63 | PyErr(PyErr), [INFO] [stderr] | ----- ^^^^^ [INFO] [stderr] | | [INFO] [stderr] | field in this variant [INFO] [stderr] | [INFO] [stderr] = note: `AsgiError` has a derived impl for the trait `Debug`, 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] 63 - PyErr(PyErr), [INFO] [stderr] 63 + PyErr(()), [INFO] [stderr] | [INFO] [stderr] [INFO] [stderr] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stderr] --> src/databases/pubsub.rs:264:9 [INFO] [stderr] | [INFO] [stderr] 264 | &self, [INFO] [stderr] | ^^^^^ the lifetime is elided here [INFO] [stderr] ... [INFO] [stderr] 268 | ) -> BoxFuture> { [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stderr] | [INFO] [stderr] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stderr] = note: `#[warn(mismatched_lifetime_syntaxes)]` implied by `#[warn(warnings)]` [INFO] [stderr] help: use `'_` for type paths [INFO] [stderr] | [INFO] [stderr] 268 | ) -> BoxFuture<'_, PuffResult<()>> { [INFO] [stderr] | +++ [INFO] [stderr] [INFO] [stderr] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stderr] --> src/databases/pubsub.rs:319:37 [INFO] [stderr] | [INFO] [stderr] 319 | pub fn subscribe>(&self, channel: T) -> BoxFuture { [INFO] [stderr] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stderr] | | [INFO] [stderr] | the lifetime is elided here [INFO] [stderr] | [INFO] [stderr] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stderr] help: use `'_` for type paths [INFO] [stderr] | [INFO] [stderr] 319 | pub fn subscribe>(&self, channel: T) -> BoxFuture<'_, bool> { [INFO] [stderr] | +++ [INFO] [stderr] [INFO] [stderr] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stderr] --> src/databases/pubsub.rs:335:39 [INFO] [stderr] | [INFO] [stderr] 335 | pub fn unsubscribe>(&self, channel: T) -> BoxFuture { [INFO] [stderr] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stderr] | | [INFO] [stderr] | the lifetime is elided here [INFO] [stderr] | [INFO] [stderr] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stderr] help: use `'_` for type paths [INFO] [stderr] | [INFO] [stderr] 335 | pub fn unsubscribe>(&self, channel: T) -> BoxFuture<'_, bool> { [INFO] [stderr] | +++ [INFO] [stderr] [INFO] [stderr] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stderr] --> src/databases/pubsub.rs:352:9 [INFO] [stderr] | [INFO] [stderr] 352 | &self, [INFO] [stderr] | ^^^^^ the lifetime is elided here [INFO] [stderr] ... [INFO] [stderr] 355 | ) -> BoxFuture> { [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stderr] | [INFO] [stderr] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stderr] help: use `'_` for type paths [INFO] [stderr] | [INFO] [stderr] 355 | ) -> BoxFuture<'_, PuffResult<()>> { [INFO] [stderr] | +++ [INFO] [stderr] [INFO] [stderr] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item [INFO] [stderr] --> src/json/error.rs:31:17 [INFO] [stderr] | [INFO] [stderr] 31 | #[derive(Debug, Fail)] [INFO] [stderr] | ^--- [INFO] [stderr] | | [INFO] [stderr] | `Fail` is not local [INFO] [stderr] | move the `impl` block outside of this constant `_DERIVE_failure_Fail_FOR_HyperJsonError` [INFO] [stderr] 32 | pub enum HyperJsonError { [INFO] [stderr] | -------------- `HyperJsonError` is not local [INFO] [stderr] | [INFO] [stderr] = note: the derive macro `Fail` defines the non-local `impl`, and may need to be changed [INFO] [stderr] = note: the derive macro `Fail` may come from an old version of the `failure_derive` crate, try updating your dependency with `cargo update -p failure_derive` [INFO] [stderr] = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl` [INFO] [stderr] = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint [INFO] [stderr] = note: `#[warn(non_local_definitions)]` implied by `#[warn(warnings)]` [INFO] [stderr] = note: this warning originates in the derive macro `Fail` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item [INFO] [stderr] --> src/json/error.rs:31:17 [INFO] [stderr] | [INFO] [stderr] 31 | #[derive(Debug, Fail)] [INFO] [stderr] | ^--- [INFO] [stderr] | | [INFO] [stderr] | `Display` is not local [INFO] [stderr] | move the `impl` block outside of this constant `_DERIVE_failure_core_fmt_Display_FOR_HyperJsonError` [INFO] [stderr] 32 | pub enum HyperJsonError { [INFO] [stderr] | -------------- `HyperJsonError` is not local [INFO] [stderr] | [INFO] [stderr] = note: the derive macro `Fail` defines the non-local `impl`, and may need to be changed [INFO] [stderr] = note: the derive macro `Fail` may come from an old version of the `failure_derive` crate, try updating your dependency with `cargo update -p failure_derive` [INFO] [stderr] = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl` [INFO] [stderr] = note: items in an anonymous const item (`const _: () = { ... }`) are treated as in the same scope as the anonymous const's declaration for the purpose of this lint [INFO] [stderr] = note: this warning originates in the derive macro `Fail` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stderr] --> src/python/asgi/mod.rs:121:18 [INFO] [stderr] | [INFO] [stderr] 121 | pub fn start(&mut self) -> Result>> { [INFO] [stderr] | ^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stderr] | | [INFO] [stderr] | the lifetime is elided here [INFO] [stderr] | [INFO] [stderr] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stderr] help: use `'_` for type paths [INFO] [stderr] | [INFO] [stderr] 121 | pub fn start(&mut self) -> Result>> { [INFO] [stderr] | +++ [INFO] [stderr] [INFO] [stderr] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stderr] --> src/python/wsgi/mod.rs:74:18 [INFO] [stderr] | [INFO] [stderr] 74 | pub fn start(&mut self) -> Result>> { [INFO] [stderr] | ^^^^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stderr] | | [INFO] [stderr] | the lifetime is elided here [INFO] [stderr] | [INFO] [stderr] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stderr] help: use `'_` for type paths [INFO] [stderr] | [INFO] [stderr] 74 | pub fn start(&mut self) -> Result>> { [INFO] [stderr] | +++ [INFO] [stderr] [INFO] [stderr] warning: `puff-rs` (lib) generated 40 warnings (10 duplicates) (run `cargo fix --lib -p puff-rs` to apply 10 suggestions) [INFO] [stderr] warning: `puff-rs` (lib test) generated 40 warnings (40 duplicates) [INFO] [stderr] warning: this function depends on never type fallback being `()` [INFO] [stderr] --> examples/basic.rs:30:1 [INFO] [stderr] | [INFO] [stderr] 30 | async fn background_task(redis: RedisClient) -> PuffResult { [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in Rust 2024 and in a future release in all editions! [INFO] [stderr] = note: for more information, see [INFO] [stderr] = help: specify the types explicitly [INFO] [stderr] note: in edition 2024, the requirement `!: FromRedisValue` will fail [INFO] [stderr] --> examples/basic.rs:33:10 [INFO] [stderr] | [INFO] [stderr] 33 | conn.set("hello", "world").await?; [INFO] [stderr] | ^^^ [INFO] [stderr] = note: `#[warn(dependency_on_unit_never_type_fallback)]` (part of `#[warn(rust_2024_compatibility)]`) on by default [INFO] [stderr] help: use `()` annotations to avoid fallback changes [INFO] [stderr] | [INFO] [stderr] 33 | conn.set::<_, _, ()>("hello", "world").await?; [INFO] [stderr] | ++++++++++++ [INFO] [stderr] [INFO] [stderr] warning: `puff-rs` (example "basic") generated 1 warning (run `cargo fix --example "basic"` to apply 1 suggestion) [INFO] [stderr] Finished `test` profile [unoptimized + debuginfo] target(s) in 0.51s [INFO] [stderr] warning: the following packages contain code that will be rejected by a future version of Rust: puff-rs v0.1.8 (/opt/rustwide/workdir) [INFO] [stderr] note: to see what the problems were, use the option `--future-incompat-report`, or run `cargo report future-incompatibilities --id 3` [INFO] [stderr] Running unittests src/lib.rs (/opt/rustwide/target/debug/deps/puff_rs-f896a9bb12b31b10) [INFO] [stdout] [INFO] [stdout] running 1 test [INFO] [stdout] test web::server::tests::check_router ... ok [INFO] [stdout] [INFO] [stdout] test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.03s [INFO] [stdout] [INFO] [stderr] Running unittests src/main.rs (/opt/rustwide/target/debug/deps/puff-1093ac0eef639850) [INFO] [stdout] [INFO] [stdout] running 0 tests [INFO] [stdout] [INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s [INFO] [stdout] [INFO] [stderr] Running unittests src/watch.rs (/opt/rustwide/target/debug/deps/puff_watch-bad220400cd20c91) [INFO] [stderr] Doc-tests puff_rs [INFO] [stdout] [INFO] [stdout] running 0 tests [INFO] [stdout] [INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s [INFO] [stdout] [INFO] [stderr] warning: unexpected character `=` [INFO] [stderr] --> src/../readme.md:1:1 [INFO] [stderr] | [INFO] [stderr] 1 | / # ☁ Puff ☁ [INFO] [stderr] 2 | | [INFO] [stderr] 3 | | Python with an async runtime built-in Rust for GraphQL, ASGI, WSGI, Postgres, PubSub, Redis, Distributed Tasks, and HTTP2 Client. [INFO] [stderr] ... | [INFO] [stderr] 624 | | Probably the end game of puff is to have something like gevent's monkeypatch to automatically make existing projects compatible. [INFO] [stderr] | |________________________________________________________________________________________________________________________________^ [INFO] [stderr] | [INFO] [stderr] note: the lint level is defined here [INFO] [stderr] --> src/lib.rs:2:9 [INFO] [stderr] | [INFO] [stderr] 2 | #![deny(warnings)] [INFO] [stderr] | ^^^^^^^^ [INFO] [stderr] = note: `#[warn(rustdoc::invalid_codeblock_attributes)]` implied by `#[warn(warnings)]` [INFO] [stderr] [INFO] [stderr] warning: 1 warning emitted [INFO] [stderr] [INFO] [stdout] [INFO] [stdout] running 47 tests [INFO] [stdout] test src/program/mod.rs - program (line 11) - compile ... ok [INFO] [stdout] test src/program/mod.rs - program::RunnableCommand (line 88) - compile ... ok [INFO] [stdout] test src/types/bytes_builder.rs - types::bytes_builder::BytesBuilder::with_capacity (line 45) ... ok [INFO] [stdout] test src/types/map.rs - types::map::Map::from_hash_map (line 81) ... ok [INFO] [stdout] test src/types/map.rs - types::map::Map::from_builder (line 69) ... ok [INFO] [stdout] test src/types/bytes_builder.rs - types::bytes_builder::BytesBuilder (line 11) ... ok [INFO] [stdout] test src/types/bytes_builder.rs - types::bytes_builder::BytesBuilder::new (line 30) ... ok [INFO] [stdout] test src/types/bytes_builder.rs - types::bytes_builder::BytesBuilder::put_slice (line 70) ... ok [INFO] [stdout] test src/runtime/mod.rs - runtime::RuntimeConfig (line 144) ... ok [INFO] [stdout] test src/types/map.rs - types::map::Map::get_key_value (line 120) ... ok [INFO] [stdout] test src/types/map.rs - types::map::Map (line 18) ... ok [INFO] [stdout] test src/types/map.rs - types::map::Map::get (line 107) ... ok [INFO] [stdout] test src/types/bytes_builder.rs - types::bytes_builder::BytesBuilder::put (line 57) ... ok [INFO] [stdout] test src/types/map.rs - types::map::Map::new (line 57) ... ok [INFO] [stdout] test src/types/map.rs - types::map::Map::is_empty (line 94) ... ok [INFO] [stdout] test src/types/map_builder.rs - types::map_builder::MapBuilder::is_empty (line 108) ... ok [INFO] [stdout] test src/types/map.rs - types::map::Map::len (line 135) ... ok [INFO] [stdout] test src/types/map_builder.rs - types::map_builder::MapBuilder::get (line 92) ... ok [INFO] [stdout] test src/types/map_builder.rs - types::map_builder::MapBuilder (line 16) ... ok [INFO] [stdout] test src/types/mod.rs - types (line 28) ... ok [INFO] [stdout] test src/types/text_builder.rs - types::text_builder::TextBuilder::from_text (line 61) ... ok [INFO] [stdout] test src/types/text_builder.rs - types::text_builder::TextBuilder (line 10) ... ok [INFO] [stdout] test src/types/map_builder.rs - types::map_builder::MapBuilder::len (line 121) ... ok [INFO] [stdout] test src/types/text.rs - types::text::Text (line 33) ... ok [INFO] [stdout] test src/types/map_builder.rs - types::map_builder::MapBuilder::with_capacity (line 54) ... ok [INFO] [stdout] test src/types/map_builder.rs - types::map_builder::MapBuilder::new (line 39) ... ok [INFO] [stdout] test src/types/text_builder.rs - types::text_builder::TextBuilder::push_str (line 75) ... ok [INFO] [stdout] test src/types/map_builder.rs - types::map_builder::MapBuilder::insert (line 73) ... ok [INFO] [stdout] test src/types/text.rs - types::text::Text (line 25) ... ok [INFO] [stdout] test src/types/text_builder.rs - types::text_builder::TextBuilder::push_text (line 94) ... ok [INFO] [stdout] test src/types/vector.rs - types::vector::Vector::len (line 160) ... ok [INFO] [stdout] test src/types/vector.rs - types::vector::Vector::from_vec (line 83) ... ok [INFO] [stdout] test src/types/vector.rs - types::vector::Vector::from_vector_builder (line 95) ... ok [INFO] [stdout] test src/types/vector.rs - types::vector::Vector::is_empty (line 107) ... ok [INFO] [stdout] test src/types/text_builder.rs - types::text_builder::TextBuilder::into_text (line 113) ... ok [INFO] [stdout] test src/types/vector.rs - types::vector::Vector::get (line 123) ... ok [INFO] [stdout] test src/types/vector.rs - types::vector::Vector::new (line 71) ... ok [INFO] [stdout] test src/types/vector.rs - types::vector::Vector (line 18) ... ok [INFO] [stdout] test src/types/vector.rs - types::vector::Vector::slice (line 140) ... ok [INFO] [stdout] test src/web/server.rs - web::server (line 20) - compile ... ok [INFO] [stdout] test src/types/vector_builder.rs - types::vector_builder::VectorBuilder::with_capacity (line 51) ... ok [INFO] [stdout] test src/types/vector_builder.rs - types::vector_builder::VectorBuilder (line 14) ... ok [INFO] [stdout] test src/types/vector_builder.rs - types::vector_builder::VectorBuilder::get (line 96) ... ok [INFO] [stdout] test src/types/vector_builder.rs - types::vector_builder::VectorBuilder::new (line 36) ... ok [INFO] [stdout] test src/types/vector_builder.rs - types::vector_builder::VectorBuilder::is_empty (line 80) ... ok [INFO] [stdout] test src/types/vector_builder.rs - types::vector_builder::VectorBuilder::len (line 110) ... ok [INFO] [stdout] test src/types/vector_builder.rs - types::vector_builder::VectorBuilder::push (line 63) ... ok [INFO] [stdout] [INFO] [stdout] test result: ok. 47 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 71.01s [INFO] [stdout] [INFO] running `Command { std: "docker" "inspect" "ac5c816a7c3870f43351184f46b92d64b708d6bbb8a8f1a8301986262bf1daf2", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "ac5c816a7c3870f43351184f46b92d64b708d6bbb8a8f1a8301986262bf1daf2", kill_on_drop: false }` [INFO] [stdout] ac5c816a7c3870f43351184f46b92d64b708d6bbb8a8f1a8301986262bf1daf2