[INFO] fetching crate puff-rs 0.1.8...
[INFO] documenting puff-rs-0.1.8 against 1.99.0-beta.8 for beta-rustdoc-1.100
[INFO] extracting crate puff-rs 0.1.8 into /workspace/builds/worker-1-tc1/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-1-tc1/source/Cargo.toml
[INFO] validating manifest of crates.io crate puff-rs 0.1.8 on toolchain 1.99.0-beta.8
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+1.99.0-beta.8" "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" "+1.99.0-beta.8" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]  Downloading crates ...
[INFO] [stderr]   Downloaded futures-macro v0.3.25
[INFO] [stderr]   Downloaded futures-io v0.3.25
[INFO] [stderr]   Downloaded tower-http v0.3.4
[INFO] [stderr]   Downloaded uuid v1.2.1
[INFO] [stderr]   Downloaded http-range-header v0.3.0
[INFO] [stderr]   Downloaded async-compression v0.3.15
[INFO] [stderr]   Downloaded stringprep v0.1.2
[INFO] [stderr]   Downloaded generic-array v0.14.6
[INFO] [stderr]   Downloaded block-buffer v0.10.3
[INFO] [stderr]   Downloaded md-5 v0.10.5
[INFO] [stderr]   Downloaded tokio-stream v0.1.11
[INFO] [stderr]   Downloaded digest v0.10.5
[INFO] [stderr]   Downloaded postgres-protocol v0.6.4
[INFO] [stderr]   Downloaded cpufeatures v0.2.5
[INFO] [stderr]   Downloaded tokio-util v0.7.4
[INFO] [stderr]   Downloaded miniz_oxide v0.5.4
[INFO] [stderr]   Downloaded postgres-types v0.2.4
[INFO] [stderr]   Downloaded scratch v1.0.2
[INFO] [stderr]   Downloaded link-cplusplus v1.0.7
[INFO] [stderr]   Downloaded tokio-postgres v0.7.7
[INFO] [stderr]   Downloaded phf_shared v0.11.1
[INFO] [stderr]   Downloaded serde_bytes v0.11.7
[INFO] [stderr]   Downloaded cxx-build v1.0.80
[INFO] [stderr]   Downloaded cxxbridge-flags v1.0.80
[INFO] [stderr]   Downloaded array-init v2.0.1
[INFO] [stderr]   Downloaded wasm-bindgen-futures v0.4.33
[INFO] [stderr]   Downloaded async-trait v0.1.58
[INFO] [stderr]   Downloaded phf v0.11.1
[INFO] [stderr]   Downloaded serde_json v1.0.87
[INFO] [stderr]   Downloaded cxxbridge-macro v1.0.80
[INFO] [stderr]   Downloaded chrono v0.4.22
[INFO] [stderr]   Downloaded reqwest v0.11.12
[INFO] [stderr]   Downloaded cxx v1.0.80
[INFO] [stderr]   Downloaded h2 v0.3.15
[INFO] [stderr]   Downloaded time v0.3.16
[INFO] [stderr]   Downloaded time-macros v0.2.5
[INFO] [stderr]   Downloaded openssl v0.10.42
[INFO] [stderr]   Downloaded hyper v0.14.22
[INFO] [stderr]   Downloaded cookie_store v0.16.1
[INFO] [stderr]   Downloaded time-core v0.1.0
[INFO] [stderr]   Downloaded publicsuffix v2.2.3
[INFO] [stderr]   Downloaded pyo3-ffi v0.17.3
[INFO] [stderr]   Downloaded cookie v0.16.1
[INFO] [stderr]   Downloaded pyo3-chrono v0.5.0
[INFO] [stderr]   Downloaded pyo3-macros v0.17.3
[INFO] [stderr]   Downloaded unindent v0.1.10
[INFO] [stderr]   Downloaded pythonize v0.17.0
[INFO] [stderr]   Downloaded pyo3-build-config v0.17.3
[INFO] [stderr]   Downloaded target-lexicon v0.12.4
[INFO] [stderr]   Downloaded notify v5.0.0
[INFO] [stderr]   Downloaded pyo3-macros-backend v0.17.3
[INFO] [stderr]   Downloaded indoc v1.0.7
[INFO] [stderr]   Downloaded pyo3 v0.17.3
[INFO] [stderr]   Downloaded filetime v0.2.18
[INFO] [stderr]   Downloaded crossbeam-utils v0.8.12
[INFO] [stderr]   Downloaded juniper_codegen_puff v0.16.0-dev
[INFO] [stderr]   Downloaded graphql-parser v0.4.0
[INFO] [stderr]   Downloaded derive_utils v0.11.2
[INFO] [stderr]   Downloaded futures v0.3.25
[INFO] [stderr]   Downloaded juniper_subscriptions_puff v0.17.0-dev
[INFO] [stderr]   Downloaded juniper_puff v0.16.0-dev
[INFO] [stderr]   Downloaded futures-enum v0.1.17
[INFO] [stderr]   Downloaded bson v2.4.0
[INFO] [stderr]   Downloaded futures-executor v0.3.25
[INFO] [stderr]   Downloaded juniper_graphql_ws_puff v0.4.0-dev
[INFO] [stderr]   Downloaded dotenvy v0.15.6
[INFO] [stderr]   Downloaded castaway v0.2.2
[INFO] [stderr]   Downloaded bb8-redis v0.11.0
[INFO] [stderr]   Downloaded bb8-postgres v0.8.1
[INFO] [stderr]   Downloaded backtrace v0.3.66
[INFO] [stderr]   Downloaded compact_str v0.6.1
[INFO] [stderr]   Downloaded rustversion v1.0.9
[INFO] [stderr]   Downloaded tokio-tungstenite v0.17.2
[INFO] [stderr]   Downloaded tungstenite v0.17.3
[INFO] [stderr]   Downloaded os_str_bytes v6.3.1
[INFO] [stderr]   Downloaded object v0.29.0
[INFO] [stderr]   Downloaded clap v4.0.18
[INFO] [stderr]   Downloaded bb8 v0.8.0
[INFO] [stderr]   Downloaded redis v0.21.6
[INFO] [stderr]   Downloaded axum v0.6.0-rc.2
[INFO] [stderr]   Downloaded matchit v0.6.0
[INFO] [stderr]   Downloaded sha1 v0.10.5
[INFO] [stderr]   Downloaded sync_wrapper v0.1.1
[INFO] [stderr]   Downloaded axum-core v0.3.0-rc.2
[INFO] [stderr]   Downloaded anyhow v1.0.66
[INFO] [stderr]   Downloaded headers v0.3.8
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-tc1/target:/opt/rustwide/target:rw,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" "-m" "1610612736" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:77db811e55d90add9212f6832c23229e3de5f1c1f9905e8cb07319ea15df73ac" "sleep" "infinity", kill_on_drop: false }`
[INFO] [stdout] 9d6e6b74ce3f55be986094fa928f42fc09b0b14c5f9db3e9b827d6716db1a597
[INFO] running `Command { std: "docker" "start" "9d6e6b74ce3f55be986094fa928f42fc09b0b14c5f9db3e9b827d6716db1a597", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "9d6e6b74ce3f55be986094fa928f42fc09b0b14c5f9db3e9b827d6716db1a597", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "exec" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-w" "/opt/rustwide/workdir" "--user" "0:0" "9d6e6b74ce3f55be986094fa928f42fc09b0b14c5f9db3e9b827d6716db1a597" "/opt/rustwide/cargo-home/bin/cargo" "+1.99.0-beta.8" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "9d6e6b74ce3f55be986094fa928f42fc09b0b14c5f9db3e9b827d6716db1a597", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "exec" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "RUSTDOCFLAGS=--cap-lints=warn" "-w" "/opt/rustwide/workdir" "--user" "0:0" "9d6e6b74ce3f55be986094fa928f42fc09b0b14c5f9db3e9b827d6716db1a597" "/opt/rustwide/cargo-home/bin/cargo" "+1.99.0-beta.8" "doc" "--frozen" "--no-deps" "--document-private-items" "--message-format=json", kill_on_drop: false }`
[INFO] [stderr]    Compiling proc-macro2 v1.0.47
[INFO] [stderr]    Compiling quote v1.0.21
[INFO] [stderr]    Compiling unicode-ident v1.0.5
[INFO] [stderr]    Compiling syn v1.0.103
[INFO] [stderr]    Compiling libc v0.2.137
[INFO] [stderr]    Compiling memchr v2.5.0
[INFO] [stderr]    Compiling log v0.4.17
[INFO] [stderr]     Checking itoa v1.0.4
[INFO] [stderr]     Checking pin-project-lite v0.2.9
[INFO] [stderr]     Checking bytes v1.2.1
[INFO] [stderr]    Compiling futures-core v0.3.25
[INFO] [stderr]    Compiling serde_derive v1.0.147
[INFO] [stderr]     Checking once_cell v1.16.0
[INFO] [stderr]    Compiling lock_api v0.4.9
[INFO] [stderr]    Compiling serde v1.0.147
[INFO] [stderr]     Checking smallvec v1.10.0
[INFO] [stderr]    Compiling parking_lot_core v0.9.4
[INFO] [stderr]     Checking 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 tokio v1.21.2
[INFO] [stderr]    Compiling futures-util v0.3.25
[INFO] [stderr]     Checking tinyvec v1.6.0
[INFO] [stderr]     Checking futures-io v0.3.25
[INFO] [stderr]     Checking unicode-bidi v0.3.8
[INFO] [stderr]    Compiling generic-array v0.14.6
[INFO] [stderr]     Checking tracing-core v0.1.30
[INFO] [stderr]    Compiling indexmap v1.9.1
[INFO] [stderr]     Checking percent-encoding v2.2.0
[INFO] [stderr]     Checking ryu v1.0.11
[INFO] [stderr]    Compiling cc v1.0.74
[INFO] [stderr]     Checking ppv-lite86 v0.2.16
[INFO] [stderr]     Checking subtle v2.4.1
[INFO] [stderr]    Compiling target-lexicon v0.12.4
[INFO] [stderr]     Checking form_urlencoded v1.1.0
[INFO] [stderr]     Checking http v0.2.8
[INFO] [stderr]    Compiling num-traits v0.2.15
[INFO] [stderr]     Checking byteorder v1.4.3
[INFO] [stderr]    Compiling serde_json v1.0.87
[INFO] [stderr]    Compiling async-trait v0.1.58
[INFO] [stderr]    Compiling num-integer v0.1.45
[INFO] [stderr]     Checking cpufeatures v0.2.5
[INFO] [stderr]    Compiling pkg-config v0.3.26
[INFO] [stderr]     Checking mio v0.8.5
[INFO] [stderr]     Checking signal-hook-registry v1.4.0
[INFO] [stderr]     Checking num_cpus v1.13.1
[INFO] [stderr]     Checking socket2 v0.4.7
[INFO] [stderr]     Checking getrandom v0.2.8
[INFO] [stderr]     Checking time v0.1.44
[INFO] [stderr]    Compiling thiserror v1.0.37
[INFO] [stderr]     Checking parking_lot v0.12.1
[INFO] [stderr]     Checking rand_core v0.6.4
[INFO] [stderr]     Checking unicode-normalization v0.1.22
[INFO] [stderr]     Checking iana-time-zone v0.1.53
[INFO] [stderr]    Compiling time-core v0.1.0
[INFO] [stderr]     Checking num_threads v0.1.6
[INFO] [stderr]    Compiling time-macros v0.2.5
[INFO] [stderr]     Checking rand_chacha v0.3.1
[INFO] [stderr]     Checking miniz_oxide v0.5.4
[INFO] [stderr]     Checking block-buffer v0.10.3
[INFO] [stderr]     Checking crypto-common v0.1.6
[INFO] [stderr]    Compiling unicase v2.6.0
[INFO] [stderr]    Compiling crc32fast v1.3.2
[INFO] [stderr]    Compiling openssl v0.10.42
[INFO] [stderr]     Checking digest v0.10.5
[INFO] [stderr]    Compiling pyo3-build-config v0.17.3
[INFO] [stderr]     Checking rand v0.8.5
[INFO] [stderr]     Checking idna v0.3.0
[INFO] [stderr]    Compiling proc-macro-error-attr v1.0.4
[INFO] [stderr]     Checking brotli-decompressor v2.3.2
[INFO] [stderr]    Compiling smartstring v1.0.1
[INFO] [stderr]    Compiling memoffset v0.6.5
[INFO] [stderr]     Checking http-body v0.4.5
[INFO] [stderr]     Checking either v1.8.0
[INFO] [stderr]    Compiling native-tls v0.2.10
[INFO] [stderr]     Checking mime v0.3.16
[INFO] [stderr]     Checking httpdate v1.0.2
[INFO] [stderr]     Checking combine v3.8.1
[INFO] [stderr]     Checking flate2 v1.0.24
[INFO] [stderr]     Checking want v0.3.0
[INFO] [stderr]     Checking url v2.3.1
[INFO] [stderr]     Checking ahash v0.7.6
[INFO] [stderr]     Checking sha2 v0.10.6
[INFO] [stderr]     Checking hmac v0.12.1
[INFO] [stderr]     Checking md-5 v0.10.5
[INFO] [stderr]     Checking stringprep v0.1.2
[INFO] [stderr]    Compiling openssl-sys v0.9.77
[INFO] [stderr]    Compiling cookie v0.16.1
[INFO] [stderr]     Checking siphasher v0.3.10
[INFO] [stderr]     Checking tower-layer v0.3.2
[INFO] [stderr]    Compiling rustversion v1.0.9
[INFO] [stderr]    Compiling crossbeam-utils v0.8.12
[INFO] [stderr]     Checking fallible-iterator v0.2.0
[INFO] [stderr]     Checking time v0.3.16
[INFO] [stderr]    Compiling backtrace v0.3.66
[INFO] [stderr]     Checking phf_shared v0.11.1
[INFO] [stderr]    Compiling mime_guess v2.0.4
[INFO] [stderr]     Checking sha-1 v0.10.0
[INFO] [stderr]     Checking brotli v3.3.4
[INFO] [stderr]     Checking psl-types v2.0.11
[INFO] [stderr]    Compiling proc-macro-hack v0.5.19
[INFO] [stderr]     Checking array-init v2.0.1
[INFO] [stderr]     Checking gimli v0.26.2
[INFO] [stderr]     Checking unindent v0.1.10
[INFO] [stderr]    Compiling unicode-xid v0.2.4
[INFO] [stderr]    Compiling indoc v1.0.7
[INFO] [stderr]    Compiling encoding_rs v0.8.31
[INFO] [stderr]    Compiling failure_derive v0.1.8
[INFO] [stderr]     Checking postgres-protocol v0.6.4
[INFO] [stderr]     Checking phf v0.11.1
[INFO] [stderr]     Checking idna v0.2.3
[INFO] [stderr]     Checking publicsuffix v2.2.3
[INFO] [stderr]     Checking headers-core v0.2.0
[INFO] [stderr]     Checking sha1 v0.10.5
[INFO] [stderr]     Checking inotify-sys v0.1.5
[INFO] [stderr]     Checking object v0.29.0
[INFO] [stderr]    Compiling anyhow v1.0.66
[INFO] [stderr]     Checking http-range-header v0.3.0
[INFO] [stderr]     Checking overload v0.1.1
[INFO] [stderr]     Checking rustc-demangle v0.1.21
[INFO] [stderr]     Checking os_str_bytes v6.3.1
[INFO] [stderr]     Checking walkdir v2.3.2
[INFO] [stderr]     Checking crossbeam-channel v0.5.6
[INFO] [stderr]     Checking clap_lex v0.3.0
[INFO] [stderr]     Checking headers v0.3.8
[INFO] [stderr]     Checking nu-ansi-term v0.46.0
[INFO] [stderr]     Checking inotify v0.9.6
[INFO] [stderr]     Checking tracing-log v0.1.3
[INFO] [stderr]     Checking castaway v0.2.2
[INFO] [stderr]     Checking sharded-slab v0.1.4
[INFO] [stderr]     Checking atty v0.2.14
[INFO] [stderr]     Checking filetime v0.2.18
[INFO] [stderr]     Checking thread_local v1.1.4
[INFO] [stderr]     Checking matchit v0.6.0
[INFO] [stderr]     Checking termcolor v1.1.3
[INFO] [stderr]     Checking stable_deref_trait v1.2.0
[INFO] [stderr]     Checking sync_wrapper v0.1.1
[INFO] [stderr]     Checking ipnet v2.5.0
[INFO] [stderr]     Checking owning_ref v0.4.1
[INFO] [stderr]     Checking clap v4.0.18
[INFO] [stderr]    Compiling pyo3-ffi v0.17.3
[INFO] [stderr]    Compiling pyo3 v0.17.3
[INFO] [stderr]     Checking dotenvy v0.15.6
[INFO] [stderr]     Checking notify v5.0.0
[INFO] [stderr]     Checking tracing-subscriber v0.3.16
[INFO] [stderr]     Checking addr2line v0.17.0
[INFO] [stderr]    Compiling proc-macro-error v1.0.4
[INFO] [stderr]    Compiling pyo3-macros-backend v0.17.3
[INFO] [stderr]    Compiling derive_utils v0.11.2
[INFO] [stderr]    Compiling synstructure v0.12.6
[INFO] [stderr]    Compiling futures-macro v0.3.25
[INFO] [stderr]    Compiling tokio-macros v1.8.0
[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 futures-enum v0.1.17
[INFO] [stderr]    Compiling juniper_codegen_puff v0.16.0-dev
[INFO] [stderr]     Checking failure v0.1.8
[INFO] [stderr]     Checking graphql-parser v0.4.0
[INFO] [stderr]     Checking tungstenite v0.17.3
[INFO] [stderr]     Checking pin-project v1.0.12
[INFO] [stderr]     Checking tracing v0.1.37
[INFO] [stderr]    Compiling pyo3-macros v0.17.3
[INFO] [stderr]     Checking futures-executor v0.3.25
[INFO] [stderr]     Checking axum-core v0.3.0-rc.2
[INFO] [stderr]     Checking futures v0.3.25
[INFO] [stderr]     Checking chrono v0.4.22
[INFO] [stderr]     Checking uuid v1.2.1
[INFO] [stderr]     Checking serde_bytes v0.11.7
[INFO] [stderr]     Checking serde_urlencoded v0.7.1
[INFO] [stderr]     Checking bincode v1.3.3
[INFO] [stderr]     Checking compact_str v0.6.1
[INFO] [stderr]     Checking toml v0.5.9
[INFO] [stderr]     Checking pythonize v0.17.0
[INFO] [stderr]     Checking tokio-util v0.7.4
[INFO] [stderr]     Checking async-compression v0.3.15
[INFO] [stderr]     Checking tower v0.4.13
[INFO] [stderr]     Checking tokio-native-tls v0.3.0
[INFO] [stderr]     Checking bb8 v0.8.0
[INFO] [stderr]     Checking tokio-tungstenite v0.17.2
[INFO] [stderr]     Checking tokio-stream v0.1.11
[INFO] [stderr]     Checking h2 v0.3.15
[INFO] [stderr]     Checking combine v4.6.6
[INFO] [stderr]     Checking tower-http v0.3.4
[INFO] [stderr]     Checking pyo3-chrono v0.5.0
[INFO] [stderr]     Checking bson v2.4.0
[INFO] [stderr]     Checking postgres-types v0.2.4
[INFO] [stderr]     Checking cookie_store v0.16.1
[INFO] [stderr]     Checking tokio-postgres v0.7.7
[INFO] [stderr]     Checking bb8-postgres v0.8.1
[INFO] [stderr]     Checking juniper_puff v0.16.0-dev
[INFO] [stderr]     Checking hyper v0.14.22
[INFO] [stderr]     Checking redis v0.21.6
[INFO] [stderr]     Checking juniper_subscriptions_puff v0.17.0-dev
[INFO] [stderr]     Checking bb8-redis v0.11.0
[INFO] [stderr]     Checking juniper_graphql_ws_puff v0.4.0-dev
[INFO] [stderr]     Checking hyper-tls v0.5.0
[INFO] [stderr]     Checking axum v0.6.0-rc.2
[INFO] [stderr]     Checking reqwest v0.11.12
[INFO] [stderr]     Checking puff-rs v0.1.8 (/opt/rustwide/workdir)
[INFO] [stderr]  Documenting 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 34 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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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/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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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/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 34 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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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: use of deprecated constant `std::f64::NAN`: replaced by the `NAN` associated constant on `f64`
[INFO] [stdout]    --> src/json/mod.rs:518:32
[INFO] [stdout]     |
[INFO] [stdout] 518 |         b"NaN" => Ok(std::f64::NAN.to_object(py)),
[INFO] [stdout]     |                                ^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: `#[warn(deprecated)]` implied by `#[warn(warnings)]`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated constant `std::f64::INFINITY`: replaced by the `INFINITY` associated constant on `f64`
[INFO] [stdout]    --> src/json/mod.rs:519:37
[INFO] [stdout]     |
[INFO] [stdout] 519 |         b"Infinity" => Ok(std::f64::INFINITY.to_object(py)),
[INFO] [stdout]     |                                     ^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: use of deprecated constant `std::f64::NEG_INFINITY`: replaced by the `NEG_INFINITY` associated constant on `f64`
[INFO] [stdout]    --> src/json/mod.rs:520:38
[INFO] [stdout]     |
[INFO] [stdout] 520 |         b"-Infinity" => Ok(std::f64::NEG_INFINITY.to_object(py)),
[INFO] [stdout]     |                                      ^^^^^^^^^^^^
[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<T: IntoConnectionInfo>(
[INFO] [stdout] 376 | |     conn: T,
[INFO] [stdout] 377 | |     check: bool,
[INFO] [stdout] 378 | |     pool_size: u32,
[INFO] [stdout] 379 | | ) -> PuffResult<PubSubClient> {
[INFO] [stdout]     | |_____________________________^
[INFO] [stdout]     |
[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]     = 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 <https://doc.rust-lang.org/edition-guide/rust-2024/never-type-fallback.html>
[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] 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<T: IntoConnectionInfo>(
[INFO] [stdout] 28 | |     conn: T,
[INFO] [stdout] 29 | |     check: bool,
[INFO] [stdout] 30 | |     pool_size: u32,
[INFO] [stdout] 31 | | ) -> PuffResult<RedisClient> {
[INFO] [stdout]    | |____________________________^
[INFO] [stdout]    |
[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]    = 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 <https://doc.rust-lang.org/edition-guide/rust-2024/never-type-fallback.html>
[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<T: Into<Text>>(
[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<Py<PyBytes>> {
[INFO] [stdout]     | |____________________________^
[INFO] [stdout]     |
[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]     = 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 <https://doc.rust-lang.org/edition-guide/rust-2024/never-type-fallback.html>
[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<T: IntoConnectionInfo>(
[INFO] [stdout] 527 | |     conn: T,
[INFO] [stdout] 528 | |     check: bool,
[INFO] [stdout] 529 | |     pool_size: u32,
[INFO] [stdout] 530 | | ) -> PuffResult<TaskQueue> {
[INFO] [stdout]     | |__________________________^
[INFO] [stdout]     |
[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]     = 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 <https://doc.rust-lang.org/edition-guide/rust-2024/never-type-fallback.html>
[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: unexpected character `=`
[INFO] [stdout]    --> src/../readme.md:1:1
[INFO] [stdout]     |
[INFO] [stdout]   1 | / # ☁ Puff ☁
[INFO] [stdout]   2 | |
[INFO] [stdout]   3 | | Python with an async runtime built-in Rust for GraphQL, ASGI, WSGI, Postgres, PubSub, Redis, Distributed Tasks, and HTTP2 Client.
[INFO] [stdout] ...   |
[INFO] [stdout] 624 | | Probably the end game of puff is to have something like gevent's monkeypatch to automatically make existing projects compatible.
[INFO] [stdout]     | |________________________________________________________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: `#[warn(rustdoc::invalid_codeblock_attributes)]` implied by `#[warn(warnings)]`
[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<AggroScalarValue>);
[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<PuffResult<()>> {
[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<T: Into<Text>>(&self, channel: T) -> BoxFuture<bool> {
[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<T: Into<Text>>(&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<T: Into<Text>>(&self, channel: T) -> BoxFuture<bool> {
[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<T: Into<Text>>(&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<PuffResult<()>> {
[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<LocalBoxFuture<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<LocalBoxFuture<'_, 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<LocalBoxFuture<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<LocalBoxFuture<'_, Result<()>>> {
[INFO] [stdout]    |                                                      +++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished `dev` profile [unoptimized + debuginfo] target(s) in 50.52s
[INFO] [stderr] warning: the following packages contain code that will be rejected by a future version of Rust: openssl v0.10.42, 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] [stderr]    Generated /opt/rustwide/target/doc/puff_rs/index.html and 2 other files
[INFO] running `Command { std: "docker" "inspect" "9d6e6b74ce3f55be986094fa928f42fc09b0b14c5f9db3e9b827d6716db1a597", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "exec" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "RUSTDOCFLAGS=--cap-lints=warn" "-e" "RUSTC_BOOTSTRAP=1" "-e" "DOCS_RS=1" "-w" "/opt/rustwide/workdir" "--user" "0:0" "9d6e6b74ce3f55be986094fa928f42fc09b0b14c5f9db3e9b827d6716db1a597" "/opt/rustwide/cargo-home/bin/cargo" "+1.99.0-beta.8" "rustdoc" "--lib" "-Zrustdoc-map" "--config" "build.rustdocflags=[\"--cfg\", \"docsrs\", \"-Z\", \"unstable-options\", \"--document-private-items\"]" "--frozen" "--message-format=json", kill_on_drop: false }`
[INFO] [stderr]  Documenting 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 34 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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> 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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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/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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the macro `$crate::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 character `=`
[INFO] [stdout]    --> src/../readme.md:1:1
[INFO] [stdout]     |
[INFO] [stdout]   1 | / # ☁ Puff ☁
[INFO] [stdout]   2 | |
[INFO] [stdout]   3 | | Python with an async runtime built-in Rust for GraphQL, ASGI, WSGI, Postgres, PubSub, Redis, Distributed Tasks, and HTTP2 Client.
[INFO] [stdout] ...   |
[INFO] [stdout] 624 | | Probably the end game of puff is to have something like gevent's monkeypatch to automatically make existing projects compatible.
[INFO] [stdout]     | |________________________________________________________________________________________________________________________________^
[INFO] [stdout]     |
[INFO] [stdout]     = note: `#[warn(rustdoc::invalid_codeblock_attributes)]` implied by `#[warn(warnings)]`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished `dev` profile [unoptimized + debuginfo] target(s) in 2.89s
[INFO] [stderr] warning: the following packages contain code that will be rejected by a future version of Rust: openssl v0.10.42
[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]    Generated /opt/rustwide/target/doc/puff_rs/index.html
[INFO] running `Command { std: "docker" "inspect" "9d6e6b74ce3f55be986094fa928f42fc09b0b14c5f9db3e9b827d6716db1a597", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "9d6e6b74ce3f55be986094fa928f42fc09b0b14c5f9db3e9b827d6716db1a597", kill_on_drop: false }`
[INFO] [stdout] 9d6e6b74ce3f55be986094fa928f42fc09b0b14c5f9db3e9b827d6716db1a597
