[INFO] fetching crate pyonear 0.2.0...
[INFO] checking pyonear-0.2.0 against try#78c81ee3917a99dcff6e2e6822800f0492c415c3 for pr-148967
[INFO] extracting crate pyonear 0.2.0 into /workspace/builds/worker-3-tc2/source
[INFO] started tweaking crates.io crate pyonear 0.2.0
[INFO] finished tweaking crates.io crate pyonear 0.2.0
[INFO] tweaked toml for crates.io crate pyonear 0.2.0 written to /workspace/builds/worker-3-tc2/source/Cargo.toml
[INFO] validating manifest of crates.io crate pyonear 0.2.0 on toolchain 78c81ee3917a99dcff6e2e6822800f0492c415c3
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+78c81ee3917a99dcff6e2e6822800f0492c415c3" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+78c81ee3917a99dcff6e2e6822800f0492c415c3" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] [stderr]     Updating crates.io index
[INFO] [stderr]      Locking 267 packages to latest compatible versions
[INFO] [stderr]       Adding borsh v0.9.3 (available: v1.5.7)
[INFO] [stderr]       Adding derive_more v0.99.20 (available: v2.0.1)
[INFO] [stderr]       Adding ed25519-dalek v1.0.1 (available: v2.2.0)
[INFO] [stderr]       Adding generic-array v0.14.7 (available: v0.14.9)
[INFO] [stderr]       Adding near-crypto v0.15.0 (available: v0.33.0)
[INFO] [stderr]       Adding near-primitives v0.15.0 (available: v0.33.0)
[INFO] [stderr]       Adding near-primitives-core v0.15.0 (available: v0.33.0)
[INFO] [stderr]       Adding near-vm-errors v0.15.0 (available: v3.1.0)
[INFO] [stderr]       Adding pyo3 v0.18.3 (available: v0.27.1)
[INFO] [stderr]       Adding secp256k1 v0.24.3 (available: v0.31.1)
[INFO] [stderr]       Adding serde_with v2.3.3 (available: v3.16.0)
[INFO] [stderr]       Adding solders-macros v0.14.4 (available: v0.22.0)
[INFO] [stderr]       Adding solders-traits v0.14.4 (available: v0.21.0)
[INFO] [stderr]       Adding zeroize v1.3.0 (available: v1.8.2)
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+78c81ee3917a99dcff6e2e6822800f0492c415c3" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:4848fb76d95f26979359cc7e45710b1dbc8f3acb7aeedee7c460d7702230f228" "/opt/rustwide/cargo-home/bin/cargo" "+78c81ee3917a99dcff6e2e6822800f0492c415c3" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 4146f0d5f7d2aa9fcf06cb8e4bdde2ad4186a69912bb44b718ee4acca222e693
[INFO] running `Command { std: "docker" "start" "-a" "4146f0d5f7d2aa9fcf06cb8e4bdde2ad4186a69912bb44b718ee4acca222e693", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "4146f0d5f7d2aa9fcf06cb8e4bdde2ad4186a69912bb44b718ee4acca222e693", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "4146f0d5f7d2aa9fcf06cb8e4bdde2ad4186a69912bb44b718ee4acca222e693", kill_on_drop: false }`
[INFO] [stdout] 4146f0d5f7d2aa9fcf06cb8e4bdde2ad4186a69912bb44b718ee4acca222e693
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:4848fb76d95f26979359cc7e45710b1dbc8f3acb7aeedee7c460d7702230f228" "/opt/rustwide/cargo-home/bin/cargo" "+78c81ee3917a99dcff6e2e6822800f0492c415c3" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] caae24db23b5e523a58a61d12f7f3b0fdf03681b4e9fcf5dffafba3543b545f4
[INFO] running `Command { std: "docker" "start" "-a" "caae24db23b5e523a58a61d12f7f3b0fdf03681b4e9fcf5dffafba3543b545f4", kill_on_drop: false }`
[INFO] [stderr]     Checking subtle v2.6.1
[INFO] [stderr]    Compiling generic-array v0.14.7
[INFO] [stderr]    Compiling serde_core v1.0.228
[INFO] [stderr]    Compiling serde v1.0.228
[INFO] [stderr]    Compiling crunchy v0.2.4
[INFO] [stderr]    Compiling libc v0.2.177
[INFO] [stderr]    Compiling semver v1.0.27
[INFO] [stderr]     Checking cpufeatures v0.2.17
[INFO] [stderr]    Compiling zeroize_derive v1.4.2
[INFO] [stderr]     Checking num-integer v0.1.46
[INFO] [stderr]     Checking getrandom v0.1.16
[INFO] [stderr]    Compiling num-traits v0.2.19
[INFO] [stderr]    Compiling ahash v0.7.8
[INFO] [stderr]     Checking rand_chacha v0.3.1
[INFO] [stderr]    Compiling target-lexicon v0.12.16
[INFO] [stderr]    Compiling ahash v0.8.12
[INFO] [stderr]     Checking opaque-debug v0.3.1
[INFO] [stderr]    Compiling borsh-derive-internal v0.9.3
[INFO] [stderr]    Compiling borsh-schema-derive-internal v0.9.3
[INFO] [stderr]     Checking byteorder v1.5.0
[INFO] [stderr]     Checking rand_core v0.5.1
[INFO] [stderr]    Compiling rustc_version v0.4.1
[INFO] [stderr]     Checking rand v0.8.5
[INFO] [stderr]     Checking rand_chacha v0.2.2
[INFO] [stderr]    Compiling wasm-bindgen-shared v0.2.105
[INFO] [stderr]    Compiling toml_parser v1.0.4
[INFO] [stderr]     Checking num-bigint v0.4.6
[INFO] [stderr]     Checking rand v0.7.3
[INFO] [stderr]     Checking hashbrown v0.11.2
[INFO] [stderr]    Compiling ark-serialize-derive v0.4.2
[INFO] [stderr]     Checking zeroize v1.3.0
[INFO] [stderr]    Compiling toml_datetime v0.7.3
[INFO] [stderr]    Compiling digest v0.9.0
[INFO] [stderr]     Checking hashbrown v0.13.2
[INFO] [stderr]     Checking itertools v0.10.5
[INFO] [stderr]    Compiling libsecp256k1-core v0.2.2
[INFO] [stderr]    Compiling toml_edit v0.23.7
[INFO] [stderr]    Compiling ark-ff-asm v0.4.2
[INFO] [stderr]    Compiling derivative v2.2.0
[INFO] [stderr]     Checking ark-std v0.4.0
[INFO] [stderr]     Checking bs58 v0.4.0
[INFO] [stderr]    Compiling jobserver v0.1.34
[INFO] [stderr]     Checking block-buffer v0.10.4
[INFO] [stderr]     Checking crypto-common v0.1.7
[INFO] [stderr]     Checking crypto-mac v0.8.0
[INFO] [stderr]     Checking block-buffer v0.9.0
[INFO] [stderr]    Compiling pyo3-build-config v0.18.3
[INFO] [stderr]     Checking curve25519-dalek v3.2.1
[INFO] [stderr]     Checking digest v0.10.7
[INFO] [stderr]    Compiling feature-probe v0.1.1
[INFO] [stderr]     Checking signature v1.6.4
[INFO] [stderr]    Compiling darling_core v0.20.11
[INFO] [stderr]     Checking sha2 v0.9.9
[INFO] [stderr]     Checking ed25519 v1.5.3
[INFO] [stderr]    Compiling cc v1.2.46
[INFO] [stderr]     Checking sha2 v0.10.9
[INFO] [stderr]    Compiling libsecp256k1-gen-ecmult v0.2.1
[INFO] [stderr]    Compiling libsecp256k1-gen-genmult v0.2.1
[INFO] [stderr]    Compiling bv v0.11.1
[INFO] [stderr]     Checking hmac v0.8.1
[INFO] [stderr]    Compiling solana-frozen-abi-macro v1.18.26
[INFO] [stderr]     Checking bitmaps v2.1.0
[INFO] [stderr]    Compiling im v15.1.0
[INFO] [stderr]    Compiling bumpalo v3.19.0
[INFO] [stderr]     Checking serde_json v1.0.145
[INFO] [stderr]     Checking ark-serialize v0.4.2
[INFO] [stderr]    Compiling borsh v1.5.7
[INFO] [stderr]    Compiling libsecp256k1 v0.6.0
[INFO] [stderr]    Compiling proc-macro-crate v3.4.0
[INFO] [stderr]    Compiling wasm-bindgen-macro-support v0.2.105
[INFO] [stderr]     Checking rayon v1.11.0
[INFO] [stderr]    Compiling solana-frozen-abi v1.18.26
[INFO] [stderr]     Checking rand_xoshiro v0.6.0
[INFO] [stderr]    Compiling wasm-bindgen v0.2.105
[INFO] [stderr]     Checking ed25519-dalek v1.0.1
[INFO] [stderr]    Compiling borsh-derive-internal v0.10.4
[INFO] [stderr]    Compiling borsh-schema-derive-internal v0.10.4
[INFO] [stderr]    Compiling memoffset v0.9.1
[INFO] [stderr]    Compiling num-bigint v0.3.3
[INFO] [stderr]     Checking sized-chunks v0.6.5
[INFO] [stderr]     Checking unicode-ident v1.0.22
[INFO] [stderr]     Checking hmac-drbg v0.3.0
[INFO] [stderr]     Checking pbkdf2 v0.4.0
[INFO] [stderr]     Checking serde_bytes v0.11.19
[INFO] [stderr]     Checking memmap2 v0.5.10
[INFO] [stderr]     Checking atty v0.2.14
[INFO] [stderr]    Compiling borsh-derive v1.5.7
[INFO] [stderr]    Compiling num-rational v0.3.2
[INFO] [stderr]    Compiling memoffset v0.8.0
[INFO] [stderr]     Checking base64 v0.12.3
[INFO] [stderr]    Compiling convert_case v0.4.0
[INFO] [stderr]    Compiling pyo3-ffi v0.18.3
[INFO] [stderr]     Checking constant_time_eq v0.3.1
[INFO] [stderr]     Checking uint v0.9.5
[INFO] [stderr]     Checking tiny-bip39 v0.8.2
[INFO] [stderr]     Checking env_logger v0.9.3
[INFO] [stderr]     Checking chrono v0.4.42
[INFO] [stderr]    Compiling secp256k1-sys v0.6.1
[INFO] [stderr]    Compiling blake3 v1.8.2
[INFO] [stderr]    Compiling solana-program v1.18.26
[INFO] [stderr]    Compiling solana-sdk-macro v1.18.26
[INFO] [stderr]     Checking sha3 v0.10.8
[INFO] [stderr]    Compiling derive_more v0.99.20
[INFO] [stderr]    Compiling pyo3 v0.18.3
[INFO] [stderr]    Compiling num_enum_derive v0.7.5
[INFO] [stderr]     Checking bytemuck v1.24.0
[INFO] [stderr]     Checking fixed-hash v0.7.0
[INFO] [stderr]    Compiling toml v0.5.11
[INFO] [stderr]    Compiling near-rpc-error-core v0.15.0
[INFO] [stderr]     Checking hmac v0.12.1
[INFO] [stderr]    Compiling ark-ff-macros v0.4.2
[INFO] [stderr]     Checking cipher v0.2.5
[INFO] [stderr]    Compiling solana-sdk v1.18.26
[INFO] [stderr]     Checking bincode v1.3.3
[INFO] [stderr]    Compiling pyo3-macros-backend v0.18.3
[INFO] [stderr]    Compiling num-derive v0.4.2
[INFO] [stderr]    Compiling darling_macro v0.20.11
[INFO] [stderr]     Checking bitflags v2.10.0
[INFO] [stderr]    Compiling reed-solomon-erasure v4.0.2
[INFO] [stderr]     Checking derivation-path v0.2.0
[INFO] [stderr]     Checking uriparse v0.6.4
[INFO] [stderr]    Compiling proc-macro-crate v0.1.5
[INFO] [stderr]    Compiling darling v0.20.11
[INFO] [stderr]    Compiling serde_with_macros v2.3.3
[INFO] [stderr]     Checking num_enum v0.7.5
[INFO] [stderr]     Checking ed25519-dalek-bip32 v0.2.0
[INFO] [stderr]     Checking ark-ff v0.4.2
[INFO] [stderr]     Checking qstring v0.7.2
[INFO] [stderr]    Compiling near-rpc-error-macro v0.15.0
[INFO] [stderr]     Checking c2-chacha v0.3.3
[INFO] [stderr]    Compiling wasm-bindgen-macro v0.2.105
[INFO] [stderr]     Checking primitive-types v0.10.1
[INFO] [stderr]     Checking solana-logger v1.18.26
[INFO] [stderr]     Checking pbkdf2 v0.11.0
[INFO] [stderr]     Checking blake2 v0.9.2
[INFO] [stderr]    Compiling qualifier_attr v0.2.2
[INFO] [stderr]     Checking unindent v0.1.11
[INFO] [stderr]     Checking assert_matches v1.5.0
[INFO] [stderr]     Checking siphasher v0.3.11
[INFO] [stderr]     Checking half v1.8.3
[INFO] [stderr]    Compiling indoc v1.0.9
[INFO] [stderr]    Compiling borsh-derive v0.9.3
[INFO] [stderr]    Compiling borsh-derive v0.10.4
[INFO] [stderr]     Checking serde_cbor v0.11.2
[INFO] [stderr]    Compiling smart-default v0.6.0
[INFO] [stderr]    Compiling easy-ext v0.2.9
[INFO] [stderr]     Checking bytesize v1.3.3
[INFO] [stderr]    Compiling solders-macros v0.14.4
[INFO] [stderr]     Checking borsh v0.10.4
[INFO] [stderr]     Checking borsh v0.9.3
[INFO] [stderr]     Checking serde_with v2.3.3
[INFO] [stderr]     Checking near-account-id v0.15.0
[INFO] [stderr]    Compiling pyo3-macros v0.18.3
[INFO] [stderr]     Checking near-vm-errors v0.15.0
[INFO] [stderr]     Checking near-primitives-core v0.15.0
[INFO] [stderr]     Checking secp256k1 v0.24.3
[INFO] [stderr]     Checking near-crypto v0.15.0
[INFO] [stderr]     Checking near-primitives v0.15.0
[INFO] [stderr]     Checking ark-poly v0.4.2
[INFO] [stderr]     Checking ark-ec v0.4.2
[INFO] [stderr]     Checking ark-bn254 v0.4.0
[INFO] [stderr]     Checking light-poseidon v0.2.0
[INFO] [stderr]     Checking solders-traits v0.14.4
[INFO] [stderr]     Checking pyonear v0.2.0 (/opt/rustwide/workdir)
[INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of`
[INFO] [stdout]   --> src/error/exception.rs:29:1
[INFO] [stdout]    |
[INFO] [stdout] 29 | / create_exception!(
[INFO] [stdout] 30 | |     pyonear,
[INFO] [stdout] 31 | |     ParseKeyError,
[INFO] [stdout] 32 | |     PyException,
[INFO] [stdout] 33 | |     "Raised when an error is encountered parsing a cryptographic key."
[INFO] [stdout] 34 | | );
[INFO] [stdout]    | |_^
[INFO] [stdout]    |
[INFO] [stdout]    = help: expected names are: `docsrs`, `feature`, and `test` and 31 more
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]    = 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/error/exception.rs:29:1
[INFO] [stdout]    |
[INFO] [stdout] 29 | / create_exception!(
[INFO] [stdout] 30 | |     pyonear,
[INFO] [stdout] 31 | |     ParseKeyError,
[INFO] [stdout] 32 | |     PyException,
[INFO] [stdout] 33 | |     "Raised when an error is encountered parsing a cryptographic key."
[INFO] [stdout] 34 | | );
[INFO] [stdout]    | |_^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stdout]    = note: see <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/error/exception.rs:36:1
[INFO] [stdout]    |
[INFO] [stdout] 36 | / create_exception!(
[INFO] [stdout] 37 | |     pyonear,
[INFO] [stdout] 38 | |     ParseSignatureError,
[INFO] [stdout] 39 | |     PyException,
[INFO] [stdout] 40 | |     "Raised when an error is encountered parsing a cryptographic signature."
[INFO] [stdout] 41 | | );
[INFO] [stdout]    | |_^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stdout]    = note: see <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/error/exception.rs:36:1
[INFO] [stdout]    |
[INFO] [stdout] 36 | / create_exception!(
[INFO] [stdout] 37 | |     pyonear,
[INFO] [stdout] 38 | |     ParseSignatureError,
[INFO] [stdout] 39 | |     PyException,
[INFO] [stdout] 40 | |     "Raised when an error is encountered parsing a cryptographic signature."
[INFO] [stdout] 41 | | );
[INFO] [stdout]    | |_^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stdout]    = note: see <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/error/exception.rs:43:1
[INFO] [stdout]    |
[INFO] [stdout] 43 | / create_exception!(
[INFO] [stdout] 44 | |     pyonear,
[INFO] [stdout] 45 | |     TryFromSliceError,
[INFO] [stdout] 46 | |     PyException,
[INFO] [stdout] 47 | |     "Raised when conversion from a slice to an array fails."
[INFO] [stdout] 48 | | );
[INFO] [stdout]    | |_^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stdout]    = note: see <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/error/exception.rs:43:1
[INFO] [stdout]    |
[INFO] [stdout] 43 | / create_exception!(
[INFO] [stdout] 44 | |     pyonear,
[INFO] [stdout] 45 | |     TryFromSliceError,
[INFO] [stdout] 46 | |     PyException,
[INFO] [stdout] 47 | |     "Raised when conversion from a slice to an array fails."
[INFO] [stdout] 48 | | );
[INFO] [stdout]    | |_^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stdout]    = note: see <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/error/exception.rs:50:1
[INFO] [stdout]    |
[INFO] [stdout] 50 | / create_exception!(
[INFO] [stdout] 51 | |     pyonear,
[INFO] [stdout] 52 | |     Secp256K1Error,
[INFO] [stdout] 53 | |     PyException,
[INFO] [stdout] 54 | |     "Raised when an error is encountered in the secp256k1 library."
[INFO] [stdout] 55 | | );
[INFO] [stdout]    | |_^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stdout]    = note: see <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/error/exception.rs:50:1
[INFO] [stdout]    |
[INFO] [stdout] 50 | / create_exception!(
[INFO] [stdout] 51 | |     pyonear,
[INFO] [stdout] 52 | |     Secp256K1Error,
[INFO] [stdout] 53 | |     PyException,
[INFO] [stdout] 54 | |     "Raised when an error is encountered in the secp256k1 library."
[INFO] [stdout] 55 | | );
[INFO] [stdout]    | |_^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stdout]    = note: see <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/error/exception.rs:29:1
[INFO] [stdout]    |
[INFO] [stdout] 29 | / create_exception!(
[INFO] [stdout] 30 | |     pyonear,
[INFO] [stdout] 31 | |     ParseKeyError,
[INFO] [stdout] 32 | |     PyException,
[INFO] [stdout] 33 | |     "Raised when an error is encountered parsing a cryptographic key."
[INFO] [stdout] 34 | | );
[INFO] [stdout]    | |_^
[INFO] [stdout]    |
[INFO] [stdout]    = help: expected names are: `docsrs`, `feature`, and `test` and 31 more
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]    = 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/error/exception.rs:29:1
[INFO] [stdout]    |
[INFO] [stdout] 29 | / create_exception!(
[INFO] [stdout] 30 | |     pyonear,
[INFO] [stdout] 31 | |     ParseKeyError,
[INFO] [stdout] 32 | |     PyException,
[INFO] [stdout] 33 | |     "Raised when an error is encountered parsing a cryptographic key."
[INFO] [stdout] 34 | | );
[INFO] [stdout]    | |_^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stdout]    = note: see <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/error/exception.rs:36:1
[INFO] [stdout]    |
[INFO] [stdout] 36 | / create_exception!(
[INFO] [stdout] 37 | |     pyonear,
[INFO] [stdout] 38 | |     ParseSignatureError,
[INFO] [stdout] 39 | |     PyException,
[INFO] [stdout] 40 | |     "Raised when an error is encountered parsing a cryptographic signature."
[INFO] [stdout] 41 | | );
[INFO] [stdout]    | |_^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stdout]    = note: see <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/error/exception.rs:36:1
[INFO] [stdout]    |
[INFO] [stdout] 36 | / create_exception!(
[INFO] [stdout] 37 | |     pyonear,
[INFO] [stdout] 38 | |     ParseSignatureError,
[INFO] [stdout] 39 | |     PyException,
[INFO] [stdout] 40 | |     "Raised when an error is encountered parsing a cryptographic signature."
[INFO] [stdout] 41 | | );
[INFO] [stdout]    | |_^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stdout]    = note: see <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/error/exception.rs:43:1
[INFO] [stdout]    |
[INFO] [stdout] 43 | / create_exception!(
[INFO] [stdout] 44 | |     pyonear,
[INFO] [stdout] 45 | |     TryFromSliceError,
[INFO] [stdout] 46 | |     PyException,
[INFO] [stdout] 47 | |     "Raised when conversion from a slice to an array fails."
[INFO] [stdout] 48 | | );
[INFO] [stdout]    | |_^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stdout]    = note: see <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/error/exception.rs:43:1
[INFO] [stdout]    |
[INFO] [stdout] 43 | / create_exception!(
[INFO] [stdout] 44 | |     pyonear,
[INFO] [stdout] 45 | |     TryFromSliceError,
[INFO] [stdout] 46 | |     PyException,
[INFO] [stdout] 47 | |     "Raised when conversion from a slice to an array fails."
[INFO] [stdout] 48 | | );
[INFO] [stdout]    | |_^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stdout]    = note: see <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/error/exception.rs:50:1
[INFO] [stdout]    |
[INFO] [stdout] 50 | / create_exception!(
[INFO] [stdout] 51 | |     pyonear,
[INFO] [stdout] 52 | |     Secp256K1Error,
[INFO] [stdout] 53 | |     PyException,
[INFO] [stdout] 54 | |     "Raised when an error is encountered in the secp256k1 library."
[INFO] [stdout] 55 | | );
[INFO] [stdout]    | |_^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stdout]    = note: see <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/error/exception.rs:50:1
[INFO] [stdout]    |
[INFO] [stdout] 50 | / create_exception!(
[INFO] [stdout] 51 | |     pyonear,
[INFO] [stdout] 52 | |     Secp256K1Error,
[INFO] [stdout] 53 | |     PyException,
[INFO] [stdout] 54 | |     "Raised when an error is encountered in the secp256k1 library."
[INFO] [stdout] 55 | | );
[INFO] [stdout]    | |_^
[INFO] [stdout]    |
[INFO] [stdout]    = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3`
[INFO] [stdout]    = note: see <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: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]     --> src/error/core.rs:1058:45
[INFO] [stdout]      |
[INFO] [stdout] 1058 | fn get_invalid_access_key_error_members(py: Python) -> Vec<&PyType> {
[INFO] [stdout]      |                                             ^^^^^^         ^^^^^^^ the same lifetime is elided here
[INFO] [stdout]      |                                             |
[INFO] [stdout]      |                                             the 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)]` on by default
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]      |
[INFO] [stdout] 1058 | fn get_invalid_access_key_error_members(py: Python<'_>) -> Vec<&PyType> {
[INFO] [stdout]      |                                                   ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]     --> src/error/core.rs:1069:45
[INFO] [stdout]      |
[INFO] [stdout] 1069 | fn get_actions_validation_error_members(py: Python) -> Vec<&PyType> {
[INFO] [stdout]      |                                             ^^^^^^         ^^^^^^^ the same lifetime is elided here
[INFO] [stdout]      |                                             |
[INFO] [stdout]      |                                             the 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] 1069 | fn get_actions_validation_error_members(py: Python<'_>) -> Vec<&PyType> {
[INFO] [stdout]      |                                                   ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]     --> src/error/core.rs:1085:37
[INFO] [stdout]      |
[INFO] [stdout] 1085 | fn get_invalid_tx_error_members(py: Python) -> Vec<&PyType> {
[INFO] [stdout]      |                                     ^^^^^^         ^^^^^^^ the same lifetime is elided here
[INFO] [stdout]      |                                     |
[INFO] [stdout]      |                                     the 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] 1085 | fn get_invalid_tx_error_members(py: Python<'_>) -> Vec<&PyType> {
[INFO] [stdout]      |                                           ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]     --> src/error/core.rs:1103:50
[INFO] [stdout]      |
[INFO] [stdout] 1103 | pub(crate) fn get_tx_execution_error_members(py: Python) -> Vec<&PyType> {
[INFO] [stdout]      |                                                  ^^^^^^         ^^^^^^^ the same lifetime is elided here
[INFO] [stdout]      |                                                  |
[INFO] [stdout]      |                                                  the 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] 1103 | pub(crate) fn get_tx_execution_error_members(py: Python<'_>) -> Vec<&PyType> {
[INFO] [stdout]      |                                                        ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/error/vm.rs:595:55
[INFO] [stdout]     |
[INFO] [stdout] 595 | pub(crate) fn get_function_call_error_ser_members(py: Python) -> Vec<&PyType> {
[INFO] [stdout]     |                                                       ^^^^^^         ^^^^^^^ the same lifetime is elided here
[INFO] [stdout]     |                                                       |
[INFO] [stdout]     |                                                       the 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] 595 | pub(crate) fn get_function_call_error_ser_members(py: Python<'_>) -> Vec<&PyType> {
[INFO] [stdout]     |                                                             ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]     --> src/error/core.rs:1058:45
[INFO] [stdout]      |
[INFO] [stdout] 1058 | fn get_invalid_access_key_error_members(py: Python) -> Vec<&PyType> {
[INFO] [stdout]      |                                             ^^^^^^         ^^^^^^^ the same lifetime is elided here
[INFO] [stdout]      |                                             |
[INFO] [stdout]      |                                             the 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)]` on by default
[INFO] [stdout] help: use `'_` for type paths
[INFO] [stdout]      |
[INFO] [stdout] 1058 | fn get_invalid_access_key_error_members(py: Python<'_>) -> Vec<&PyType> {
[INFO] [stdout]      |                                                   ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]     --> src/error/core.rs:1069:45
[INFO] [stdout]      |
[INFO] [stdout] 1069 | fn get_actions_validation_error_members(py: Python) -> Vec<&PyType> {
[INFO] [stdout]      |                                             ^^^^^^         ^^^^^^^ the same lifetime is elided here
[INFO] [stdout]      |                                             |
[INFO] [stdout]      |                                             the 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] 1069 | fn get_actions_validation_error_members(py: Python<'_>) -> Vec<&PyType> {
[INFO] [stdout]      |                                                   ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]     --> src/error/core.rs:1085:37
[INFO] [stdout]      |
[INFO] [stdout] 1085 | fn get_invalid_tx_error_members(py: Python) -> Vec<&PyType> {
[INFO] [stdout]      |                                     ^^^^^^         ^^^^^^^ the same lifetime is elided here
[INFO] [stdout]      |                                     |
[INFO] [stdout]      |                                     the 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] 1085 | fn get_invalid_tx_error_members(py: Python<'_>) -> Vec<&PyType> {
[INFO] [stdout]      |                                           ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]     --> src/error/core.rs:1103:50
[INFO] [stdout]      |
[INFO] [stdout] 1103 | pub(crate) fn get_tx_execution_error_members(py: Python) -> Vec<&PyType> {
[INFO] [stdout]      |                                                  ^^^^^^         ^^^^^^^ the same lifetime is elided here
[INFO] [stdout]      |                                                  |
[INFO] [stdout]      |                                                  the 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] 1103 | pub(crate) fn get_tx_execution_error_members(py: Python<'_>) -> Vec<&PyType> {
[INFO] [stdout]      |                                                        ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing
[INFO] [stdout]    --> src/error/vm.rs:595:55
[INFO] [stdout]     |
[INFO] [stdout] 595 | pub(crate) fn get_function_call_error_ser_members(py: Python) -> Vec<&PyType> {
[INFO] [stdout]     |                                                       ^^^^^^         ^^^^^^^ the same lifetime is elided here
[INFO] [stdout]     |                                                       |
[INFO] [stdout]     |                                                       the 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] 595 | pub(crate) fn get_function_call_error_ser_members(py: Python<'_>) -> Vec<&PyType> {
[INFO] [stdout]     |                                                             ++++
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished `dev` profile [unoptimized + debuginfo] target(s) in 33.16s
[INFO] running `Command { std: "docker" "inspect" "caae24db23b5e523a58a61d12f7f3b0fdf03681b4e9fcf5dffafba3543b545f4", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "caae24db23b5e523a58a61d12f7f3b0fdf03681b4e9fcf5dffafba3543b545f4", kill_on_drop: false }`
[INFO] [stdout] caae24db23b5e523a58a61d12f7f3b0fdf03681b4e9fcf5dffafba3543b545f4
