[INFO] fetching crate akinator-py 0.2.1... [INFO] checking akinator-py-0.2.1 against master#8c32e313cccf7df531e2d49ffb8227bb92304aee for pr-145608-1 [INFO] extracting crate akinator-py 0.2.1 into /workspace/builds/worker-7-tc1/source [INFO] started tweaking crates.io crate akinator-py 0.2.1 [INFO] finished tweaking crates.io crate akinator-py 0.2.1 [INFO] tweaked toml for crates.io crate akinator-py 0.2.1 written to /workspace/builds/worker-7-tc1/source/Cargo.toml [INFO] validating manifest of crates.io crate akinator-py 0.2.1 on toolchain 8c32e313cccf7df531e2d49ffb8227bb92304aee [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+8c32e313cccf7df531e2d49ffb8227bb92304aee" "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" "+8c32e313cccf7df531e2d49ffb8227bb92304aee" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Updating crates.io index [INFO] [stderr] Locking 167 packages to latest compatible versions [INFO] [stderr] Adding pyo3 v0.16.6 (available: v0.26.0) [INFO] [stderr] Adding pyo3-asyncio v0.16.0 (available: v0.20.0) [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+8c32e313cccf7df531e2d49ffb8227bb92304aee" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Downloading crates ... [INFO] [stderr] Downloaded akinator-rs v0.1.13 [INFO] [stderr] Downloaded pyo3-macros-backend v0.16.6 [INFO] [stderr] Downloaded pyo3-asyncio v0.16.0 [INFO] [stderr] Downloaded pyo3-build-config v0.16.6 [INFO] [stderr] Downloaded pyo3-ffi v0.16.6 [INFO] [stderr] Downloaded pyo3-macros v0.16.6 [INFO] [stderr] Downloaded pyo3 v0.16.6 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:7ad1b28ee6f5f7f699f6cf7015098d6ccdd96d6f2d78dd06228f5b4c9faf309c" "/opt/rustwide/cargo-home/bin/cargo" "+8c32e313cccf7df531e2d49ffb8227bb92304aee" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 5802020182d0b41c8ccc2f5481af88fd80d7498f8dd8a72f7645a230d7898894 [INFO] running `Command { std: "docker" "start" "-a" "5802020182d0b41c8ccc2f5481af88fd80d7498f8dd8a72f7645a230d7898894", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "5802020182d0b41c8ccc2f5481af88fd80d7498f8dd8a72f7645a230d7898894", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "5802020182d0b41c8ccc2f5481af88fd80d7498f8dd8a72f7645a230d7898894", kill_on_drop: false }` [INFO] [stdout] 5802020182d0b41c8ccc2f5481af88fd80d7498f8dd8a72f7645a230d7898894 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:7ad1b28ee6f5f7f699f6cf7015098d6ccdd96d6f2d78dd06228f5b4c9faf309c" "/opt/rustwide/cargo-home/bin/cargo" "+8c32e313cccf7df531e2d49ffb8227bb92304aee" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] b76acb22062081518931c400f165f2fdb98341692a0ef9c8f4902cd5dbffbcef [INFO] running `Command { std: "docker" "start" "-a" "b76acb22062081518931c400f165f2fdb98341692a0ef9c8f4902cd5dbffbcef", kill_on_drop: false }` [INFO] [stderr] Compiling target-lexicon v0.12.16 [INFO] [stderr] Compiling find-msvc-tools v0.1.0 [INFO] [stderr] Checking parking_lot_core v0.9.11 [INFO] [stderr] Compiling tokio-macros v2.5.0 [INFO] [stderr] Compiling futures-macro v0.3.31 [INFO] [stderr] Checking signal-hook-registry v1.4.6 [INFO] [stderr] Checking potential_utf v0.1.3 [INFO] [stderr] Checking getrandom v0.2.16 [INFO] [stderr] Compiling once_cell v1.21.3 [INFO] [stderr] Compiling cc v1.2.35 [INFO] [stderr] Checking parking_lot v0.12.4 [INFO] [stderr] Checking icu_collections v2.0.0 [INFO] [stderr] Compiling rustls v0.21.12 [INFO] [stderr] Compiling syn v1.0.109 [INFO] [stderr] Checking http-body v0.4.6 [INFO] [stderr] Checking socket2 v0.5.10 [INFO] [stderr] Compiling pyo3-build-config v0.16.6 [INFO] [stderr] Checking unindent v0.1.11 [INFO] [stderr] Checking webpki-roots v0.25.4 [INFO] [stderr] Checking icu_properties v2.0.1 [INFO] [stderr] Checking icu_normalizer v2.0.0 [INFO] [stderr] Checking tokio v1.47.1 [INFO] [stderr] Compiling indoc v1.0.9 [INFO] [stderr] Checking futures-util v0.3.31 [INFO] [stderr] Compiling ring v0.17.14 [INFO] [stderr] Checking idna_adapter v1.2.1 [INFO] [stderr] Checking idna v1.1.0 [INFO] [stderr] Compiling pyo3-ffi v0.16.6 [INFO] [stderr] Compiling pyo3 v0.16.6 [INFO] [stderr] Checking url v2.5.7 [INFO] [stderr] Compiling pyo3-macros-backend v0.16.6 [INFO] [stderr] Checking futures-executor v0.3.31 [INFO] [stderr] Checking futures v0.3.31 [INFO] [stderr] Checking tokio-util v0.7.16 [INFO] [stderr] Checking h2 v0.3.27 [INFO] [stderr] Checking rustls-webpki v0.101.7 [INFO] [stderr] Checking sct v0.7.1 [INFO] [stderr] Compiling pyo3-macros v0.16.6 [INFO] [stderr] Checking tokio-rustls v0.24.1 [INFO] [stderr] Checking hyper v0.14.32 [INFO] [stderr] Checking pyo3-asyncio v0.16.0 [INFO] [stderr] Checking hyper-rustls v0.24.2 [INFO] [stderr] Checking reqwest v0.11.27 [INFO] [stderr] Checking akinator-rs v0.1.13 [INFO] [stderr] Checking akinator-py v0.2.1 (/opt/rustwide/workdir) [INFO] [stdout] warning: unexpected `cfg` condition name: `addr_of` [INFO] [stdout] --> src/error.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | / create_exceptions![ [INFO] [stdout] 29 | | (CantGoBackAnyFurther, "Raised when the akinator is already on the 1st question / there are no more questions to go back on"), [INFO] [stdout] 30 | | (InvalidAnswer, "Raised when an invalid answer string is used when instantiating a Language enum from str"), [INFO] [stdout] 31 | | (InvalidLanguage, "Raised when an invalid language string is used when instantiating a Language enum from str"), [INFO] [stdout] ... | [INFO] [stdout] 36 | | (ServersDown, "Raised when the akinator servers in the requested region are down"), [INFO] [stdout] 37 | | ]; [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[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_exceptions` (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.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | / create_exceptions![ [INFO] [stdout] 29 | | (CantGoBackAnyFurther, "Raised when the akinator is already on the 1st question / there are no more questions to go back on"), [INFO] [stdout] 30 | | (InvalidAnswer, "Raised when an invalid answer string is used when instantiating a Language enum from str"), [INFO] [stdout] 31 | | (InvalidLanguage, "Raised when an invalid language string is used when instantiating a Language enum from str"), [INFO] [stdout] ... | [INFO] [stdout] 36 | | (ServersDown, "Raised when the akinator servers in the requested region are down"), [INFO] [stdout] 37 | | ]; [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exceptions` (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.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | / create_exceptions![ [INFO] [stdout] 29 | | (CantGoBackAnyFurther, "Raised when the akinator is already on the 1st question / there are no more questions to go back on"), [INFO] [stdout] 30 | | (InvalidAnswer, "Raised when an invalid answer string is used when instantiating a Language enum from str"), [INFO] [stdout] 31 | | (InvalidLanguage, "Raised when an invalid language string is used when instantiating a Language enum from str"), [INFO] [stdout] ... | [INFO] [stdout] 36 | | (ServersDown, "Raised when the akinator servers in the requested region are down"), [INFO] [stdout] 37 | | ]; [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exceptions` (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.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | / create_exceptions![ [INFO] [stdout] 29 | | (CantGoBackAnyFurther, "Raised when the akinator is already on the 1st question / there are no more questions to go back on"), [INFO] [stdout] 30 | | (InvalidAnswer, "Raised when an invalid answer string is used when instantiating a Language enum from str"), [INFO] [stdout] 31 | | (InvalidLanguage, "Raised when an invalid language string is used when instantiating a Language enum from str"), [INFO] [stdout] ... | [INFO] [stdout] 36 | | (ServersDown, "Raised when the akinator servers in the requested region are down"), [INFO] [stdout] 37 | | ]; [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exceptions` (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.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | / create_exceptions![ [INFO] [stdout] 29 | | (CantGoBackAnyFurther, "Raised when the akinator is already on the 1st question / there are no more questions to go back on"), [INFO] [stdout] 30 | | (InvalidAnswer, "Raised when an invalid answer string is used when instantiating a Language enum from str"), [INFO] [stdout] 31 | | (InvalidLanguage, "Raised when an invalid language string is used when instantiating a Language enum from str"), [INFO] [stdout] ... | [INFO] [stdout] 36 | | (ServersDown, "Raised when the akinator servers in the requested region are down"), [INFO] [stdout] 37 | | ]; [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exceptions` (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.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | / create_exceptions![ [INFO] [stdout] 29 | | (CantGoBackAnyFurther, "Raised when the akinator is already on the 1st question / there are no more questions to go back on"), [INFO] [stdout] 30 | | (InvalidAnswer, "Raised when an invalid answer string is used when instantiating a Language enum from str"), [INFO] [stdout] 31 | | (InvalidLanguage, "Raised when an invalid language string is used when instantiating a Language enum from str"), [INFO] [stdout] ... | [INFO] [stdout] 36 | | (ServersDown, "Raised when the akinator servers in the requested region are down"), [INFO] [stdout] 37 | | ]; [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exceptions` (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.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | / create_exceptions![ [INFO] [stdout] 29 | | (CantGoBackAnyFurther, "Raised when the akinator is already on the 1st question / there are no more questions to go back on"), [INFO] [stdout] 30 | | (InvalidAnswer, "Raised when an invalid answer string is used when instantiating a Language enum from str"), [INFO] [stdout] 31 | | (InvalidLanguage, "Raised when an invalid language string is used when instantiating a Language enum from str"), [INFO] [stdout] ... | [INFO] [stdout] 36 | | (ServersDown, "Raised when the akinator servers in the requested region are down"), [INFO] [stdout] 37 | | ]; [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exceptions` (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.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | / create_exceptions![ [INFO] [stdout] 29 | | (CantGoBackAnyFurther, "Raised when the akinator is already on the 1st question / there are no more questions to go back on"), [INFO] [stdout] 30 | | (InvalidAnswer, "Raised when an invalid answer string is used when instantiating a Language enum from str"), [INFO] [stdout] 31 | | (InvalidLanguage, "Raised when an invalid language string is used when instantiating a Language enum from str"), [INFO] [stdout] ... | [INFO] [stdout] 36 | | (ServersDown, "Raised when the akinator servers in the requested region are down"), [INFO] [stdout] 37 | | ]; [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exceptions` (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.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | / create_exceptions![ [INFO] [stdout] 29 | | (CantGoBackAnyFurther, "Raised when the akinator is already on the 1st question / there are no more questions to go back on"), [INFO] [stdout] 30 | | (InvalidAnswer, "Raised when an invalid answer string is used when instantiating a Language enum from str"), [INFO] [stdout] 31 | | (InvalidLanguage, "Raised when an invalid language string is used when instantiating a Language enum from str"), [INFO] [stdout] ... | [INFO] [stdout] 36 | | (ServersDown, "Raised when the akinator servers in the requested region are down"), [INFO] [stdout] 37 | | ]; [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exceptions` (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.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | / create_exceptions![ [INFO] [stdout] 29 | | (CantGoBackAnyFurther, "Raised when the akinator is already on the 1st question / there are no more questions to go back on"), [INFO] [stdout] 30 | | (InvalidAnswer, "Raised when an invalid answer string is used when instantiating a Language enum from str"), [INFO] [stdout] 31 | | (InvalidLanguage, "Raised when an invalid language string is used when instantiating a Language enum from str"), [INFO] [stdout] ... | [INFO] [stdout] 36 | | (ServersDown, "Raised when the akinator servers in the requested region are down"), [INFO] [stdout] 37 | | ]; [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exceptions` (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.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | / create_exceptions![ [INFO] [stdout] 29 | | (CantGoBackAnyFurther, "Raised when the akinator is already on the 1st question / there are no more questions to go back on"), [INFO] [stdout] 30 | | (InvalidAnswer, "Raised when an invalid answer string is used when instantiating a Language enum from str"), [INFO] [stdout] 31 | | (InvalidLanguage, "Raised when an invalid language string is used when instantiating a Language enum from str"), [INFO] [stdout] ... | [INFO] [stdout] 36 | | (ServersDown, "Raised when the akinator servers in the requested region are down"), [INFO] [stdout] 37 | | ]; [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exceptions` (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.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | / create_exceptions![ [INFO] [stdout] 29 | | (CantGoBackAnyFurther, "Raised when the akinator is already on the 1st question / there are no more questions to go back on"), [INFO] [stdout] 30 | | (InvalidAnswer, "Raised when an invalid answer string is used when instantiating a Language enum from str"), [INFO] [stdout] 31 | | (InvalidLanguage, "Raised when an invalid language string is used when instantiating a Language enum from str"), [INFO] [stdout] ... | [INFO] [stdout] 36 | | (ServersDown, "Raised when the akinator servers in the requested region are down"), [INFO] [stdout] 37 | | ]; [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exceptions` (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.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | / create_exceptions![ [INFO] [stdout] 29 | | (CantGoBackAnyFurther, "Raised when the akinator is already on the 1st question / there are no more questions to go back on"), [INFO] [stdout] 30 | | (InvalidAnswer, "Raised when an invalid answer string is used when instantiating a Language enum from str"), [INFO] [stdout] 31 | | (InvalidLanguage, "Raised when an invalid language string is used when instantiating a Language enum from str"), [INFO] [stdout] ... | [INFO] [stdout] 36 | | (ServersDown, "Raised when the akinator servers in the requested region are down"), [INFO] [stdout] 37 | | ]; [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exceptions` (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.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | / create_exceptions![ [INFO] [stdout] 29 | | (CantGoBackAnyFurther, "Raised when the akinator is already on the 1st question / there are no more questions to go back on"), [INFO] [stdout] 30 | | (InvalidAnswer, "Raised when an invalid answer string is used when instantiating a Language enum from str"), [INFO] [stdout] 31 | | (InvalidLanguage, "Raised when an invalid language string is used when instantiating a Language enum from str"), [INFO] [stdout] ... | [INFO] [stdout] 36 | | (ServersDown, "Raised when the akinator servers in the requested region are down"), [INFO] [stdout] 37 | | ]; [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exceptions` (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.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | / create_exceptions![ [INFO] [stdout] 29 | | (CantGoBackAnyFurther, "Raised when the akinator is already on the 1st question / there are no more questions to go back on"), [INFO] [stdout] 30 | | (InvalidAnswer, "Raised when an invalid answer string is used when instantiating a Language enum from str"), [INFO] [stdout] 31 | | (InvalidLanguage, "Raised when an invalid language string is used when instantiating a Language enum from str"), [INFO] [stdout] ... | [INFO] [stdout] 36 | | (ServersDown, "Raised when the akinator servers in the requested region are down"), [INFO] [stdout] 37 | | ]; [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exceptions` (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.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | / create_exceptions![ [INFO] [stdout] 29 | | (CantGoBackAnyFurther, "Raised when the akinator is already on the 1st question / there are no more questions to go back on"), [INFO] [stdout] 30 | | (InvalidAnswer, "Raised when an invalid answer string is used when instantiating a Language enum from str"), [INFO] [stdout] 31 | | (InvalidLanguage, "Raised when an invalid language string is used when instantiating a Language enum from str"), [INFO] [stdout] ... | [INFO] [stdout] 36 | | (ServersDown, "Raised when the akinator servers in the requested region are down"), [INFO] [stdout] 37 | | ]; [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exceptions` (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.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | / create_exceptions![ [INFO] [stdout] 29 | | (CantGoBackAnyFurther, "Raised when the akinator is already on the 1st question / there are no more questions to go back on"), [INFO] [stdout] 30 | | (InvalidAnswer, "Raised when an invalid answer string is used when instantiating a Language enum from str"), [INFO] [stdout] 31 | | (InvalidLanguage, "Raised when an invalid language string is used when instantiating a Language enum from str"), [INFO] [stdout] ... | [INFO] [stdout] 36 | | (ServersDown, "Raised when the akinator servers in the requested region are down"), [INFO] [stdout] 37 | | ]; [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = help: expected names are: `docsrs`, `feature`, and `test` and 31 more [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[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_exceptions` (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.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | / create_exceptions![ [INFO] [stdout] 29 | | (CantGoBackAnyFurther, "Raised when the akinator is already on the 1st question / there are no more questions to go back on"), [INFO] [stdout] 30 | | (InvalidAnswer, "Raised when an invalid answer string is used when instantiating a Language enum from str"), [INFO] [stdout] 31 | | (InvalidLanguage, "Raised when an invalid language string is used when instantiating a Language enum from str"), [INFO] [stdout] ... | [INFO] [stdout] 36 | | (ServersDown, "Raised when the akinator servers in the requested region are down"), [INFO] [stdout] 37 | | ]; [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exceptions` (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.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | / create_exceptions![ [INFO] [stdout] 29 | | (CantGoBackAnyFurther, "Raised when the akinator is already on the 1st question / there are no more questions to go back on"), [INFO] [stdout] 30 | | (InvalidAnswer, "Raised when an invalid answer string is used when instantiating a Language enum from str"), [INFO] [stdout] 31 | | (InvalidLanguage, "Raised when an invalid language string is used when instantiating a Language enum from str"), [INFO] [stdout] ... | [INFO] [stdout] 36 | | (ServersDown, "Raised when the akinator servers in the requested region are down"), [INFO] [stdout] 37 | | ]; [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exceptions` (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.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | / create_exceptions![ [INFO] [stdout] 29 | | (CantGoBackAnyFurther, "Raised when the akinator is already on the 1st question / there are no more questions to go back on"), [INFO] [stdout] 30 | | (InvalidAnswer, "Raised when an invalid answer string is used when instantiating a Language enum from str"), [INFO] [stdout] 31 | | (InvalidLanguage, "Raised when an invalid language string is used when instantiating a Language enum from str"), [INFO] [stdout] ... | [INFO] [stdout] 36 | | (ServersDown, "Raised when the akinator servers in the requested region are down"), [INFO] [stdout] 37 | | ]; [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exceptions` (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.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | / create_exceptions![ [INFO] [stdout] 29 | | (CantGoBackAnyFurther, "Raised when the akinator is already on the 1st question / there are no more questions to go back on"), [INFO] [stdout] 30 | | (InvalidAnswer, "Raised when an invalid answer string is used when instantiating a Language enum from str"), [INFO] [stdout] 31 | | (InvalidLanguage, "Raised when an invalid language string is used when instantiating a Language enum from str"), [INFO] [stdout] ... | [INFO] [stdout] 36 | | (ServersDown, "Raised when the akinator servers in the requested region are down"), [INFO] [stdout] 37 | | ]; [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exceptions` (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.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | / create_exceptions![ [INFO] [stdout] 29 | | (CantGoBackAnyFurther, "Raised when the akinator is already on the 1st question / there are no more questions to go back on"), [INFO] [stdout] 30 | | (InvalidAnswer, "Raised when an invalid answer string is used when instantiating a Language enum from str"), [INFO] [stdout] 31 | | (InvalidLanguage, "Raised when an invalid language string is used when instantiating a Language enum from str"), [INFO] [stdout] ... | [INFO] [stdout] 36 | | (ServersDown, "Raised when the akinator servers in the requested region are down"), [INFO] [stdout] 37 | | ]; [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exceptions` (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.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | / create_exceptions![ [INFO] [stdout] 29 | | (CantGoBackAnyFurther, "Raised when the akinator is already on the 1st question / there are no more questions to go back on"), [INFO] [stdout] 30 | | (InvalidAnswer, "Raised when an invalid answer string is used when instantiating a Language enum from str"), [INFO] [stdout] 31 | | (InvalidLanguage, "Raised when an invalid language string is used when instantiating a Language enum from str"), [INFO] [stdout] ... | [INFO] [stdout] 36 | | (ServersDown, "Raised when the akinator servers in the requested region are down"), [INFO] [stdout] 37 | | ]; [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exceptions` (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.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | / create_exceptions![ [INFO] [stdout] 29 | | (CantGoBackAnyFurther, "Raised when the akinator is already on the 1st question / there are no more questions to go back on"), [INFO] [stdout] 30 | | (InvalidAnswer, "Raised when an invalid answer string is used when instantiating a Language enum from str"), [INFO] [stdout] 31 | | (InvalidLanguage, "Raised when an invalid language string is used when instantiating a Language enum from str"), [INFO] [stdout] ... | [INFO] [stdout] 36 | | (ServersDown, "Raised when the akinator servers in the requested region are down"), [INFO] [stdout] 37 | | ]; [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exceptions` (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.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | / create_exceptions![ [INFO] [stdout] 29 | | (CantGoBackAnyFurther, "Raised when the akinator is already on the 1st question / there are no more questions to go back on"), [INFO] [stdout] 30 | | (InvalidAnswer, "Raised when an invalid answer string is used when instantiating a Language enum from str"), [INFO] [stdout] 31 | | (InvalidLanguage, "Raised when an invalid language string is used when instantiating a Language enum from str"), [INFO] [stdout] ... | [INFO] [stdout] 36 | | (ServersDown, "Raised when the akinator servers in the requested region are down"), [INFO] [stdout] 37 | | ]; [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exceptions` (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.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | / create_exceptions![ [INFO] [stdout] 29 | | (CantGoBackAnyFurther, "Raised when the akinator is already on the 1st question / there are no more questions to go back on"), [INFO] [stdout] 30 | | (InvalidAnswer, "Raised when an invalid answer string is used when instantiating a Language enum from str"), [INFO] [stdout] 31 | | (InvalidLanguage, "Raised when an invalid language string is used when instantiating a Language enum from str"), [INFO] [stdout] ... | [INFO] [stdout] 36 | | (ServersDown, "Raised when the akinator servers in the requested region are down"), [INFO] [stdout] 37 | | ]; [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exceptions` (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.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | / create_exceptions![ [INFO] [stdout] 29 | | (CantGoBackAnyFurther, "Raised when the akinator is already on the 1st question / there are no more questions to go back on"), [INFO] [stdout] 30 | | (InvalidAnswer, "Raised when an invalid answer string is used when instantiating a Language enum from str"), [INFO] [stdout] 31 | | (InvalidLanguage, "Raised when an invalid language string is used when instantiating a Language enum from str"), [INFO] [stdout] ... | [INFO] [stdout] 36 | | (ServersDown, "Raised when the akinator servers in the requested region are down"), [INFO] [stdout] 37 | | ]; [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exceptions` (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.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | / create_exceptions![ [INFO] [stdout] 29 | | (CantGoBackAnyFurther, "Raised when the akinator is already on the 1st question / there are no more questions to go back on"), [INFO] [stdout] 30 | | (InvalidAnswer, "Raised when an invalid answer string is used when instantiating a Language enum from str"), [INFO] [stdout] 31 | | (InvalidLanguage, "Raised when an invalid language string is used when instantiating a Language enum from str"), [INFO] [stdout] ... | [INFO] [stdout] 36 | | (ServersDown, "Raised when the akinator servers in the requested region are down"), [INFO] [stdout] 37 | | ]; [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exceptions` (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.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | / create_exceptions![ [INFO] [stdout] 29 | | (CantGoBackAnyFurther, "Raised when the akinator is already on the 1st question / there are no more questions to go back on"), [INFO] [stdout] 30 | | (InvalidAnswer, "Raised when an invalid answer string is used when instantiating a Language enum from str"), [INFO] [stdout] 31 | | (InvalidLanguage, "Raised when an invalid language string is used when instantiating a Language enum from str"), [INFO] [stdout] ... | [INFO] [stdout] 36 | | (ServersDown, "Raised when the akinator servers in the requested region are down"), [INFO] [stdout] 37 | | ]; [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exceptions` (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.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | / create_exceptions![ [INFO] [stdout] 29 | | (CantGoBackAnyFurther, "Raised when the akinator is already on the 1st question / there are no more questions to go back on"), [INFO] [stdout] 30 | | (InvalidAnswer, "Raised when an invalid answer string is used when instantiating a Language enum from str"), [INFO] [stdout] 31 | | (InvalidLanguage, "Raised when an invalid language string is used when instantiating a Language enum from str"), [INFO] [stdout] ... | [INFO] [stdout] 36 | | (ServersDown, "Raised when the akinator servers in the requested region are down"), [INFO] [stdout] 37 | | ]; [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exceptions` (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.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | / create_exceptions![ [INFO] [stdout] 29 | | (CantGoBackAnyFurther, "Raised when the akinator is already on the 1st question / there are no more questions to go back on"), [INFO] [stdout] 30 | | (InvalidAnswer, "Raised when an invalid answer string is used when instantiating a Language enum from str"), [INFO] [stdout] 31 | | (InvalidLanguage, "Raised when an invalid language string is used when instantiating a Language enum from str"), [INFO] [stdout] ... | [INFO] [stdout] 36 | | (ServersDown, "Raised when the akinator servers in the requested region are down"), [INFO] [stdout] 37 | | ]; [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exceptions` (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.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | / create_exceptions![ [INFO] [stdout] 29 | | (CantGoBackAnyFurther, "Raised when the akinator is already on the 1st question / there are no more questions to go back on"), [INFO] [stdout] 30 | | (InvalidAnswer, "Raised when an invalid answer string is used when instantiating a Language enum from str"), [INFO] [stdout] 31 | | (InvalidLanguage, "Raised when an invalid language string is used when instantiating a Language enum from str"), [INFO] [stdout] ... | [INFO] [stdout] 36 | | (ServersDown, "Raised when the akinator servers in the requested region are down"), [INFO] [stdout] 37 | | ]; [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::pyobject_native_type_info` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_info` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::pyobject_native_type_info` which comes from the expansion of the macro `create_exceptions` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0599]: no method named `with_theme` found for enum `Result` in the current scope [INFO] [stdout] --> src/blocking_akinator.rs:54:33 [INFO] [stdout] | [INFO] [stdout] 54 | akinator = akinator.with_theme(theme.into()); [INFO] [stdout] | ^^^^^^^^^^ method not found in `Result` [INFO] [stdout] | [INFO] [stdout] note: the method `with_theme` exists on the type `akinator_rs::Akinator` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/akinator-rs-0.1.13/src/lib.rs:145:5 [INFO] [stdout] | [INFO] [stdout] 145 | pub const fn with_theme(mut self, theme: Theme) -> Self { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] help: consider using `Result::expect` to unwrap the `akinator_rs::Akinator` value, panicking if the value is a `Result::Err` [INFO] [stdout] | [INFO] [stdout] 54 | akinator = akinator.expect("REASON").with_theme(theme.into()); [INFO] [stdout] | +++++++++++++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0599]: no method named `with_language` found for enum `Result` in the current scope [INFO] [stdout] --> src/blocking_akinator.rs:58:33 [INFO] [stdout] | [INFO] [stdout] 58 | akinator = akinator.with_language(language.into()); [INFO] [stdout] | ^^^^^^^^^^^^^ method not found in `Result` [INFO] [stdout] | [INFO] [stdout] note: the method `with_language` exists on the type `akinator_rs::Akinator` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/akinator-rs-0.1.13/src/lib.rs:152:5 [INFO] [stdout] | [INFO] [stdout] 152 | pub const fn with_language(mut self, language: Language) -> Self { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] help: consider using `Result::expect` to unwrap the `akinator_rs::Akinator` value, panicking if the value is a `Result::Err` [INFO] [stdout] | [INFO] [stdout] 58 | akinator = akinator.expect("REASON").with_language(language.into()); [INFO] [stdout] | +++++++++++++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0599]: no method named `with_child_mode` found for enum `Result` in the current scope [INFO] [stdout] --> src/blocking_akinator.rs:62:33 [INFO] [stdout] | [INFO] [stdout] 62 | akinator = akinator.with_child_mode(); [INFO] [stdout] | ^^^^^^^^^^^^^^^ method not found in `Result` [INFO] [stdout] | [INFO] [stdout] note: the method `with_child_mode` exists on the type `akinator_rs::Akinator` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/akinator-rs-0.1.13/src/lib.rs:159:5 [INFO] [stdout] | [INFO] [stdout] 159 | pub const fn with_child_mode(mut self) -> Self { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] help: consider using `Result::expect` to unwrap the `akinator_rs::Akinator` value, panicking if the value is a `Result::Err` [INFO] [stdout] | [INFO] [stdout] 62 | akinator = akinator.expect("REASON").with_child_mode(); [INFO] [stdout] | +++++++++++++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0308]: mismatched types [INFO] [stdout] --> src/blocking_akinator.rs:65:14 [INFO] [stdout] | [INFO] [stdout] 65 | Self(akinator) [INFO] [stdout] | ---- ^^^^^^^^ expected `Akinator`, found `Result` [INFO] [stdout] | | [INFO] [stdout] | arguments to this function are incorrect [INFO] [stdout] | [INFO] [stdout] = note: expected struct `akinator_rs::Akinator` [INFO] [stdout] found enum `Result` [INFO] [stdout] note: tuple struct defined here [INFO] [stdout] --> src/blocking_akinator.rs:37:12 [INFO] [stdout] | [INFO] [stdout] 37 | pub struct Akinator( [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] help: consider using `Result::expect` to unwrap the `Result` value, panicking if the value is a `Result::Err` [INFO] [stdout] | [INFO] [stdout] 65 | Self(akinator.expect("REASON")) [INFO] [stdout] | +++++++++++++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0599]: no method named `with_theme` found for enum `Result` in the current scope [INFO] [stdout] --> src/blocking_akinator.rs:54:33 [INFO] [stdout] | [INFO] [stdout] 54 | akinator = akinator.with_theme(theme.into()); [INFO] [stdout] | ^^^^^^^^^^ method not found in `Result` [INFO] [stdout] | [INFO] [stdout] note: the method `with_theme` exists on the type `akinator_rs::Akinator` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/akinator-rs-0.1.13/src/lib.rs:145:5 [INFO] [stdout] | [INFO] [stdout] 145 | pub const fn with_theme(mut self, theme: Theme) -> Self { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] help: consider using `Result::expect` to unwrap the `akinator_rs::Akinator` value, panicking if the value is a `Result::Err` [INFO] [stdout] | [INFO] [stdout] 54 | akinator = akinator.expect("REASON").with_theme(theme.into()); [INFO] [stdout] | +++++++++++++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0599]: no method named `with_language` found for enum `Result` in the current scope [INFO] [stdout] --> src/blocking_akinator.rs:58:33 [INFO] [stdout] | [INFO] [stdout] 58 | akinator = akinator.with_language(language.into()); [INFO] [stdout] | ^^^^^^^^^^^^^ method not found in `Result` [INFO] [stdout] | [INFO] [stdout] note: the method `with_language` exists on the type `akinator_rs::Akinator` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/akinator-rs-0.1.13/src/lib.rs:152:5 [INFO] [stdout] | [INFO] [stdout] 152 | pub const fn with_language(mut self, language: Language) -> Self { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] help: consider using `Result::expect` to unwrap the `akinator_rs::Akinator` value, panicking if the value is a `Result::Err` [INFO] [stdout] | [INFO] [stdout] 58 | akinator = akinator.expect("REASON").with_language(language.into()); [INFO] [stdout] | +++++++++++++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0599]: no method named `with_child_mode` found for enum `Result` in the current scope [INFO] [stdout] --> src/blocking_akinator.rs:62:33 [INFO] [stdout] | [INFO] [stdout] 62 | akinator = akinator.with_child_mode(); [INFO] [stdout] | ^^^^^^^^^^^^^^^ method not found in `Result` [INFO] [stdout] | [INFO] [stdout] note: the method `with_child_mode` exists on the type `akinator_rs::Akinator` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/akinator-rs-0.1.13/src/lib.rs:159:5 [INFO] [stdout] | [INFO] [stdout] 159 | pub const fn with_child_mode(mut self) -> Self { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] help: consider using `Result::expect` to unwrap the `akinator_rs::Akinator` value, panicking if the value is a `Result::Err` [INFO] [stdout] | [INFO] [stdout] 62 | akinator = akinator.expect("REASON").with_child_mode(); [INFO] [stdout] | +++++++++++++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0308]: mismatched types [INFO] [stdout] --> src/blocking_akinator.rs:65:14 [INFO] [stdout] | [INFO] [stdout] 65 | Self(akinator) [INFO] [stdout] | ---- ^^^^^^^^ expected `Akinator`, found `Result` [INFO] [stdout] | | [INFO] [stdout] | arguments to this function are incorrect [INFO] [stdout] | [INFO] [stdout] = note: expected struct `akinator_rs::Akinator` [INFO] [stdout] found enum `Result` [INFO] [stdout] note: tuple struct defined here [INFO] [stdout] --> src/blocking_akinator.rs:37:12 [INFO] [stdout] | [INFO] [stdout] 37 | pub struct Akinator( [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] help: consider using `Result::expect` to unwrap the `Result` value, panicking if the value is a `Result::Err` [INFO] [stdout] | [INFO] [stdout] 65 | Self(akinator.expect("REASON")) [INFO] [stdout] | +++++++++++++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0599]: no method named `with_theme` found for enum `Result` in the current scope [INFO] [stdout] --> src/async_akinator.rs:59:33 [INFO] [stdout] | [INFO] [stdout] 59 | akinator = akinator.with_theme(theme.into()); [INFO] [stdout] | ^^^^^^^^^^ method not found in `Result` [INFO] [stdout] | [INFO] [stdout] note: the method `with_theme` exists on the type `akinator_rs::Akinator` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/akinator-rs-0.1.13/src/lib.rs:145:5 [INFO] [stdout] | [INFO] [stdout] 145 | pub const fn with_theme(mut self, theme: Theme) -> Self { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] help: consider using `Result::expect` to unwrap the `akinator_rs::Akinator` value, panicking if the value is a `Result::Err` [INFO] [stdout] | [INFO] [stdout] 59 | akinator = akinator.expect("REASON").with_theme(theme.into()); [INFO] [stdout] | +++++++++++++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0599]: no method named `with_language` found for enum `Result` in the current scope [INFO] [stdout] --> src/async_akinator.rs:63:33 [INFO] [stdout] | [INFO] [stdout] 63 | akinator = akinator.with_language(language.into()); [INFO] [stdout] | ^^^^^^^^^^^^^ method not found in `Result` [INFO] [stdout] | [INFO] [stdout] note: the method `with_language` exists on the type `akinator_rs::Akinator` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/akinator-rs-0.1.13/src/lib.rs:152:5 [INFO] [stdout] | [INFO] [stdout] 152 | pub const fn with_language(mut self, language: Language) -> Self { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] help: consider using `Result::expect` to unwrap the `akinator_rs::Akinator` value, panicking if the value is a `Result::Err` [INFO] [stdout] | [INFO] [stdout] 63 | akinator = akinator.expect("REASON").with_language(language.into()); [INFO] [stdout] | +++++++++++++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0599]: no method named `with_theme` found for enum `Result` in the current scope [INFO] [stdout] --> src/async_akinator.rs:59:33 [INFO] [stdout] | [INFO] [stdout] 59 | akinator = akinator.with_theme(theme.into()); [INFO] [stdout] | ^^^^^^^^^^ method not found in `Result` [INFO] [stdout] | [INFO] [stdout] note: the method `with_theme` exists on the type `akinator_rs::Akinator` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/akinator-rs-0.1.13/src/lib.rs:145:5 [INFO] [stdout] | [INFO] [stdout] 145 | pub const fn with_theme(mut self, theme: Theme) -> Self { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] help: consider using `Result::expect` to unwrap the `akinator_rs::Akinator` value, panicking if the value is a `Result::Err` [INFO] [stdout] | [INFO] [stdout] 59 | akinator = akinator.expect("REASON").with_theme(theme.into()); [INFO] [stdout] | +++++++++++++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0599]: no method named `with_child_mode` found for enum `Result` in the current scope [INFO] [stdout] --> src/async_akinator.rs:67:33 [INFO] [stdout] | [INFO] [stdout] 67 | akinator = akinator.with_child_mode(); [INFO] [stdout] | ^^^^^^^^^^^^^^^ method not found in `Result` [INFO] [stdout] | [INFO] [stdout] note: the method `with_child_mode` exists on the type `akinator_rs::Akinator` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/akinator-rs-0.1.13/src/lib.rs:159:5 [INFO] [stdout] | [INFO] [stdout] 159 | pub const fn with_child_mode(mut self) -> Self { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] help: consider using `Result::expect` to unwrap the `akinator_rs::Akinator` value, panicking if the value is a `Result::Err` [INFO] [stdout] | [INFO] [stdout] 67 | akinator = akinator.expect("REASON").with_child_mode(); [INFO] [stdout] | +++++++++++++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0308]: mismatched types [INFO] [stdout] --> src/async_akinator.rs:71:34 [INFO] [stdout] | [INFO] [stdout] 71 | Arc::new(RwLock::new(akinator)) [INFO] [stdout] | ----------- ^^^^^^^^ expected `Akinator`, found `Result` [INFO] [stdout] | | [INFO] [stdout] | arguments to this function are incorrect [INFO] [stdout] | [INFO] [stdout] = note: expected struct `akinator_rs::Akinator` [INFO] [stdout] found enum `Result` [INFO] [stdout] note: associated function defined here [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/tokio-1.47.1/src/sync/rwlock.rs:204:12 [INFO] [stdout] | [INFO] [stdout] 204 | pub fn new(value: T) -> RwLock [INFO] [stdout] | ^^^ [INFO] [stdout] help: consider using `Result::expect` to unwrap the `Result` value, panicking if the value is a `Result::Err` [INFO] [stdout] | [INFO] [stdout] 71 | Arc::new(RwLock::new(akinator.expect("REASON"))) [INFO] [stdout] | +++++++++++++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0599]: no method named `with_language` found for enum `Result` in the current scope [INFO] [stdout] --> src/async_akinator.rs:63:33 [INFO] [stdout] | [INFO] [stdout] 63 | akinator = akinator.with_language(language.into()); [INFO] [stdout] | ^^^^^^^^^^^^^ method not found in `Result` [INFO] [stdout] | [INFO] [stdout] note: the method `with_language` exists on the type `akinator_rs::Akinator` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/akinator-rs-0.1.13/src/lib.rs:152:5 [INFO] [stdout] | [INFO] [stdout] 152 | pub const fn with_language(mut self, language: Language) -> Self { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] help: consider using `Result::expect` to unwrap the `akinator_rs::Akinator` value, panicking if the value is a `Result::Err` [INFO] [stdout] | [INFO] [stdout] 63 | akinator = akinator.expect("REASON").with_language(language.into()); [INFO] [stdout] | +++++++++++++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0599]: no method named `with_child_mode` found for enum `Result` in the current scope [INFO] [stdout] --> src/async_akinator.rs:67:33 [INFO] [stdout] | [INFO] [stdout] 67 | akinator = akinator.with_child_mode(); [INFO] [stdout] | ^^^^^^^^^^^^^^^ method not found in `Result` [INFO] [stdout] | [INFO] [stdout] note: the method `with_child_mode` exists on the type `akinator_rs::Akinator` [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/akinator-rs-0.1.13/src/lib.rs:159:5 [INFO] [stdout] | [INFO] [stdout] 159 | pub const fn with_child_mode(mut self) -> Self { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] help: consider using `Result::expect` to unwrap the `akinator_rs::Akinator` value, panicking if the value is a `Result::Err` [INFO] [stdout] | [INFO] [stdout] 67 | akinator = akinator.expect("REASON").with_child_mode(); [INFO] [stdout] | +++++++++++++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0308]: mismatched types [INFO] [stdout] --> src/async_akinator.rs:71:34 [INFO] [stdout] | [INFO] [stdout] 71 | Arc::new(RwLock::new(akinator)) [INFO] [stdout] | ----------- ^^^^^^^^ expected `Akinator`, found `Result` [INFO] [stdout] | | [INFO] [stdout] | arguments to this function are incorrect [INFO] [stdout] | [INFO] [stdout] = note: expected struct `akinator_rs::Akinator` [INFO] [stdout] found enum `Result` [INFO] [stdout] note: associated function defined here [INFO] [stdout] --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/tokio-1.47.1/src/sync/rwlock.rs:204:12 [INFO] [stdout] | [INFO] [stdout] 204 | pub fn new(value: T) -> RwLock [INFO] [stdout] | ^^^ [INFO] [stdout] help: consider using `Result::expect` to unwrap the `Result` value, panicking if the value is a `Result::Err` [INFO] [stdout] | [INFO] [stdout] 71 | Arc::new(RwLock::new(akinator.expect("REASON"))) [INFO] [stdout] | +++++++++++++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] Some errors have detailed explanations: E0308, E0599. [INFO] [stdout] [INFO] [stdout] For more information about an error, try `rustc --explain E0308`. [INFO] [stdout] [INFO] [stderr] error: could not compile `akinator-py` (lib) due to 8 previous errors; 16 warnings emitted [INFO] [stderr] warning: build failed, waiting for other jobs to finish... [INFO] [stdout] Some errors have detailed explanations: E0308, E0599. [INFO] [stdout] [INFO] [stdout] For more information about an error, try `rustc --explain E0308`. [INFO] [stdout] [INFO] [stderr] error: could not compile `akinator-py` (lib test) due to 8 previous errors; 16 warnings emitted [INFO] running `Command { std: "docker" "inspect" "b76acb22062081518931c400f165f2fdb98341692a0ef9c8f4902cd5dbffbcef", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "b76acb22062081518931c400f165f2fdb98341692a0ef9c8f4902cd5dbffbcef", kill_on_drop: false }` [INFO] [stdout] b76acb22062081518931c400f165f2fdb98341692a0ef9c8f4902cd5dbffbcef