[INFO] cloning repository https://github.com/wolfspider/limbo-freebsd [INFO] running `Command { std: "git" "-c" "credential.helper=" "-c" "credential.helper=/workspace/cargo-home/bin/git-credential-null" "clone" "--bare" "https://github.com/wolfspider/limbo-freebsd" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fwolfspider%2Flimbo-freebsd", kill_on_drop: false }` [INFO] [stderr] Cloning into bare repository '/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fwolfspider%2Flimbo-freebsd'... [INFO] running `Command { std: "git" "rev-parse" "HEAD", kill_on_drop: false }` [INFO] [stdout] 114c60ebd89f660bca08d527be19532513a40046 [INFO] testing wolfspider/limbo-freebsd against nightly-2025-01-18+rustflags=-Zrandomize-layout for randomize-layout-3 [INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fwolfspider%2Flimbo-freebsd" "/workspace/builds/worker-1-tc2/source", kill_on_drop: false }` [INFO] [stderr] Cloning into '/workspace/builds/worker-1-tc2/source'... [INFO] [stderr] done. [INFO] validating manifest of git repo https://github.com/wolfspider/limbo-freebsd on toolchain nightly-2025-01-18 [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+nightly-2025-01-18" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] started tweaking git repo https://github.com/wolfspider/limbo-freebsd [INFO] finished tweaking git repo https://github.com/wolfspider/limbo-freebsd [INFO] tweaked toml for git repo https://github.com/wolfspider/limbo-freebsd written to /workspace/builds/worker-1-tc2/source/Cargo.toml [INFO] crate git repo https://github.com/wolfspider/limbo-freebsd already has a lockfile, it will not be regenerated [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+nightly-2025-01-18" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-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:819108c5571ea2e421544af4d832f968d213c87fbe3707a016657f43d2f853bc" "/opt/rustwide/cargo-home/bin/cargo" "+nightly-2025-01-18" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 12b1b812503c45eb124bf42684abdc8f61167abcfa52e03c39d6e73d1467894a [INFO] running `Command { std: "docker" "start" "-a" "12b1b812503c45eb124bf42684abdc8f61167abcfa52e03c39d6e73d1467894a", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "12b1b812503c45eb124bf42684abdc8f61167abcfa52e03c39d6e73d1467894a", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "12b1b812503c45eb124bf42684abdc8f61167abcfa52e03c39d6e73d1467894a", kill_on_drop: false }` [INFO] [stdout] 12b1b812503c45eb124bf42684abdc8f61167abcfa52e03c39d6e73d1467894a [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-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 -Zrandomize-layout" "-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:819108c5571ea2e421544af4d832f968d213c87fbe3707a016657f43d2f853bc" "/opt/rustwide/cargo-home/bin/cargo" "+nightly-2025-01-18" "build" "--frozen" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 746d0dafde960150fb89c56c66989ef37e1d063e3687a122cfe5fe676c813558 [INFO] running `Command { std: "docker" "start" "-a" "746d0dafde960150fb89c56c66989ef37e1d063e3687a122cfe5fe676c813558", kill_on_drop: false }` [INFO] [stderr] Compiling proc-macro2 v1.0.86 [INFO] [stderr] Compiling unicode-ident v1.0.12 [INFO] [stderr] Compiling once_cell v1.19.0 [INFO] [stderr] Compiling libc v0.2.155 [INFO] [stderr] Compiling serde v1.0.204 [INFO] [stderr] Compiling bitflags v2.6.0 [INFO] [stderr] Compiling autocfg v1.3.0 [INFO] [stderr] Compiling cc v1.0.104 [INFO] [stderr] Compiling target-lexicon v0.12.16 [INFO] [stderr] Compiling anstyle v1.0.7 [INFO] [stderr] Compiling itoa v1.0.11 [INFO] [stderr] Compiling ryu v1.0.18 [INFO] [stderr] Compiling uncased v0.9.10 [INFO] [stderr] Compiling ahash v0.8.11 [INFO] [stderr] Compiling siphasher v0.3.11 [INFO] [stderr] Compiling allocator-api2 v0.2.18 [INFO] [stderr] Compiling thiserror v1.0.61 [INFO] [stderr] Compiling rand_core v0.6.4 [INFO] [stderr] Compiling aho-corasick v1.1.3 [INFO] [stderr] Compiling regex-syntax v0.8.4 [INFO] [stderr] Compiling log v0.4.22 [INFO] [stderr] Compiling rand v0.8.5 [INFO] [stderr] Compiling anstyle-parse v0.2.4 [INFO] [stderr] Compiling anstyle-query v1.1.0 [INFO] [stderr] Compiling colorchoice v1.0.1 [INFO] [stderr] Compiling rustix v0.38.34 [INFO] [stderr] Compiling num-traits v0.2.19 [INFO] [stderr] Compiling is_terminal_polyfill v1.70.0 [INFO] [stderr] Compiling ucd-trie v0.1.6 [INFO] [stderr] Compiling phf_shared v0.11.2 [INFO] [stderr] Compiling anstream v0.6.14 [INFO] [stderr] Compiling predicates-core v1.0.8 [INFO] [stderr] Compiling hashbrown v0.14.5 [INFO] [stderr] Compiling linux-raw-sys v0.4.14 [INFO] [stderr] Compiling cfg_aliases v0.2.1 [INFO] [stderr] Compiling mockall_derive v0.13.0 [INFO] [stderr] Compiling ppv-lite86 v0.2.17 [INFO] [stderr] Compiling serde_json v1.0.120 [INFO] [stderr] Compiling nix v0.29.0 [INFO] [stderr] Compiling termtree v0.4.1 [INFO] [stderr] Compiling minimal-lexical v0.2.1 [INFO] [stderr] Compiling iana-time-zone v0.1.60 [INFO] [stderr] Compiling quote v1.0.36 [INFO] [stderr] Compiling pyo3-build-config v0.22.2 [INFO] [stderr] Compiling phf_generator v0.11.2 [INFO] [stderr] Compiling io-uring v0.6.4 [INFO] [stderr] Compiling phf_codegen v0.11.2 [INFO] [stderr] Compiling clap_lex v0.7.1 [INFO] [stderr] Compiling nom v7.1.3 [INFO] [stderr] Compiling phf v0.11.2 [INFO] [stderr] Compiling predicates-tree v1.0.11 [INFO] [stderr] Compiling syn v2.0.69 [INFO] [stderr] Compiling clap_builder v4.5.8 [INFO] [stderr] Compiling predicates v3.1.2 [INFO] [stderr] Compiling byteorder v1.5.0 [INFO] [stderr] Compiling downcast v0.11.0 [INFO] [stderr] Compiling fallible-iterator v0.3.0 [INFO] [stderr] Compiling fast-float v0.2.0 [INFO] [stderr] Compiling wasm-bindgen-shared v0.2.92 [INFO] [stderr] Compiling fragile v2.0.0 [INFO] [stderr] Compiling ordered-float v4.2.1 [INFO] [stderr] Compiling chrono v0.4.38 [INFO] [stderr] Compiling cfg_block v0.1.1 [INFO] [stderr] Compiling sieve-cache v0.1.4 [INFO] [stderr] Compiling hex v0.4.3 [INFO] [stderr] Compiling libmimalloc-sys v0.1.39 [INFO] [stderr] Compiling sqlite3-parser v0.13.0 [INFO] [stderr] Compiling bumpalo v3.16.0 [INFO] [stderr] Compiling winnow v0.6.18 [INFO] [stderr] Compiling getrandom v0.2.15 [INFO] [stderr] Compiling smallvec v1.13.2 [INFO] [stderr] Compiling indexmap v2.2.6 [INFO] [stderr] Compiling rand_chacha v0.3.1 [INFO] [stderr] Compiling fastrand v2.1.0 [INFO] [stderr] Compiling regex-automata v0.4.7 [INFO] [stderr] Compiling julian_day_converter v0.3.2 [INFO] [stderr] Compiling anyhow v1.0.86 [INFO] [stderr] Compiling tempfile v3.10.1 [INFO] [stderr] Compiling pyo3-macros-backend v0.22.2 [INFO] [stderr] Compiling pyo3-ffi v0.22.2 [INFO] [stderr] Compiling syn v1.0.109 [INFO] [stderr] Compiling cfg_aliases v0.1.1 [INFO] [stderr] Compiling cbindgen v0.27.0 [INFO] [stderr] Compiling pkg-config v0.3.30 [INFO] [stderr] Compiling clap v4.5.8 [INFO] [stderr] Compiling mimalloc v0.1.43 [INFO] [stderr] Compiling nix v0.28.0 [INFO] [stderr] Compiling nibble_vec v0.1.0 [INFO] [stderr] Compiling memoffset v0.9.1 [INFO] [stderr] Compiling heck v0.4.1 [INFO] [stderr] Compiling termcolor v1.4.1 [INFO] [stderr] Compiling endian-type v0.1.2 [INFO] [stderr] Compiling wasm-bindgen v0.2.92 [INFO] [stderr] Compiling unicode-width v0.1.13 [INFO] [stderr] Compiling radix_trie v0.2.1 [INFO] [stderr] Compiling dirs-sys v0.4.1 [INFO] [stderr] Compiling fd-lock v3.0.13 [INFO] [stderr] Compiling pyo3 v0.22.2 [INFO] [stderr] Compiling is-terminal v0.4.12 [INFO] [stderr] Compiling nix v0.26.4 [INFO] [stderr] Compiling csv-core v0.1.11 [INFO] [stderr] Compiling unicode-segmentation v1.11.0 [INFO] [stderr] Compiling home v0.5.9 [INFO] [stderr] Compiling dirs v5.0.1 [INFO] [stderr] Compiling py-limbo v0.0.4 (/opt/rustwide/workdir/bindings/python) [INFO] [stderr] Compiling hashlink v0.8.4 [INFO] [stderr] Compiling libsqlite3-sys v0.26.0 [INFO] [stderr] Compiling fallible-iterator v0.2.0 [INFO] [stderr] Compiling unindent v0.2.3 [INFO] [stderr] Compiling fallible-streaming-iterator v0.1.9 [INFO] [stderr] Compiling indoc v2.0.5 [INFO] [stderr] Compiling ctrlc v3.4.4 [INFO] [stderr] Compiling rustyline v12.0.0 [INFO] [stderr] Compiling regex v1.10.5 [INFO] [stderr] Compiling wasm-bindgen-backend v0.2.92 [INFO] [stderr] Compiling cli-table-derive v0.4.6 [INFO] [stderr] Compiling env_filter v0.1.0 [INFO] [stderr] Compiling env_logger v0.10.2 [INFO] [stderr] Compiling env_logger v0.11.3 [INFO] [stderr] Compiling serde_derive v1.0.204 [INFO] [stderr] Compiling thiserror-impl v1.0.61 [INFO] [stderr] Compiling clap_derive v4.5.8 [INFO] [stderr] Compiling wasm-bindgen-macro-support v0.2.92 [INFO] [stderr] Compiling pest v2.7.11 [INFO] [stderr] Compiling wasm-bindgen-macro v0.2.92 [INFO] [stderr] Compiling console_error_panic_hook v0.1.7 [INFO] [stderr] Compiling pyo3-macros v0.22.2 [INFO] [stderr] Compiling mockall v0.13.0 [INFO] [stderr] Compiling pest_meta v2.7.11 [INFO] [stderr] Compiling pest_generator v2.7.11 [INFO] [stderr] Compiling pest_derive v2.7.11 [INFO] [stderr] Compiling toml_datetime v0.6.8 [INFO] [stderr] Compiling serde_spanned v0.6.7 [INFO] [stderr] Compiling csv v1.3.0 [INFO] [stderr] Compiling toml_edit v0.22.20 [INFO] [stderr] Compiling cli-table v0.4.9 [INFO] [stderr] Compiling rusqlite v0.29.0 [INFO] [stderr] Compiling jsonb v0.4.1 [INFO] [stderr] Compiling toml v0.8.19 [INFO] [stderr] Compiling limbo_core v0.0.4 (/opt/rustwide/workdir/core) [INFO] [stderr] Compiling core_tester v0.0.4 (/opt/rustwide/workdir/test) [INFO] [stderr] Compiling limbo_sqlite3 v0.0.4 (/opt/rustwide/workdir/sqlite3) [INFO] [stderr] Compiling limbo v0.0.4 (/opt/rustwide/workdir/cli) [INFO] [stderr] Compiling limbo_sim v0.0.4 (/opt/rustwide/workdir/simulator) [INFO] [stderr] Compiling limbo-wasm v0.0.4 (/opt/rustwide/workdir/bindings/wasm) [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / create_exception!( [INFO] [stdout] 5 | | limbo, [INFO] [stdout] 6 | | Warning, [INFO] [stdout] 7 | | PyException, [INFO] [stdout] 8 | | "Exception raised for important warnings like data truncations while inserting." [INFO] [stdout] 9 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / create_exception!( [INFO] [stdout] 5 | | limbo, [INFO] [stdout] 6 | | Warning, [INFO] [stdout] 7 | | PyException, [INFO] [stdout] 8 | | "Exception raised for important warnings like data truncations while inserting." [INFO] [stdout] 9 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / create_exception!( [INFO] [stdout] 5 | | limbo, [INFO] [stdout] 6 | | Warning, [INFO] [stdout] 7 | | PyException, [INFO] [stdout] 8 | | "Exception raised for important warnings like data truncations while inserting." [INFO] [stdout] 9 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / create_exception!( [INFO] [stdout] 5 | | limbo, [INFO] [stdout] 6 | | Warning, [INFO] [stdout] 7 | | PyException, [INFO] [stdout] 8 | | "Exception raised for important warnings like data truncations while inserting." [INFO] [stdout] 9 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / create_exception!( [INFO] [stdout] 5 | | limbo, [INFO] [stdout] 6 | | Warning, [INFO] [stdout] 7 | | PyException, [INFO] [stdout] 8 | | "Exception raised for important warnings like data truncations while inserting." [INFO] [stdout] 9 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / create_exception!( [INFO] [stdout] 5 | | limbo, [INFO] [stdout] 6 | | Warning, [INFO] [stdout] 7 | | PyException, [INFO] [stdout] 8 | | "Exception raised for important warnings like data truncations while inserting." [INFO] [stdout] 9 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / create_exception!( [INFO] [stdout] 5 | | limbo, [INFO] [stdout] 6 | | Warning, [INFO] [stdout] 7 | | PyException, [INFO] [stdout] 8 | | "Exception raised for important warnings like data truncations while inserting." [INFO] [stdout] 9 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / create_exception!( [INFO] [stdout] 5 | | limbo, [INFO] [stdout] 6 | | Warning, [INFO] [stdout] 7 | | PyException, [INFO] [stdout] 8 | | "Exception raised for important warnings like data truncations while inserting." [INFO] [stdout] 9 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / create_exception!( [INFO] [stdout] 5 | | limbo, [INFO] [stdout] 6 | | Warning, [INFO] [stdout] 7 | | PyException, [INFO] [stdout] 8 | | "Exception raised for important warnings like data truncations while inserting." [INFO] [stdout] 9 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / create_exception!( [INFO] [stdout] 5 | | limbo, [INFO] [stdout] 6 | | Warning, [INFO] [stdout] 7 | | PyException, [INFO] [stdout] 8 | | "Exception raised for important warnings like data truncations while inserting." [INFO] [stdout] 9 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` 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_extract` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(limbo, Error, PyException, "Base class for all other error exceptions. Catch all database-related errors using this class.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(limbo, Error, PyException, "Base class for all other error exceptions. Catch all database-related errors using this class.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(limbo, Error, PyException, "Base class for all other error exceptions. Catch all database-related errors using this class.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(limbo, Error, PyException, "Base class for all other error exceptions. Catch all database-related errors using this class.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(limbo, Error, PyException, "Base class for all other error exceptions. Catch all database-related errors using this class.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(limbo, Error, PyException, "Base class for all other error exceptions. Catch all database-related errors using this class.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(limbo, Error, PyException, "Base class for all other error exceptions. Catch all database-related errors using this class.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(limbo, Error, PyException, "Base class for all other error exceptions. Catch all database-related errors using this class.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(limbo, Error, PyException, "Base class for all other error exceptions. Catch all database-related errors using this class.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(limbo, Error, PyException, "Base class for all other error exceptions. Catch all database-related errors using this class.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` 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_extract` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:12:1 [INFO] [stdout] | [INFO] [stdout] 12 | / create_exception!( [INFO] [stdout] 13 | | limbo, [INFO] [stdout] 14 | | InterfaceError, [INFO] [stdout] 15 | | Error, [INFO] [stdout] 16 | | "Raised for errors related to the database interface rather than the database itself." [INFO] [stdout] 17 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:12:1 [INFO] [stdout] | [INFO] [stdout] 12 | / create_exception!( [INFO] [stdout] 13 | | limbo, [INFO] [stdout] 14 | | InterfaceError, [INFO] [stdout] 15 | | Error, [INFO] [stdout] 16 | | "Raised for errors related to the database interface rather than the database itself." [INFO] [stdout] 17 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:12:1 [INFO] [stdout] | [INFO] [stdout] 12 | / create_exception!( [INFO] [stdout] 13 | | limbo, [INFO] [stdout] 14 | | InterfaceError, [INFO] [stdout] 15 | | Error, [INFO] [stdout] 16 | | "Raised for errors related to the database interface rather than the database itself." [INFO] [stdout] 17 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:12:1 [INFO] [stdout] | [INFO] [stdout] 12 | / create_exception!( [INFO] [stdout] 13 | | limbo, [INFO] [stdout] 14 | | InterfaceError, [INFO] [stdout] 15 | | Error, [INFO] [stdout] 16 | | "Raised for errors related to the database interface rather than the database itself." [INFO] [stdout] 17 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:12:1 [INFO] [stdout] | [INFO] [stdout] 12 | / create_exception!( [INFO] [stdout] 13 | | limbo, [INFO] [stdout] 14 | | InterfaceError, [INFO] [stdout] 15 | | Error, [INFO] [stdout] 16 | | "Raised for errors related to the database interface rather than the database itself." [INFO] [stdout] 17 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:12:1 [INFO] [stdout] | [INFO] [stdout] 12 | / create_exception!( [INFO] [stdout] 13 | | limbo, [INFO] [stdout] 14 | | InterfaceError, [INFO] [stdout] 15 | | Error, [INFO] [stdout] 16 | | "Raised for errors related to the database interface rather than the database itself." [INFO] [stdout] 17 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:12:1 [INFO] [stdout] | [INFO] [stdout] 12 | / create_exception!( [INFO] [stdout] 13 | | limbo, [INFO] [stdout] 14 | | InterfaceError, [INFO] [stdout] 15 | | Error, [INFO] [stdout] 16 | | "Raised for errors related to the database interface rather than the database itself." [INFO] [stdout] 17 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:12:1 [INFO] [stdout] | [INFO] [stdout] 12 | / create_exception!( [INFO] [stdout] 13 | | limbo, [INFO] [stdout] 14 | | InterfaceError, [INFO] [stdout] 15 | | Error, [INFO] [stdout] 16 | | "Raised for errors related to the database interface rather than the database itself." [INFO] [stdout] 17 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:12:1 [INFO] [stdout] | [INFO] [stdout] 12 | / create_exception!( [INFO] [stdout] 13 | | limbo, [INFO] [stdout] 14 | | InterfaceError, [INFO] [stdout] 15 | | Error, [INFO] [stdout] 16 | | "Raised for errors related to the database interface rather than the database itself." [INFO] [stdout] 17 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:12:1 [INFO] [stdout] | [INFO] [stdout] 12 | / create_exception!( [INFO] [stdout] 13 | | limbo, [INFO] [stdout] 14 | | InterfaceError, [INFO] [stdout] 15 | | Error, [INFO] [stdout] 16 | | "Raised for errors related to the database interface rather than the database itself." [INFO] [stdout] 17 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` 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_extract` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | / create_exception!( [INFO] [stdout] 19 | | limbo, [INFO] [stdout] 20 | | DatabaseError, [INFO] [stdout] 21 | | Error, [INFO] [stdout] 22 | | "Raised for errors that are related to the database." [INFO] [stdout] 23 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | / create_exception!( [INFO] [stdout] 19 | | limbo, [INFO] [stdout] 20 | | DatabaseError, [INFO] [stdout] 21 | | Error, [INFO] [stdout] 22 | | "Raised for errors that are related to the database." [INFO] [stdout] 23 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | / create_exception!( [INFO] [stdout] 19 | | limbo, [INFO] [stdout] 20 | | DatabaseError, [INFO] [stdout] 21 | | Error, [INFO] [stdout] 22 | | "Raised for errors that are related to the database." [INFO] [stdout] 23 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | / create_exception!( [INFO] [stdout] 19 | | limbo, [INFO] [stdout] 20 | | DatabaseError, [INFO] [stdout] 21 | | Error, [INFO] [stdout] 22 | | "Raised for errors that are related to the database." [INFO] [stdout] 23 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | / create_exception!( [INFO] [stdout] 19 | | limbo, [INFO] [stdout] 20 | | DatabaseError, [INFO] [stdout] 21 | | Error, [INFO] [stdout] 22 | | "Raised for errors that are related to the database." [INFO] [stdout] 23 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | / create_exception!( [INFO] [stdout] 19 | | limbo, [INFO] [stdout] 20 | | DatabaseError, [INFO] [stdout] 21 | | Error, [INFO] [stdout] 22 | | "Raised for errors that are related to the database." [INFO] [stdout] 23 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | / create_exception!( [INFO] [stdout] 19 | | limbo, [INFO] [stdout] 20 | | DatabaseError, [INFO] [stdout] 21 | | Error, [INFO] [stdout] 22 | | "Raised for errors that are related to the database." [INFO] [stdout] 23 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | / create_exception!( [INFO] [stdout] 19 | | limbo, [INFO] [stdout] 20 | | DatabaseError, [INFO] [stdout] 21 | | Error, [INFO] [stdout] 22 | | "Raised for errors that are related to the database." [INFO] [stdout] 23 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | / create_exception!( [INFO] [stdout] 19 | | limbo, [INFO] [stdout] 20 | | DatabaseError, [INFO] [stdout] 21 | | Error, [INFO] [stdout] 22 | | "Raised for errors that are related to the database." [INFO] [stdout] 23 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | / create_exception!( [INFO] [stdout] 19 | | limbo, [INFO] [stdout] 20 | | DatabaseError, [INFO] [stdout] 21 | | Error, [INFO] [stdout] 22 | | "Raised for errors that are related to the database." [INFO] [stdout] 23 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` 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_extract` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:25:1 [INFO] [stdout] | [INFO] [stdout] 25 | create_exception!(limbo, DataError, DatabaseError, "Raised for errors due to problems with the processed data like division by zero, numeric value out of range, etc.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:25:1 [INFO] [stdout] | [INFO] [stdout] 25 | create_exception!(limbo, DataError, DatabaseError, "Raised for errors due to problems with the processed data like division by zero, numeric value out of range, etc.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:25:1 [INFO] [stdout] | [INFO] [stdout] 25 | create_exception!(limbo, DataError, DatabaseError, "Raised for errors due to problems with the processed data like division by zero, numeric value out of range, etc.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:25:1 [INFO] [stdout] | [INFO] [stdout] 25 | create_exception!(limbo, DataError, DatabaseError, "Raised for errors due to problems with the processed data like division by zero, numeric value out of range, etc.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:25:1 [INFO] [stdout] | [INFO] [stdout] 25 | create_exception!(limbo, DataError, DatabaseError, "Raised for errors due to problems with the processed data like division by zero, numeric value out of range, etc.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:25:1 [INFO] [stdout] | [INFO] [stdout] 25 | create_exception!(limbo, DataError, DatabaseError, "Raised for errors due to problems with the processed data like division by zero, numeric value out of range, etc.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:25:1 [INFO] [stdout] | [INFO] [stdout] 25 | create_exception!(limbo, DataError, DatabaseError, "Raised for errors due to problems with the processed data like division by zero, numeric value out of range, etc.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:25:1 [INFO] [stdout] | [INFO] [stdout] 25 | create_exception!(limbo, DataError, DatabaseError, "Raised for errors due to problems with the processed data like division by zero, numeric value out of range, etc.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:25:1 [INFO] [stdout] | [INFO] [stdout] 25 | create_exception!(limbo, DataError, DatabaseError, "Raised for errors due to problems with the processed data like division by zero, numeric value out of range, etc.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:25:1 [INFO] [stdout] | [INFO] [stdout] 25 | create_exception!(limbo, DataError, DatabaseError, "Raised for errors due to problems with the processed data like division by zero, numeric value out of range, etc.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` 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_extract` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:26:1 [INFO] [stdout] | [INFO] [stdout] 26 | create_exception!(limbo, OperationalError, DatabaseError, "Raised for errors related to the database’s operation, not necessarily under the programmer's control.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:26:1 [INFO] [stdout] | [INFO] [stdout] 26 | create_exception!(limbo, OperationalError, DatabaseError, "Raised for errors related to the database’s operation, not necessarily under the programmer's control.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:26:1 [INFO] [stdout] | [INFO] [stdout] 26 | create_exception!(limbo, OperationalError, DatabaseError, "Raised for errors related to the database’s operation, not necessarily under the programmer's control.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:26:1 [INFO] [stdout] | [INFO] [stdout] 26 | create_exception!(limbo, OperationalError, DatabaseError, "Raised for errors related to the database’s operation, not necessarily under the programmer's control.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:26:1 [INFO] [stdout] | [INFO] [stdout] 26 | create_exception!(limbo, OperationalError, DatabaseError, "Raised for errors related to the database’s operation, not necessarily under the programmer's control.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:26:1 [INFO] [stdout] | [INFO] [stdout] 26 | create_exception!(limbo, OperationalError, DatabaseError, "Raised for errors related to the database’s operation, not necessarily under the programmer's control.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:26:1 [INFO] [stdout] | [INFO] [stdout] 26 | create_exception!(limbo, OperationalError, DatabaseError, "Raised for errors related to the database’s operation, not necessarily under the programmer's control.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:26:1 [INFO] [stdout] | [INFO] [stdout] 26 | create_exception!(limbo, OperationalError, DatabaseError, "Raised for errors related to the database’s operation, not necessarily under the programmer's control.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:26:1 [INFO] [stdout] | [INFO] [stdout] 26 | create_exception!(limbo, OperationalError, DatabaseError, "Raised for errors related to the database’s operation, not necessarily under the programmer's control.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:26:1 [INFO] [stdout] | [INFO] [stdout] 26 | create_exception!(limbo, OperationalError, DatabaseError, "Raised for errors related to the database’s operation, not necessarily under the programmer's control.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` 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_extract` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | create_exception!(limbo, IntegrityError, DatabaseError, "Raised when the relational integrity of the database is affected, e.g., a foreign key check fails.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | create_exception!(limbo, IntegrityError, DatabaseError, "Raised when the relational integrity of the database is affected, e.g., a foreign key check fails.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | create_exception!(limbo, IntegrityError, DatabaseError, "Raised when the relational integrity of the database is affected, e.g., a foreign key check fails.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | create_exception!(limbo, IntegrityError, DatabaseError, "Raised when the relational integrity of the database is affected, e.g., a foreign key check fails.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | create_exception!(limbo, IntegrityError, DatabaseError, "Raised when the relational integrity of the database is affected, e.g., a foreign key check fails.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | create_exception!(limbo, IntegrityError, DatabaseError, "Raised when the relational integrity of the database is affected, e.g., a foreign key check fails.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | create_exception!(limbo, IntegrityError, DatabaseError, "Raised when the relational integrity of the database is affected, e.g., a foreign key check fails.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | create_exception!(limbo, IntegrityError, DatabaseError, "Raised when the relational integrity of the database is affected, e.g., a foreign key check fails.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | create_exception!(limbo, IntegrityError, DatabaseError, "Raised when the relational integrity of the database is affected, e.g., a foreign key check fails.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | create_exception!(limbo, IntegrityError, DatabaseError, "Raised when the relational integrity of the database is affected, e.g., a foreign key check fails.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` 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_extract` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | create_exception!(limbo, InternalError, DatabaseError, "Raised when the database encounters an internal error, e.g., cursor is not valid anymore, transaction out of sync.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | create_exception!(limbo, InternalError, DatabaseError, "Raised when the database encounters an internal error, e.g., cursor is not valid anymore, transaction out of sync.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | create_exception!(limbo, InternalError, DatabaseError, "Raised when the database encounters an internal error, e.g., cursor is not valid anymore, transaction out of sync.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | create_exception!(limbo, InternalError, DatabaseError, "Raised when the database encounters an internal error, e.g., cursor is not valid anymore, transaction out of sync.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | create_exception!(limbo, InternalError, DatabaseError, "Raised when the database encounters an internal error, e.g., cursor is not valid anymore, transaction out of sync.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | create_exception!(limbo, InternalError, DatabaseError, "Raised when the database encounters an internal error, e.g., cursor is not valid anymore, transaction out of sync.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | create_exception!(limbo, InternalError, DatabaseError, "Raised when the database encounters an internal error, e.g., cursor is not valid anymore, transaction out of sync.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | create_exception!(limbo, InternalError, DatabaseError, "Raised when the database encounters an internal error, e.g., cursor is not valid anymore, transaction out of sync.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | create_exception!(limbo, InternalError, DatabaseError, "Raised when the database encounters an internal error, e.g., cursor is not valid anymore, transaction out of sync.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | create_exception!(limbo, InternalError, DatabaseError, "Raised when the database encounters an internal error, e.g., cursor is not valid anymore, transaction out of sync.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` 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_extract` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:29:1 [INFO] [stdout] | [INFO] [stdout] 29 | create_exception!(limbo, ProgrammingError, DatabaseError, "Raised for programming errors, e.g., table not found, syntax error in SQL, wrong number of parameters specified.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:29:1 [INFO] [stdout] | [INFO] [stdout] 29 | create_exception!(limbo, ProgrammingError, DatabaseError, "Raised for programming errors, e.g., table not found, syntax error in SQL, wrong number of parameters specified.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:29:1 [INFO] [stdout] | [INFO] [stdout] 29 | create_exception!(limbo, ProgrammingError, DatabaseError, "Raised for programming errors, e.g., table not found, syntax error in SQL, wrong number of parameters specified.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:29:1 [INFO] [stdout] | [INFO] [stdout] 29 | create_exception!(limbo, ProgrammingError, DatabaseError, "Raised for programming errors, e.g., table not found, syntax error in SQL, wrong number of parameters specified.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:29:1 [INFO] [stdout] | [INFO] [stdout] 29 | create_exception!(limbo, ProgrammingError, DatabaseError, "Raised for programming errors, e.g., table not found, syntax error in SQL, wrong number of parameters specified.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:29:1 [INFO] [stdout] | [INFO] [stdout] 29 | create_exception!(limbo, ProgrammingError, DatabaseError, "Raised for programming errors, e.g., table not found, syntax error in SQL, wrong number of parameters specified.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:29:1 [INFO] [stdout] | [INFO] [stdout] 29 | create_exception!(limbo, ProgrammingError, DatabaseError, "Raised for programming errors, e.g., table not found, syntax error in SQL, wrong number of parameters specified.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:29:1 [INFO] [stdout] | [INFO] [stdout] 29 | create_exception!(limbo, ProgrammingError, DatabaseError, "Raised for programming errors, e.g., table not found, syntax error in SQL, wrong number of parameters specified.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:29:1 [INFO] [stdout] | [INFO] [stdout] 29 | create_exception!(limbo, ProgrammingError, DatabaseError, "Raised for programming errors, e.g., table not found, syntax error in SQL, wrong number of parameters specified.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:29:1 [INFO] [stdout] | [INFO] [stdout] 29 | create_exception!(limbo, ProgrammingError, DatabaseError, "Raised for programming errors, e.g., table not found, syntax error in SQL, wrong number of parameters specified.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` 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_extract` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:30:1 [INFO] [stdout] | [INFO] [stdout] 30 | / create_exception!( [INFO] [stdout] 31 | | limbo, [INFO] [stdout] 32 | | NotSupportedError, [INFO] [stdout] 33 | | DatabaseError, [INFO] [stdout] 34 | | "Raised when a method or database API is used which is not supported by the database." [INFO] [stdout] 35 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:30:1 [INFO] [stdout] | [INFO] [stdout] 30 | / create_exception!( [INFO] [stdout] 31 | | limbo, [INFO] [stdout] 32 | | NotSupportedError, [INFO] [stdout] 33 | | DatabaseError, [INFO] [stdout] 34 | | "Raised when a method or database API is used which is not supported by the database." [INFO] [stdout] 35 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:30:1 [INFO] [stdout] | [INFO] [stdout] 30 | / create_exception!( [INFO] [stdout] 31 | | limbo, [INFO] [stdout] 32 | | NotSupportedError, [INFO] [stdout] 33 | | DatabaseError, [INFO] [stdout] 34 | | "Raised when a method or database API is used which is not supported by the database." [INFO] [stdout] 35 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:30:1 [INFO] [stdout] | [INFO] [stdout] 30 | / create_exception!( [INFO] [stdout] 31 | | limbo, [INFO] [stdout] 32 | | NotSupportedError, [INFO] [stdout] 33 | | DatabaseError, [INFO] [stdout] 34 | | "Raised when a method or database API is used which is not supported by the database." [INFO] [stdout] 35 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:30:1 [INFO] [stdout] | [INFO] [stdout] 30 | / create_exception!( [INFO] [stdout] 31 | | limbo, [INFO] [stdout] 32 | | NotSupportedError, [INFO] [stdout] 33 | | DatabaseError, [INFO] [stdout] 34 | | "Raised when a method or database API is used which is not supported by the database." [INFO] [stdout] 35 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:30:1 [INFO] [stdout] | [INFO] [stdout] 30 | / create_exception!( [INFO] [stdout] 31 | | limbo, [INFO] [stdout] 32 | | NotSupportedError, [INFO] [stdout] 33 | | DatabaseError, [INFO] [stdout] 34 | | "Raised when a method or database API is used which is not supported by the database." [INFO] [stdout] 35 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:30:1 [INFO] [stdout] | [INFO] [stdout] 30 | / create_exception!( [INFO] [stdout] 31 | | limbo, [INFO] [stdout] 32 | | NotSupportedError, [INFO] [stdout] 33 | | DatabaseError, [INFO] [stdout] 34 | | "Raised when a method or database API is used which is not supported by the database." [INFO] [stdout] 35 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:30:1 [INFO] [stdout] | [INFO] [stdout] 30 | / create_exception!( [INFO] [stdout] 31 | | limbo, [INFO] [stdout] 32 | | NotSupportedError, [INFO] [stdout] 33 | | DatabaseError, [INFO] [stdout] 34 | | "Raised when a method or database API is used which is not supported by the database." [INFO] [stdout] 35 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:30:1 [INFO] [stdout] | [INFO] [stdout] 30 | / create_exception!( [INFO] [stdout] 31 | | limbo, [INFO] [stdout] 32 | | NotSupportedError, [INFO] [stdout] 33 | | DatabaseError, [INFO] [stdout] 34 | | "Raised when a method or database API is used which is not supported by the database." [INFO] [stdout] 35 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:30:1 [INFO] [stdout] | [INFO] [stdout] 30 | / create_exception!( [INFO] [stdout] 31 | | limbo, [INFO] [stdout] 32 | | NotSupportedError, [INFO] [stdout] 33 | | DatabaseError, [INFO] [stdout] 34 | | "Raised when a method or database API is used which is not supported by the database." [INFO] [stdout] 35 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` 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_extract` 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] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 20.99s [INFO] running `Command { std: "docker" "inspect" "746d0dafde960150fb89c56c66989ef37e1d063e3687a122cfe5fe676c813558", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "746d0dafde960150fb89c56c66989ef37e1d063e3687a122cfe5fe676c813558", kill_on_drop: false }` [INFO] [stdout] 746d0dafde960150fb89c56c66989ef37e1d063e3687a122cfe5fe676c813558 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-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 -Zrandomize-layout" "-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:819108c5571ea2e421544af4d832f968d213c87fbe3707a016657f43d2f853bc" "/opt/rustwide/cargo-home/bin/cargo" "+nightly-2025-01-18" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 3427b476efe0a8329cedc2197ff0a29b4e94d30628c6276936e4633c9f933b34 [INFO] running `Command { std: "docker" "start" "-a" "3427b476efe0a8329cedc2197ff0a29b4e94d30628c6276936e4633c9f933b34", kill_on_drop: false }` [INFO] [stderr] Compiling serde v1.0.204 [INFO] [stderr] Compiling num-traits v0.2.19 [INFO] [stderr] Compiling serde_json v1.0.120 [INFO] [stderr] Compiling syn v2.0.69 [INFO] [stderr] Compiling ahash v0.8.11 [INFO] [stderr] Compiling slab v0.4.9 [INFO] [stderr] Compiling semver v1.0.23 [INFO] [stderr] Compiling futures-core v0.3.30 [INFO] [stderr] Compiling futures-sink v0.3.30 [INFO] [stderr] Compiling futures-io v0.3.30 [INFO] [stderr] Compiling pin-utils v0.1.0 [INFO] [stderr] Compiling pin-project-lite v0.2.14 [INFO] [stderr] Compiling crossbeam-utils v0.8.20 [INFO] [stderr] Compiling futures-task v0.3.30 [INFO] [stderr] Compiling rayon-core v1.12.1 [INFO] [stderr] Compiling either v1.13.0 [INFO] [stderr] Compiling half v2.4.1 [INFO] [stderr] Compiling lock_api v0.4.12 [INFO] [stderr] Compiling plotters-backend v0.3.6 [INFO] [stderr] Compiling futures-channel v0.3.30 [INFO] [stderr] Compiling uuid v1.9.1 [INFO] [stderr] Compiling glob v0.3.1 [INFO] [stderr] Compiling cpp_demangle v0.4.3 [INFO] [stderr] Compiling relative-path v1.9.3 [INFO] [stderr] Compiling ciborium-io v0.2.2 [INFO] [stderr] Compiling itertools v0.10.5 [INFO] [stderr] Compiling hashbrown v0.14.5 [INFO] [stderr] Compiling memmap2 v0.9.4 [INFO] [stderr] Compiling plotters-svg v0.3.6 [INFO] [stderr] Compiling ciborium-ll v0.2.2 [INFO] [stderr] Compiling findshlibs v0.10.2 [INFO] [stderr] Compiling backtrace v0.3.73 [INFO] [stderr] Compiling futures-timer v3.0.3 [INFO] [stderr] Compiling rustc_version v0.4.0 [INFO] [stderr] Compiling debugid v0.8.0 [INFO] [stderr] Compiling cast v0.3.0 [INFO] [stderr] Compiling stable_deref_trait v1.2.0 [INFO] [stderr] Compiling symbolic-demangle v12.9.2 [INFO] [stderr] Compiling arrayvec v0.7.4 [INFO] [stderr] Compiling bytemuck v1.16.1 [INFO] [stderr] Compiling gimli v0.29.0 [INFO] [stderr] Compiling parking_lot_core v0.9.10 [INFO] [stderr] Compiling symbolic-common v12.9.2 [INFO] [stderr] Compiling rgb v0.8.40 [INFO] [stderr] Compiling object v0.36.1 [INFO] [stderr] Compiling crossbeam-epoch v0.9.18 [INFO] [stderr] Compiling num-format v0.4.4 [INFO] [stderr] Compiling rstest_macros v0.18.2 [INFO] [stderr] Compiling quick-xml v0.26.0 [INFO] [stderr] Compiling str_stack v0.1.0 [INFO] [stderr] Compiling pprof v0.12.1 [INFO] [stderr] Compiling hashlink v0.8.4 [INFO] [stderr] Compiling anes v0.1.6 [INFO] [stderr] Compiling oorandom v11.1.4 [INFO] [stderr] Compiling crossbeam-deque v0.8.5 [INFO] [stderr] Compiling parking_lot v0.12.3 [INFO] [stderr] Compiling chrono v0.4.38 [INFO] [stderr] Compiling ordered-float v4.2.1 [INFO] [stderr] Compiling plotters v0.3.6 [INFO] [stderr] Compiling rusqlite v0.29.0 [INFO] [stderr] Compiling rayon v1.10.0 [INFO] [stderr] Compiling criterion-plot v0.5.0 [INFO] [stderr] Compiling julian_day_converter v0.3.2 [INFO] [stderr] Compiling addr2line v0.22.0 [INFO] [stderr] Compiling wasm-bindgen-backend v0.2.92 [INFO] [stderr] Compiling pyo3-macros-backend v0.22.2 [INFO] [stderr] Compiling serde_derive v1.0.204 [INFO] [stderr] Compiling thiserror-impl v1.0.61 [INFO] [stderr] Compiling mockall_derive v0.13.0 [INFO] [stderr] Compiling futures-macro v0.3.30 [INFO] [stderr] Compiling clap_derive v4.5.8 [INFO] [stderr] Compiling futures-util v0.3.30 [INFO] [stderr] Compiling wasm-bindgen-macro-support v0.2.92 [INFO] [stderr] Compiling thiserror v1.0.61 [INFO] [stderr] Compiling pest v2.7.11 [INFO] [stderr] Compiling wasm-bindgen-macro v0.2.92 [INFO] [stderr] Compiling clap v4.5.8 [INFO] [stderr] Compiling wasm-bindgen v0.2.92 [INFO] [stderr] Compiling mockall v0.13.0 [INFO] [stderr] Compiling console_error_panic_hook v0.1.7 [INFO] [stderr] Compiling pyo3-macros v0.22.2 [INFO] [stderr] Compiling pest_meta v2.7.11 [INFO] [stderr] Compiling futures-executor v0.3.30 [INFO] [stderr] Compiling pyo3 v0.22.2 [INFO] [stderr] Compiling futures v0.3.30 [INFO] [stderr] Compiling rstest v0.18.2 [INFO] [stderr] Compiling pest_generator v2.7.11 [INFO] [stderr] Compiling pest_derive v2.7.11 [INFO] [stderr] Compiling indexmap v2.2.6 [INFO] [stderr] Compiling ciborium v0.2.2 [INFO] [stderr] Compiling csv v1.3.0 [INFO] [stderr] Compiling toml_datetime v0.6.8 [INFO] [stderr] Compiling serde_spanned v0.6.7 [INFO] [stderr] Compiling toml_edit v0.22.20 [INFO] [stderr] Compiling cli-table v0.4.9 [INFO] [stderr] Compiling sqlite3-parser v0.13.0 [INFO] [stderr] Compiling inferno v0.11.19 [INFO] [stderr] Compiling jsonb v0.4.1 [INFO] [stderr] Compiling tinytemplate v1.2.1 [INFO] [stderr] Compiling criterion v0.5.1 [INFO] [stderr] Compiling toml v0.8.19 [INFO] [stderr] Compiling limbo_core v0.0.4 (/opt/rustwide/workdir/core) [INFO] [stderr] Compiling cbindgen v0.27.0 [INFO] [stderr] Compiling core_tester v0.0.4 (/opt/rustwide/workdir/test) [INFO] [stderr] Compiling limbo_sqlite3 v0.0.4 (/opt/rustwide/workdir/sqlite3) [INFO] [stderr] Compiling limbo_sim v0.0.4 (/opt/rustwide/workdir/simulator) [INFO] [stderr] Compiling limbo-wasm v0.0.4 (/opt/rustwide/workdir/bindings/wasm) [INFO] [stderr] Compiling py-limbo v0.0.4 (/opt/rustwide/workdir/bindings/python) [INFO] [stderr] Compiling limbo v0.0.4 (/opt/rustwide/workdir/cli) [INFO] [stdout] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / create_exception!( [INFO] [stdout] 5 | | limbo, [INFO] [stdout] 6 | | Warning, [INFO] [stdout] 7 | | PyException, [INFO] [stdout] 8 | | "Exception raised for important warnings like data truncations while inserting." [INFO] [stdout] 9 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / create_exception!( [INFO] [stdout] 5 | | limbo, [INFO] [stdout] 6 | | Warning, [INFO] [stdout] 7 | | PyException, [INFO] [stdout] 8 | | "Exception raised for important warnings like data truncations while inserting." [INFO] [stdout] 9 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / create_exception!( [INFO] [stdout] 5 | | limbo, [INFO] [stdout] 6 | | Warning, [INFO] [stdout] 7 | | PyException, [INFO] [stdout] 8 | | "Exception raised for important warnings like data truncations while inserting." [INFO] [stdout] 9 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / create_exception!( [INFO] [stdout] 5 | | limbo, [INFO] [stdout] 6 | | Warning, [INFO] [stdout] 7 | | PyException, [INFO] [stdout] 8 | | "Exception raised for important warnings like data truncations while inserting." [INFO] [stdout] 9 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / create_exception!( [INFO] [stdout] 5 | | limbo, [INFO] [stdout] 6 | | Warning, [INFO] [stdout] 7 | | PyException, [INFO] [stdout] 8 | | "Exception raised for important warnings like data truncations while inserting." [INFO] [stdout] 9 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / create_exception!( [INFO] [stdout] 5 | | limbo, [INFO] [stdout] 6 | | Warning, [INFO] [stdout] 7 | | PyException, [INFO] [stdout] 8 | | "Exception raised for important warnings like data truncations while inserting." [INFO] [stdout] 9 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / create_exception!( [INFO] [stdout] 5 | | limbo, [INFO] [stdout] 6 | | Warning, [INFO] [stdout] 7 | | PyException, [INFO] [stdout] 8 | | "Exception raised for important warnings like data truncations while inserting." [INFO] [stdout] 9 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / create_exception!( [INFO] [stdout] 5 | | limbo, [INFO] [stdout] 6 | | Warning, [INFO] [stdout] 7 | | PyException, [INFO] [stdout] 8 | | "Exception raised for important warnings like data truncations while inserting." [INFO] [stdout] 9 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / create_exception!( [INFO] [stdout] 5 | | limbo, [INFO] [stdout] 6 | | Warning, [INFO] [stdout] 7 | | PyException, [INFO] [stdout] 8 | | "Exception raised for important warnings like data truncations while inserting." [INFO] [stdout] 9 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | / create_exception!( [INFO] [stdout] 5 | | limbo, [INFO] [stdout] 6 | | Warning, [INFO] [stdout] 7 | | PyException, [INFO] [stdout] 8 | | "Exception raised for important warnings like data truncations while inserting." [INFO] [stdout] 9 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` 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_extract` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(limbo, Error, PyException, "Base class for all other error exceptions. Catch all database-related errors using this class.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(limbo, Error, PyException, "Base class for all other error exceptions. Catch all database-related errors using this class.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(limbo, Error, PyException, "Base class for all other error exceptions. Catch all database-related errors using this class.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(limbo, Error, PyException, "Base class for all other error exceptions. Catch all database-related errors using this class.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(limbo, Error, PyException, "Base class for all other error exceptions. Catch all database-related errors using this class.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(limbo, Error, PyException, "Base class for all other error exceptions. Catch all database-related errors using this class.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(limbo, Error, PyException, "Base class for all other error exceptions. Catch all database-related errors using this class.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(limbo, Error, PyException, "Base class for all other error exceptions. Catch all database-related errors using this class.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(limbo, Error, PyException, "Base class for all other error exceptions. Catch all database-related errors using this class.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:10:1 [INFO] [stdout] | [INFO] [stdout] 10 | create_exception!(limbo, Error, PyException, "Base class for all other error exceptions. Catch all database-related errors using this class.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` 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_extract` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:12:1 [INFO] [stdout] | [INFO] [stdout] 12 | / create_exception!( [INFO] [stdout] 13 | | limbo, [INFO] [stdout] 14 | | InterfaceError, [INFO] [stdout] 15 | | Error, [INFO] [stdout] 16 | | "Raised for errors related to the database interface rather than the database itself." [INFO] [stdout] 17 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:12:1 [INFO] [stdout] | [INFO] [stdout] 12 | / create_exception!( [INFO] [stdout] 13 | | limbo, [INFO] [stdout] 14 | | InterfaceError, [INFO] [stdout] 15 | | Error, [INFO] [stdout] 16 | | "Raised for errors related to the database interface rather than the database itself." [INFO] [stdout] 17 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:12:1 [INFO] [stdout] | [INFO] [stdout] 12 | / create_exception!( [INFO] [stdout] 13 | | limbo, [INFO] [stdout] 14 | | InterfaceError, [INFO] [stdout] 15 | | Error, [INFO] [stdout] 16 | | "Raised for errors related to the database interface rather than the database itself." [INFO] [stdout] 17 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:12:1 [INFO] [stdout] | [INFO] [stdout] 12 | / create_exception!( [INFO] [stdout] 13 | | limbo, [INFO] [stdout] 14 | | InterfaceError, [INFO] [stdout] 15 | | Error, [INFO] [stdout] 16 | | "Raised for errors related to the database interface rather than the database itself." [INFO] [stdout] 17 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:12:1 [INFO] [stdout] | [INFO] [stdout] 12 | / create_exception!( [INFO] [stdout] 13 | | limbo, [INFO] [stdout] 14 | | InterfaceError, [INFO] [stdout] 15 | | Error, [INFO] [stdout] 16 | | "Raised for errors related to the database interface rather than the database itself." [INFO] [stdout] 17 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:12:1 [INFO] [stdout] | [INFO] [stdout] 12 | / create_exception!( [INFO] [stdout] 13 | | limbo, [INFO] [stdout] 14 | | InterfaceError, [INFO] [stdout] 15 | | Error, [INFO] [stdout] 16 | | "Raised for errors related to the database interface rather than the database itself." [INFO] [stdout] 17 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:12:1 [INFO] [stdout] | [INFO] [stdout] 12 | / create_exception!( [INFO] [stdout] 13 | | limbo, [INFO] [stdout] 14 | | InterfaceError, [INFO] [stdout] 15 | | Error, [INFO] [stdout] 16 | | "Raised for errors related to the database interface rather than the database itself." [INFO] [stdout] 17 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:12:1 [INFO] [stdout] | [INFO] [stdout] 12 | / create_exception!( [INFO] [stdout] 13 | | limbo, [INFO] [stdout] 14 | | InterfaceError, [INFO] [stdout] 15 | | Error, [INFO] [stdout] 16 | | "Raised for errors related to the database interface rather than the database itself." [INFO] [stdout] 17 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:12:1 [INFO] [stdout] | [INFO] [stdout] 12 | / create_exception!( [INFO] [stdout] 13 | | limbo, [INFO] [stdout] 14 | | InterfaceError, [INFO] [stdout] 15 | | Error, [INFO] [stdout] 16 | | "Raised for errors related to the database interface rather than the database itself." [INFO] [stdout] 17 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:12:1 [INFO] [stdout] | [INFO] [stdout] 12 | / create_exception!( [INFO] [stdout] 13 | | limbo, [INFO] [stdout] 14 | | InterfaceError, [INFO] [stdout] 15 | | Error, [INFO] [stdout] 16 | | "Raised for errors related to the database interface rather than the database itself." [INFO] [stdout] 17 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` 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_extract` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | / create_exception!( [INFO] [stdout] 19 | | limbo, [INFO] [stdout] 20 | | DatabaseError, [INFO] [stdout] 21 | | Error, [INFO] [stdout] 22 | | "Raised for errors that are related to the database." [INFO] [stdout] 23 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | / create_exception!( [INFO] [stdout] 19 | | limbo, [INFO] [stdout] 20 | | DatabaseError, [INFO] [stdout] 21 | | Error, [INFO] [stdout] 22 | | "Raised for errors that are related to the database." [INFO] [stdout] 23 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | / create_exception!( [INFO] [stdout] 19 | | limbo, [INFO] [stdout] 20 | | DatabaseError, [INFO] [stdout] 21 | | Error, [INFO] [stdout] 22 | | "Raised for errors that are related to the database." [INFO] [stdout] 23 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | / create_exception!( [INFO] [stdout] 19 | | limbo, [INFO] [stdout] 20 | | DatabaseError, [INFO] [stdout] 21 | | Error, [INFO] [stdout] 22 | | "Raised for errors that are related to the database." [INFO] [stdout] 23 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | / create_exception!( [INFO] [stdout] 19 | | limbo, [INFO] [stdout] 20 | | DatabaseError, [INFO] [stdout] 21 | | Error, [INFO] [stdout] 22 | | "Raised for errors that are related to the database." [INFO] [stdout] 23 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | / create_exception!( [INFO] [stdout] 19 | | limbo, [INFO] [stdout] 20 | | DatabaseError, [INFO] [stdout] 21 | | Error, [INFO] [stdout] 22 | | "Raised for errors that are related to the database." [INFO] [stdout] 23 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | / create_exception!( [INFO] [stdout] 19 | | limbo, [INFO] [stdout] 20 | | DatabaseError, [INFO] [stdout] 21 | | Error, [INFO] [stdout] 22 | | "Raised for errors that are related to the database." [INFO] [stdout] 23 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | / create_exception!( [INFO] [stdout] 19 | | limbo, [INFO] [stdout] 20 | | DatabaseError, [INFO] [stdout] 21 | | Error, [INFO] [stdout] 22 | | "Raised for errors that are related to the database." [INFO] [stdout] 23 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | / create_exception!( [INFO] [stdout] 19 | | limbo, [INFO] [stdout] 20 | | DatabaseError, [INFO] [stdout] 21 | | Error, [INFO] [stdout] 22 | | "Raised for errors that are related to the database." [INFO] [stdout] 23 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:18:1 [INFO] [stdout] | [INFO] [stdout] 18 | / create_exception!( [INFO] [stdout] 19 | | limbo, [INFO] [stdout] 20 | | DatabaseError, [INFO] [stdout] 21 | | Error, [INFO] [stdout] 22 | | "Raised for errors that are related to the database." [INFO] [stdout] 23 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` 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_extract` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:25:1 [INFO] [stdout] | [INFO] [stdout] 25 | create_exception!(limbo, DataError, DatabaseError, "Raised for errors due to problems with the processed data like division by zero, numeric value out of range, etc.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:25:1 [INFO] [stdout] | [INFO] [stdout] 25 | create_exception!(limbo, DataError, DatabaseError, "Raised for errors due to problems with the processed data like division by zero, numeric value out of range, etc.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:25:1 [INFO] [stdout] | [INFO] [stdout] 25 | create_exception!(limbo, DataError, DatabaseError, "Raised for errors due to problems with the processed data like division by zero, numeric value out of range, etc.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:25:1 [INFO] [stdout] | [INFO] [stdout] 25 | create_exception!(limbo, DataError, DatabaseError, "Raised for errors due to problems with the processed data like division by zero, numeric value out of range, etc.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:25:1 [INFO] [stdout] | [INFO] [stdout] 25 | create_exception!(limbo, DataError, DatabaseError, "Raised for errors due to problems with the processed data like division by zero, numeric value out of range, etc.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:25:1 [INFO] [stdout] | [INFO] [stdout] 25 | create_exception!(limbo, DataError, DatabaseError, "Raised for errors due to problems with the processed data like division by zero, numeric value out of range, etc.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:25:1 [INFO] [stdout] | [INFO] [stdout] 25 | create_exception!(limbo, DataError, DatabaseError, "Raised for errors due to problems with the processed data like division by zero, numeric value out of range, etc.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:25:1 [INFO] [stdout] | [INFO] [stdout] 25 | create_exception!(limbo, DataError, DatabaseError, "Raised for errors due to problems with the processed data like division by zero, numeric value out of range, etc.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:25:1 [INFO] [stdout] | [INFO] [stdout] 25 | create_exception!(limbo, DataError, DatabaseError, "Raised for errors due to problems with the processed data like division by zero, numeric value out of range, etc.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:25:1 [INFO] [stdout] | [INFO] [stdout] 25 | create_exception!(limbo, DataError, DatabaseError, "Raised for errors due to problems with the processed data like division by zero, numeric value out of range, etc.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` 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_extract` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:26:1 [INFO] [stdout] | [INFO] [stdout] 26 | create_exception!(limbo, OperationalError, DatabaseError, "Raised for errors related to the database’s operation, not necessarily under the programmer's control.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:26:1 [INFO] [stdout] | [INFO] [stdout] 26 | create_exception!(limbo, OperationalError, DatabaseError, "Raised for errors related to the database’s operation, not necessarily under the programmer's control.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:26:1 [INFO] [stdout] | [INFO] [stdout] 26 | create_exception!(limbo, OperationalError, DatabaseError, "Raised for errors related to the database’s operation, not necessarily under the programmer's control.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:26:1 [INFO] [stdout] | [INFO] [stdout] 26 | create_exception!(limbo, OperationalError, DatabaseError, "Raised for errors related to the database’s operation, not necessarily under the programmer's control.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:26:1 [INFO] [stdout] | [INFO] [stdout] 26 | create_exception!(limbo, OperationalError, DatabaseError, "Raised for errors related to the database’s operation, not necessarily under the programmer's control.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:26:1 [INFO] [stdout] | [INFO] [stdout] 26 | create_exception!(limbo, OperationalError, DatabaseError, "Raised for errors related to the database’s operation, not necessarily under the programmer's control.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:26:1 [INFO] [stdout] | [INFO] [stdout] 26 | create_exception!(limbo, OperationalError, DatabaseError, "Raised for errors related to the database’s operation, not necessarily under the programmer's control.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:26:1 [INFO] [stdout] | [INFO] [stdout] 26 | create_exception!(limbo, OperationalError, DatabaseError, "Raised for errors related to the database’s operation, not necessarily under the programmer's control.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:26:1 [INFO] [stdout] | [INFO] [stdout] 26 | create_exception!(limbo, OperationalError, DatabaseError, "Raised for errors related to the database’s operation, not necessarily under the programmer's control.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:26:1 [INFO] [stdout] | [INFO] [stdout] 26 | create_exception!(limbo, OperationalError, DatabaseError, "Raised for errors related to the database’s operation, not necessarily under the programmer's control.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` 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_extract` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | create_exception!(limbo, IntegrityError, DatabaseError, "Raised when the relational integrity of the database is affected, e.g., a foreign key check fails.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | create_exception!(limbo, IntegrityError, DatabaseError, "Raised when the relational integrity of the database is affected, e.g., a foreign key check fails.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | create_exception!(limbo, IntegrityError, DatabaseError, "Raised when the relational integrity of the database is affected, e.g., a foreign key check fails.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | create_exception!(limbo, IntegrityError, DatabaseError, "Raised when the relational integrity of the database is affected, e.g., a foreign key check fails.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | create_exception!(limbo, IntegrityError, DatabaseError, "Raised when the relational integrity of the database is affected, e.g., a foreign key check fails.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | create_exception!(limbo, IntegrityError, DatabaseError, "Raised when the relational integrity of the database is affected, e.g., a foreign key check fails.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | create_exception!(limbo, IntegrityError, DatabaseError, "Raised when the relational integrity of the database is affected, e.g., a foreign key check fails.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | create_exception!(limbo, IntegrityError, DatabaseError, "Raised when the relational integrity of the database is affected, e.g., a foreign key check fails.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | create_exception!(limbo, IntegrityError, DatabaseError, "Raised when the relational integrity of the database is affected, e.g., a foreign key check fails.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:27:1 [INFO] [stdout] | [INFO] [stdout] 27 | create_exception!(limbo, IntegrityError, DatabaseError, "Raised when the relational integrity of the database is affected, e.g., a foreign key check fails.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` 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_extract` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | create_exception!(limbo, InternalError, DatabaseError, "Raised when the database encounters an internal error, e.g., cursor is not valid anymore, transaction out of sync.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | create_exception!(limbo, InternalError, DatabaseError, "Raised when the database encounters an internal error, e.g., cursor is not valid anymore, transaction out of sync.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | create_exception!(limbo, InternalError, DatabaseError, "Raised when the database encounters an internal error, e.g., cursor is not valid anymore, transaction out of sync.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | create_exception!(limbo, InternalError, DatabaseError, "Raised when the database encounters an internal error, e.g., cursor is not valid anymore, transaction out of sync.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | create_exception!(limbo, InternalError, DatabaseError, "Raised when the database encounters an internal error, e.g., cursor is not valid anymore, transaction out of sync.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | create_exception!(limbo, InternalError, DatabaseError, "Raised when the database encounters an internal error, e.g., cursor is not valid anymore, transaction out of sync.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | create_exception!(limbo, InternalError, DatabaseError, "Raised when the database encounters an internal error, e.g., cursor is not valid anymore, transaction out of sync.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | create_exception!(limbo, InternalError, DatabaseError, "Raised when the database encounters an internal error, e.g., cursor is not valid anymore, transaction out of sync.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | create_exception!(limbo, InternalError, DatabaseError, "Raised when the database encounters an internal error, e.g., cursor is not valid anymore, transaction out of sync.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:28:1 [INFO] [stdout] | [INFO] [stdout] 28 | create_exception!(limbo, InternalError, DatabaseError, "Raised when the database encounters an internal error, e.g., cursor is not valid anymore, transaction out of sync.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` 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_extract` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:29:1 [INFO] [stdout] | [INFO] [stdout] 29 | create_exception!(limbo, ProgrammingError, DatabaseError, "Raised for programming errors, e.g., table not found, syntax error in SQL, wrong number of parameters specified.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:29:1 [INFO] [stdout] | [INFO] [stdout] 29 | create_exception!(limbo, ProgrammingError, DatabaseError, "Raised for programming errors, e.g., table not found, syntax error in SQL, wrong number of parameters specified.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:29:1 [INFO] [stdout] | [INFO] [stdout] 29 | create_exception!(limbo, ProgrammingError, DatabaseError, "Raised for programming errors, e.g., table not found, syntax error in SQL, wrong number of parameters specified.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:29:1 [INFO] [stdout] | [INFO] [stdout] 29 | create_exception!(limbo, ProgrammingError, DatabaseError, "Raised for programming errors, e.g., table not found, syntax error in SQL, wrong number of parameters specified.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:29:1 [INFO] [stdout] | [INFO] [stdout] 29 | create_exception!(limbo, ProgrammingError, DatabaseError, "Raised for programming errors, e.g., table not found, syntax error in SQL, wrong number of parameters specified.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:29:1 [INFO] [stdout] | [INFO] [stdout] 29 | create_exception!(limbo, ProgrammingError, DatabaseError, "Raised for programming errors, e.g., table not found, syntax error in SQL, wrong number of parameters specified.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:29:1 [INFO] [stdout] | [INFO] [stdout] 29 | create_exception!(limbo, ProgrammingError, DatabaseError, "Raised for programming errors, e.g., table not found, syntax error in SQL, wrong number of parameters specified.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:29:1 [INFO] [stdout] | [INFO] [stdout] 29 | create_exception!(limbo, ProgrammingError, DatabaseError, "Raised for programming errors, e.g., table not found, syntax error in SQL, wrong number of parameters specified.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:29:1 [INFO] [stdout] | [INFO] [stdout] 29 | create_exception!(limbo, ProgrammingError, DatabaseError, "Raised for programming errors, e.g., table not found, syntax error in SQL, wrong number of parameters specified.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:29:1 [INFO] [stdout] | [INFO] [stdout] 29 | create_exception!(limbo, ProgrammingError, DatabaseError, "Raised for programming errors, e.g., table not found, syntax error in SQL, wrong number of parameters specified.... [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` 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_extract` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:30:1 [INFO] [stdout] | [INFO] [stdout] 30 | / create_exception!( [INFO] [stdout] 31 | | limbo, [INFO] [stdout] 32 | | NotSupportedError, [INFO] [stdout] 33 | | DatabaseError, [INFO] [stdout] 34 | | "Raised when a method or database API is used which is not supported by the database." [INFO] [stdout] 35 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:30:1 [INFO] [stdout] | [INFO] [stdout] 30 | / create_exception!( [INFO] [stdout] 31 | | limbo, [INFO] [stdout] 32 | | NotSupportedError, [INFO] [stdout] 33 | | DatabaseError, [INFO] [stdout] 34 | | "Raised when a method or database API is used which is not supported by the database." [INFO] [stdout] 35 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::impl_exception_boilerplate` 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::impl_exception_boilerplate` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:30:1 [INFO] [stdout] | [INFO] [stdout] 30 | / create_exception!( [INFO] [stdout] 31 | | limbo, [INFO] [stdout] 32 | | NotSupportedError, [INFO] [stdout] 33 | | DatabaseError, [INFO] [stdout] 34 | | "Raised when a method or database API is used which is not supported by the database." [INFO] [stdout] 35 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:30:1 [INFO] [stdout] | [INFO] [stdout] 30 | / create_exception!( [INFO] [stdout] 31 | | limbo, [INFO] [stdout] 32 | | NotSupportedError, [INFO] [stdout] 33 | | DatabaseError, [INFO] [stdout] 34 | | "Raised when a method or database API is used which is not supported by the database." [INFO] [stdout] 35 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:30:1 [INFO] [stdout] | [INFO] [stdout] 30 | / create_exception!( [INFO] [stdout] 31 | | limbo, [INFO] [stdout] 32 | | NotSupportedError, [INFO] [stdout] 33 | | DatabaseError, [INFO] [stdout] 34 | | "Raised when a method or database API is used which is not supported by the database." [INFO] [stdout] 35 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_named` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_named` 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_named` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:30:1 [INFO] [stdout] | [INFO] [stdout] 30 | / create_exception!( [INFO] [stdout] 31 | | limbo, [INFO] [stdout] 32 | | NotSupportedError, [INFO] [stdout] 33 | | DatabaseError, [INFO] [stdout] 34 | | "Raised when a method or database API is used which is not supported by the database." [INFO] [stdout] 35 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:30:1 [INFO] [stdout] | [INFO] [stdout] 30 | / create_exception!( [INFO] [stdout] 31 | | limbo, [INFO] [stdout] 32 | | NotSupportedError, [INFO] [stdout] 33 | | DatabaseError, [INFO] [stdout] 34 | | "Raised when a method or database API is used which is not supported by the database." [INFO] [stdout] 35 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:30:1 [INFO] [stdout] | [INFO] [stdout] 30 | / create_exception!( [INFO] [stdout] 31 | | limbo, [INFO] [stdout] 32 | | NotSupportedError, [INFO] [stdout] 33 | | DatabaseError, [INFO] [stdout] 34 | | "Raised when a method or database API is used which is not supported by the database." [INFO] [stdout] 35 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:30:1 [INFO] [stdout] | [INFO] [stdout] 30 | / create_exception!( [INFO] [stdout] 31 | | limbo, [INFO] [stdout] 32 | | NotSupportedError, [INFO] [stdout] 33 | | DatabaseError, [INFO] [stdout] 34 | | "Raised when a method or database API is used which is not supported by the database." [INFO] [stdout] 35 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_base` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_base` 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_base` 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 value: `gil-refs` [INFO] [stdout] --> bindings/python/src/errors.rs:30:1 [INFO] [stdout] | [INFO] [stdout] 30 | / create_exception!( [INFO] [stdout] 31 | | limbo, [INFO] [stdout] 32 | | NotSupportedError, [INFO] [stdout] 33 | | DatabaseError, [INFO] [stdout] 34 | | "Raised when a method or database API is used which is not supported by the database." [INFO] [stdout] 35 | | ); [INFO] [stdout] | |_^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `extension-module` [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_extract` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `$crate::pyobject_native_type_extract` 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_extract` 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] [stderr] Finished `test` profile [unoptimized + debuginfo] target(s) in 30.91s [INFO] running `Command { std: "docker" "inspect" "3427b476efe0a8329cedc2197ff0a29b4e94d30628c6276936e4633c9f933b34", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "3427b476efe0a8329cedc2197ff0a29b4e94d30628c6276936e4633c9f933b34", kill_on_drop: false }` [INFO] [stdout] 3427b476efe0a8329cedc2197ff0a29b4e94d30628c6276936e4633c9f933b34 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-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 -Zrandomize-layout" "-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:819108c5571ea2e421544af4d832f968d213c87fbe3707a016657f43d2f853bc" "/opt/rustwide/cargo-home/bin/cargo" "+nightly-2025-01-18" "test" "--frozen", kill_on_drop: false }` [INFO] [stdout] a045e73409dabebec367a1acf8473a3ac6c9695e6a9cdf84e83a1aa2d0cfad25 [INFO] running `Command { std: "docker" "start" "-a" "a045e73409dabebec367a1acf8473a3ac6c9695e6a9cdf84e83a1aa2d0cfad25", kill_on_drop: false }` [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:4:1 [INFO] [stderr] | [INFO] [stderr] 4 | / create_exception!( [INFO] [stderr] 5 | | limbo, [INFO] [stderr] 6 | | Warning, [INFO] [stderr] 7 | | PyException, [INFO] [stderr] 8 | | "Exception raised for important warnings like data truncations while inserting." [INFO] [stderr] 9 | | ); [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stderr] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:4:1 [INFO] [stderr] | [INFO] [stderr] 4 | / create_exception!( [INFO] [stderr] 5 | | limbo, [INFO] [stderr] 6 | | Warning, [INFO] [stderr] 7 | | PyException, [INFO] [stderr] 8 | | "Exception raised for important warnings like data truncations while inserting." [INFO] [stderr] 9 | | ); [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:4:1 [INFO] [stderr] | [INFO] [stderr] 4 | / create_exception!( [INFO] [stderr] 5 | | limbo, [INFO] [stderr] 6 | | Warning, [INFO] [stderr] 7 | | PyException, [INFO] [stderr] 8 | | "Exception raised for important warnings like data truncations while inserting." [INFO] [stderr] 9 | | ); [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:4:1 [INFO] [stderr] | [INFO] [stderr] 4 | / create_exception!( [INFO] [stderr] 5 | | limbo, [INFO] [stderr] 6 | | Warning, [INFO] [stderr] 7 | | PyException, [INFO] [stderr] 8 | | "Exception raised for important warnings like data truncations while inserting." [INFO] [stderr] 9 | | ); [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:4:1 [INFO] [stderr] | [INFO] [stderr] 4 | / create_exception!( [INFO] [stderr] 5 | | limbo, [INFO] [stderr] 6 | | Warning, [INFO] [stderr] 7 | | PyException, [INFO] [stderr] 8 | | "Exception raised for important warnings like data truncations while inserting." [INFO] [stderr] 9 | | ); [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::pyobject_native_type_extract` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_extract` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_extract` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:10:1 [INFO] [stderr] | [INFO] [stderr] 10 | create_exception!(limbo, Error, PyException, "Base class for all other error exceptions. Catch all database-related errors using this class.... [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:10:1 [INFO] [stderr] | [INFO] [stderr] 10 | create_exception!(limbo, Error, PyException, "Base class for all other error exceptions. Catch all database-related errors using this class.... [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:10:1 [INFO] [stderr] | [INFO] [stderr] 10 | create_exception!(limbo, Error, PyException, "Base class for all other error exceptions. Catch all database-related errors using this class.... [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:10:1 [INFO] [stderr] | [INFO] [stderr] 10 | create_exception!(limbo, Error, PyException, "Base class for all other error exceptions. Catch all database-related errors using this class.... [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::pyobject_native_type_extract` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_extract` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_extract` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:12:1 [INFO] [stderr] | [INFO] [stderr] 12 | / create_exception!( [INFO] [stderr] 13 | | limbo, [INFO] [stderr] 14 | | InterfaceError, [INFO] [stderr] 15 | | Error, [INFO] [stderr] 16 | | "Raised for errors related to the database interface rather than the database itself." [INFO] [stderr] 17 | | ); [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:12:1 [INFO] [stderr] | [INFO] [stderr] 12 | / create_exception!( [INFO] [stderr] 13 | | limbo, [INFO] [stderr] 14 | | InterfaceError, [INFO] [stderr] 15 | | Error, [INFO] [stderr] 16 | | "Raised for errors related to the database interface rather than the database itself." [INFO] [stderr] 17 | | ); [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:12:1 [INFO] [stderr] | [INFO] [stderr] 12 | / create_exception!( [INFO] [stderr] 13 | | limbo, [INFO] [stderr] 14 | | InterfaceError, [INFO] [stderr] 15 | | Error, [INFO] [stderr] 16 | | "Raised for errors related to the database interface rather than the database itself." [INFO] [stderr] 17 | | ); [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:12:1 [INFO] [stderr] | [INFO] [stderr] 12 | / create_exception!( [INFO] [stderr] 13 | | limbo, [INFO] [stderr] 14 | | InterfaceError, [INFO] [stderr] 15 | | Error, [INFO] [stderr] 16 | | "Raised for errors related to the database interface rather than the database itself." [INFO] [stderr] 17 | | ); [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::pyobject_native_type_extract` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_extract` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_extract` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:18:1 [INFO] [stderr] | [INFO] [stderr] 18 | / create_exception!( [INFO] [stderr] 19 | | limbo, [INFO] [stderr] 20 | | DatabaseError, [INFO] [stderr] 21 | | Error, [INFO] [stderr] 22 | | "Raised for errors that are related to the database." [INFO] [stderr] 23 | | ); [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:18:1 [INFO] [stderr] | [INFO] [stderr] 18 | / create_exception!( [INFO] [stderr] 19 | | limbo, [INFO] [stderr] 20 | | DatabaseError, [INFO] [stderr] 21 | | Error, [INFO] [stderr] 22 | | "Raised for errors that are related to the database." [INFO] [stderr] 23 | | ); [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:18:1 [INFO] [stderr] | [INFO] [stderr] 18 | / create_exception!( [INFO] [stderr] 19 | | limbo, [INFO] [stderr] 20 | | DatabaseError, [INFO] [stderr] 21 | | Error, [INFO] [stderr] 22 | | "Raised for errors that are related to the database." [INFO] [stderr] 23 | | ); [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:18:1 [INFO] [stderr] | [INFO] [stderr] 18 | / create_exception!( [INFO] [stderr] 19 | | limbo, [INFO] [stderr] 20 | | DatabaseError, [INFO] [stderr] 21 | | Error, [INFO] [stderr] 22 | | "Raised for errors that are related to the database." [INFO] [stderr] 23 | | ); [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::pyobject_native_type_extract` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_extract` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_extract` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:25:1 [INFO] [stderr] | [INFO] [stderr] 25 | create_exception!(limbo, DataError, DatabaseError, "Raised for errors due to problems with the processed data like division by zero, numeric value out of range, etc.... [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:25:1 [INFO] [stderr] | [INFO] [stderr] 25 | create_exception!(limbo, DataError, DatabaseError, "Raised for errors due to problems with the processed data like division by zero, numeric value out of range, etc.... [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:25:1 [INFO] [stderr] | [INFO] [stderr] 25 | create_exception!(limbo, DataError, DatabaseError, "Raised for errors due to problems with the processed data like division by zero, numeric value out of range, etc.... [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:25:1 [INFO] [stderr] | [INFO] [stderr] 25 | create_exception!(limbo, DataError, DatabaseError, "Raised for errors due to problems with the processed data like division by zero, numeric value out of range, etc.... [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::pyobject_native_type_extract` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_extract` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_extract` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:26:1 [INFO] [stderr] | [INFO] [stderr] 26 | create_exception!(limbo, OperationalError, DatabaseError, "Raised for errors related to the database’s operation, not necessarily under the programmer's control.... [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:26:1 [INFO] [stderr] | [INFO] [stderr] 26 | create_exception!(limbo, OperationalError, DatabaseError, "Raised for errors related to the database’s operation, not necessarily under the programmer's control.... [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:26:1 [INFO] [stderr] | [INFO] [stderr] 26 | create_exception!(limbo, OperationalError, DatabaseError, "Raised for errors related to the database’s operation, not necessarily under the programmer's control.... [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:26:1 [INFO] [stderr] | [INFO] [stderr] 26 | create_exception!(limbo, OperationalError, DatabaseError, "Raised for errors related to the database’s operation, not necessarily under the programmer's control.... [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::pyobject_native_type_extract` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_extract` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_extract` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:27:1 [INFO] [stderr] | [INFO] [stderr] 27 | create_exception!(limbo, IntegrityError, DatabaseError, "Raised when the relational integrity of the database is affected, e.g., a foreign key check fails.... [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:27:1 [INFO] [stderr] | [INFO] [stderr] 27 | create_exception!(limbo, IntegrityError, DatabaseError, "Raised when the relational integrity of the database is affected, e.g., a foreign key check fails.... [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:27:1 [INFO] [stderr] | [INFO] [stderr] 27 | create_exception!(limbo, IntegrityError, DatabaseError, "Raised when the relational integrity of the database is affected, e.g., a foreign key check fails.... [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:27:1 [INFO] [stderr] | [INFO] [stderr] 27 | create_exception!(limbo, IntegrityError, DatabaseError, "Raised when the relational integrity of the database is affected, e.g., a foreign key check fails.... [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::pyobject_native_type_extract` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_extract` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_extract` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:28:1 [INFO] [stderr] | [INFO] [stderr] 28 | create_exception!(limbo, InternalError, DatabaseError, "Raised when the database encounters an internal error, e.g., cursor is not valid anymore, transaction out of sync.... [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:28:1 [INFO] [stderr] | [INFO] [stderr] 28 | create_exception!(limbo, InternalError, DatabaseError, "Raised when the database encounters an internal error, e.g., cursor is not valid anymore, transaction out of sync.... [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:28:1 [INFO] [stderr] | [INFO] [stderr] 28 | create_exception!(limbo, InternalError, DatabaseError, "Raised when the database encounters an internal error, e.g., cursor is not valid anymore, transaction out of sync.... [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:28:1 [INFO] [stderr] | [INFO] [stderr] 28 | create_exception!(limbo, InternalError, DatabaseError, "Raised when the database encounters an internal error, e.g., cursor is not valid anymore, transaction out of sync.... [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::pyobject_native_type_extract` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_extract` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_extract` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:29:1 [INFO] [stderr] | [INFO] [stderr] 29 | create_exception!(limbo, ProgrammingError, DatabaseError, "Raised for programming errors, e.g., table not found, syntax error in SQL, wrong number of parameters specified.... [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:29:1 [INFO] [stderr] | [INFO] [stderr] 29 | create_exception!(limbo, ProgrammingError, DatabaseError, "Raised for programming errors, e.g., table not found, syntax error in SQL, wrong number of parameters specified.... [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:29:1 [INFO] [stderr] | [INFO] [stderr] 29 | create_exception!(limbo, ProgrammingError, DatabaseError, "Raised for programming errors, e.g., table not found, syntax error in SQL, wrong number of parameters specified.... [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:29:1 [INFO] [stderr] | [INFO] [stderr] 29 | create_exception!(limbo, ProgrammingError, DatabaseError, "Raised for programming errors, e.g., table not found, syntax error in SQL, wrong number of parameters specified.... [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::pyobject_native_type_extract` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_extract` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_extract` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:30:1 [INFO] [stderr] | [INFO] [stderr] 30 | / create_exception!( [INFO] [stderr] 31 | | limbo, [INFO] [stderr] 32 | | NotSupportedError, [INFO] [stderr] 33 | | DatabaseError, [INFO] [stderr] 34 | | "Raised when a method or database API is used which is not supported by the database." [INFO] [stderr] 35 | | ); [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::impl_exception_boilerplate` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::impl_exception_boilerplate` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::impl_exception_boilerplate` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:30:1 [INFO] [stderr] | [INFO] [stderr] 30 | / create_exception!( [INFO] [stderr] 31 | | limbo, [INFO] [stderr] 32 | | NotSupportedError, [INFO] [stderr] 33 | | DatabaseError, [INFO] [stderr] 34 | | "Raised when a method or database API is used which is not supported by the database." [INFO] [stderr] 35 | | ); [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::pyobject_native_type_named` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_named` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_named` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:30:1 [INFO] [stderr] | [INFO] [stderr] 30 | / create_exception!( [INFO] [stderr] 31 | | limbo, [INFO] [stderr] 32 | | NotSupportedError, [INFO] [stderr] 33 | | DatabaseError, [INFO] [stderr] 34 | | "Raised when a method or database API is used which is not supported by the database." [INFO] [stderr] 35 | | ); [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::pyobject_native_type_base` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_base` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_base` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `gil-refs` [INFO] [stderr] --> bindings/python/src/errors.rs:30:1 [INFO] [stderr] | [INFO] [stderr] 30 | / create_exception!( [INFO] [stderr] 31 | | limbo, [INFO] [stderr] 32 | | NotSupportedError, [INFO] [stderr] 33 | | DatabaseError, [INFO] [stderr] 34 | | "Raised when a method or database API is used which is not supported by the database." [INFO] [stderr] 35 | | ); [INFO] [stderr] | |_^ [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `extension-module` [INFO] [stderr] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `$crate::pyobject_native_type_extract` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the macro `$crate::pyobject_native_type_extract` may come from an old version of the `pyo3` crate, try updating your dependency with `cargo update -p pyo3` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the macro `$crate::pyobject_native_type_extract` which comes from the expansion of the macro `create_exception` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: `py-limbo` (lib test) generated 100 warnings (59 duplicates) [INFO] [stderr] Finished `test` profile [unoptimized + debuginfo] target(s) in 0.38s [INFO] [stderr] Running unittests src/lib.rs (/opt/rustwide/target/debug/deps/test-cf9eb744441105a8) [INFO] [stdout] [INFO] [stdout] running 3 tests [INFO] [stdout] test tests::test_sequential_overflow_page ... ignored [INFO] [stdout] test tests::test_sequential_write ... ignored [INFO] [stdout] test tests::test_simple_overflow_page ... ignored [INFO] [stdout] [INFO] [stdout] test result: ok. 0 passed; 0 failed; 3 ignored; 0 measured; 0 filtered out; finished in 0.00s [INFO] [stdout] [INFO] [stderr] Running unittests main.rs (/opt/rustwide/target/debug/deps/limbo-8c3a707378879920) [INFO] [stdout] [INFO] [stdout] running 0 tests [INFO] [stdout] [INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s [INFO] [stdout] [INFO] [stderr] Running unittests lib.rs (/opt/rustwide/target/debug/deps/limbo_wasm-4c6bf2cbf30187be) [INFO] [stdout] [INFO] [stdout] running 0 tests [INFO] [stdout] [INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s [INFO] [stdout] [INFO] [stderr] Running unittests lib.rs (/opt/rustwide/target/debug/deps/limbo_core-bd06c3fafccf4cc8) [INFO] [stdout] [INFO] [stdout] running 136 tests [INFO] [stdout] test json::tests::test_get_json_blob_invalid_jsonb ... ok [INFO] [stdout] test json::tests::test_get_json_blob_valid_jsonb ... ok [INFO] [stdout] test json::tests::test_get_json_non_text ... ok [INFO] [stdout] test json::tests::test_get_json_invalid_json5 ... ok [INFO] [stdout] test json::tests::test_get_json_valid_json5 ... ok [INFO] [stdout] test json::tests::test_get_json_invalid_jsonb ... ok [INFO] [stdout] test json::tests::test_get_json_valid_json5_double_single_quotes ... ok [INFO] [stdout] test json::tests::test_get_json_valid_json5_infinity ... ok [INFO] [stdout] test json::tests::test_get_json_valid_json5_negative_infinity ... ok [INFO] [stdout] test json::tests::test_get_json_valid_json5_nan ... ok [INFO] [stdout] test json::tests::test_get_json_valid_jsonb ... ok [INFO] [stdout] test schema::tests::test_column_is_rowid_alias_inline_composite_primary_key ... ok [INFO] [stdout] test schema::tests::test_column_is_rowid_alias_separate_composite_primary_key_definition ... ok [INFO] [stdout] test schema::tests::test_column_is_rowid_alias_single_integer ... ok [INFO] [stdout] test schema::tests::test_column_is_rowid_alias_single_integer_separate_primary_key_definition ... ok [INFO] [stdout] test schema::tests::test_column_is_rowid_alias_single_integer_without_rowid ... ok [INFO] [stdout] test schema::tests::test_column_is_rowid_alias_single_integer_separate_primary_key_definition_without_rowid ... ok [INFO] [stdout] test schema::tests::test_column_is_rowid_alias_single_text ... ok [INFO] [stdout] test schema::tests::test_has_rowid_false ... ok [INFO] [stdout] test schema::tests::test_has_rowid_true ... ok [INFO] [stdout] test schema::tests::test_primary_key_inline_multiple ... ok [INFO] [stdout] test schema::tests::test_primary_key_separate_single ... ok [INFO] [stdout] test schema::tests::test_primary_key_inline_single ... ok [INFO] [stdout] test schema::tests::test_primary_key_separate_single_doubly_quoted ... ok [INFO] [stdout] test schema::tests::test_primary_key_separate_single_quoted ... ok [INFO] [stdout] test schema::tests::test_primary_key_separate_multiple ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::read_varint_test::case_2 ... ok [INFO] [stdout] test schema::tests::test_sqlite_schema ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::read_varint_test::case_4 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::read_varint_test::case_1 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::read_varint_test::case_3 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::read_varint_test::case_5 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::read_varint_test::case_6 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::read_varint_test::case_7 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::read_varint_test::case_8 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::read_varint_test::case_9 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_read_invalid_serial_type ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_read_invalid_value::case_1 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_read_invalid_value::case_3 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_read_invalid_value::case_2 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_read_invalid_value::case_4 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_read_invalid_value::case_5 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_read_invalid_value::case_6 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_read_invalid_value::case_7 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_read_invalid_value::case_8 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_read_invalid_value::case_9 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_read_invalid_varint ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_read_serial_type::case_01 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_read_serial_type::case_02 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_read_serial_type::case_03 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_read_serial_type::case_04 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_read_serial_type::case_05 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_read_serial_type::case_06 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_read_serial_type::case_07 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_read_serial_type::case_08 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_read_serial_type::case_10 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_read_serial_type::case_11 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_read_serial_type::case_09 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_read_serial_type::case_12 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_read_serial_type::case_14 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_read_serial_type::case_13 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_read_value::case_01 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_read_value::case_02 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_read_value::case_03 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_read_value::case_04 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_read_value::case_05 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_read_value::case_06 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_read_value::case_07 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_read_value::case_08 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_read_value::case_09 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_read_value::case_10 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_read_value::case_11 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_write_varint::case_01 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_read_value::case_12 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_write_varint::case_02 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_write_varint::case_03 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_write_varint::case_04 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_write_varint::case_05 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_write_varint::case_06 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_write_varint::case_07 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_write_varint::case_08 ... ok [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_write_varint::case_09 ... ok [INFO] [stdout] test vdbe::datetime::tests::test_apply_modifier_date_time_offset ... ignored [INFO] [stdout] test storage::sqlite3_ondisk::tests::test_write_varint::case_10 ... ok [INFO] [stdout] test vdbe::datetime::tests::test_apply_modifier_days ... ok [INFO] [stdout] test vdbe::datetime::tests::test_apply_modifier_hours ... ok [INFO] [stdout] test vdbe::datetime::tests::test_apply_modifier_minutes ... ok [INFO] [stdout] test vdbe::datetime::tests::test_apply_modifier_start_of_year ... ok [INFO] [stdout] test vdbe::datetime::tests::test_apply_modifier_seconds ... ok [INFO] [stdout] test vdbe::datetime::tests::test_apply_modifier_start_of_day ... ok [INFO] [stdout] test vdbe::datetime::tests::test_apply_modifier_time_offset ... ok [INFO] [stdout] test vdbe::datetime::tests::test_parse_date_offset ... ok [INFO] [stdout] test vdbe::datetime::tests::test_parse_date_time_offset ... ok [INFO] [stdout] test vdbe::datetime::tests::test_parse_days ... ok [INFO] [stdout] test vdbe::datetime::tests::test_parse_hours ... ok [INFO] [stdout] test vdbe::datetime::tests::test_parse_invalid_modifier ... ok [INFO] [stdout] test vdbe::datetime::tests::test_parse_months ... ok [INFO] [stdout] test vdbe::datetime::tests::test_parse_minutes ... ok [INFO] [stdout] test vdbe::datetime::tests::test_parse_other_modifiers ... ok [INFO] [stdout] test vdbe::datetime::tests::test_parse_seconds ... ok [INFO] [stdout] test vdbe::datetime::tests::test_parse_start_of ... ok [INFO] [stdout] test vdbe::datetime::tests::test_parse_time_offset ... ok [INFO] [stdout] test vdbe::datetime::tests::test_parse_weekday ... ok [INFO] [stdout] test vdbe::tests::test_abs ... ok [INFO] [stdout] test vdbe::tests::test_char ... ok [INFO] [stdout] test vdbe::tests::test_exec_if ... ok [INFO] [stdout] test vdbe::datetime::tests::test_parse_years ... ok [INFO] [stdout] test vdbe::tests::test_exec_randomblob ... ok [INFO] [stdout] test vdbe::tests::test_exec_instr ... ok [INFO] [stdout] test vdbe::tests::test_exec_round ... ok [INFO] [stdout] test vdbe::tests::test_exec_zeroblob ... ok [INFO] [stdout] test vdbe::tests::test_exec_sign ... ok [INFO] [stdout] test vdbe::tests::test_execute_sqlite_version ... ok [INFO] [stdout] test vdbe::datetime::tests::test_invalid_get_date_from_time_value ... ok [INFO] [stdout] test vdbe::datetime::tests::test_invalid_get_time_from_datetime_value ... ok [INFO] [stdout] test vdbe::tests::test_length ... ok [INFO] [stdout] test vdbe::tests::test_hex ... ok [INFO] [stdout] test vdbe::tests::test_ltrim ... ok [INFO] [stdout] test vdbe::tests::test_min_max ... ok [INFO] [stdout] test vdbe::tests::test_nullif ... ok [INFO] [stdout] test vdbe::tests::test_lower_case ... ok [INFO] [stdout] test vdbe::tests::test_random ... ok [INFO] [stdout] test vdbe::tests::test_quote ... ok [INFO] [stdout] test vdbe::tests::test_get_new_rowid ... ok [INFO] [stdout] test vdbe::tests::test_rtrim ... ok [INFO] [stdout] test vdbe::tests::test_substring ... ok [INFO] [stdout] test vdbe::tests::test_typeof ... ok [INFO] [stdout] test vdbe::tests::test_unhex ... ok [INFO] [stdout] test vdbe::tests::test_unicode ... ok [INFO] [stdout] test vdbe::tests::test_upper_case ... ok [INFO] [stdout] test vdbe::tests::test_trim ... ok [INFO] [stdout] test vdbe::datetime::tests::test_valid_get_time_from_datetime_value ... ok [INFO] [stdout] test vdbe::datetime::tests::test_valid_get_date_from_time_value ... ok [INFO] [stdout] test vdbe::tests::test_like_no_cache ... ok [INFO] [stdout] test vdbe::tests::test_like_with_cache ... ok [INFO] [stdout] test io::linux::tests::test_multiple_processes_cannot_open_file ... FAILED [INFO] [stdout] [INFO] [stdout] failures: [INFO] [stdout] [INFO] [stdout] ---- io::linux::tests::test_multiple_processes_cannot_open_file stdout ---- [INFO] [stdout] [INFO] [stdout] thread 'io::linux::tests::test_multiple_processes_cannot_open_file' panicked at core/io/common.rs:14:31: [INFO] [stdout] Failed to create IO: IOError(Os { code: 1, kind: PermissionDenied, message: "Operation not permitted" }) [INFO] [stdout] stack backtrace: [INFO] [stdout] 0: 0x6065acf5ce0a - std::backtrace_rs::backtrace::libunwind::trace::hb059275cfc8d6126 [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/../../backtrace/src/backtrace/libunwind.rs:116:5 [INFO] [stdout] 1: 0x6065acf5ce0a - std::backtrace_rs::backtrace::trace_unsynchronized::h2da071e4327ce3ee [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5 [INFO] [stdout] 2: 0x6065acf5ce0a - std::sys::backtrace::_print_fmt::h842a1474e6f8d23f [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/sys/backtrace.rs:66:9 [INFO] [stdout] 3: 0x6065acf5ce0a - ::fmt::h71a62eb3b9696b12 [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/sys/backtrace.rs:39:26 [INFO] [stdout] 4: 0x6065acf87e33 - core::fmt::rt::Argument::fmt::hdb6b616786b41dc1 [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/core/src/fmt/rt.rs:177:76 [INFO] [stdout] 5: 0x6065acf87e33 - core::fmt::write::h2cc1698af7e2d686 [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/core/src/fmt/mod.rs:1440:21 [INFO] [stdout] 6: 0x6065acf592f3 - std::io::Write::write_fmt::hab1b4cd059a79022 [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/io/mod.rs:1887:15 [INFO] [stdout] 7: 0x6065acf5cc52 - std::sys::backtrace::BacktraceLock::print::h147fe35b4ea13b08 [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/sys/backtrace.rs:42:9 [INFO] [stdout] 8: 0x6065acf5e07f - std::panicking::default_hook::{{closure}}::hbd44223dbdc0d208 [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/panicking.rs:298:22 [INFO] [stdout] 9: 0x6065acf5de98 - std::panicking::default_hook::h20f81eb0576efcec [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/panicking.rs:322:9 [INFO] [stdout] 10: 0x6065acb92cf3 - as core::ops::function::Fn>::call::hdb53814c496a4d34 [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/alloc/src/boxed.rs:2027:9 [INFO] [stdout] 11: 0x6065acb92cf3 - test::test_main::{{closure}}::hc0a4963c59427c24 [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/test/src/lib.rs:134:21 [INFO] [stdout] 12: 0x6065acf5eb73 - as core::ops::function::Fn>::call::h591b2225413a77e9 [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/alloc/src/boxed.rs:2027:9 [INFO] [stdout] 13: 0x6065acf5eb73 - std::panicking::rust_panic_with_hook::h625eea43051b2edc [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/panicking.rs:839:13 [INFO] [stdout] 14: 0x6065acf5e82a - std::panicking::begin_panic_handler::{{closure}}::h4f9159cfbc3f6bd3 [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/panicking.rs:704:13 [INFO] [stdout] 15: 0x6065acf5d309 - std::sys::backtrace::__rust_end_short_backtrace::h0390abce48353151 [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/sys/backtrace.rs:168:18 [INFO] [stdout] 16: 0x6065acf5e4bd - rust_begin_unwind [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/panicking.rs:695:5 [INFO] [stdout] 17: 0x6065acf86110 - core::panicking::panic_fmt::h9e7c637e9e5f29c9 [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/core/src/panicking.rs:75:14 [INFO] [stdout] 18: 0x6065acf86586 - core::result::unwrap_failed::h7979f09313fe1849 [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/core/src/result.rs:1704:5 [INFO] [stdout] 19: 0x6065acaabe09 - core::result::Result::expect::he742a643148e6601 [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/core/src/result.rs:1061:23 [INFO] [stdout] 20: 0x6065acadaf98 - limbo_core::io::common::tests::run_test_parent_process::h8f671abb4e0baa27 [INFO] [stdout] at /opt/rustwide/workdir/core/io/common.rs:14:19 [INFO] [stdout] 21: 0x6065acadb7b4 - limbo_core::io::common::tests::test_multiple_processes_cannot_open_file::hcf92dbe7f1af91a3 [INFO] [stdout] at /opt/rustwide/workdir/core/io/common.rs:51:9 [INFO] [stdout] 22: 0x6065acad704d - limbo_core::io::linux::tests::test_multiple_processes_cannot_open_file::h826bbffdc8ab3d76 [INFO] [stdout] at /opt/rustwide/workdir/core/io/linux.rs:274:9 [INFO] [stdout] 23: 0x6065acad7027 - limbo_core::io::linux::tests::test_multiple_processes_cannot_open_file::{{closure}}::h25a9bec965bbf777 [INFO] [stdout] at /opt/rustwide/workdir/core/io/linux.rs:273:50 [INFO] [stdout] 24: 0x6065acafa286 - core::ops::function::FnOnce::call_once::ha2281afeb3aac7af [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/core/src/ops/function.rs:250:5 [INFO] [stdout] 25: 0x6065acb9844b - core::ops::function::FnOnce::call_once::he27718dfdd183f43 [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/core/src/ops/function.rs:250:5 [INFO] [stdout] 26: 0x6065acb9844b - test::__rust_begin_short_backtrace::h4e84902998457a5d [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/test/src/lib.rs:632:18 [INFO] [stdout] 27: 0x6065acb97383 - test::run_test_in_process::{{closure}}::h7176fd18fc1feca0 [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/test/src/lib.rs:655:60 [INFO] [stdout] 28: 0x6065acb97383 - as core::ops::function::FnOnce<()>>::call_once::hf79cff2a624d8cf7 [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/core/src/panic/unwind_safe.rs:272:9 [INFO] [stdout] 29: 0x6065acb97383 - std::panicking::try::do_call::h3da0561d9ab99c25 [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/panicking.rs:587:40 [INFO] [stdout] 30: 0x6065acb97383 - std::panicking::try::h41c9fa508bc61df6 [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/panicking.rs:550:19 [INFO] [stdout] 31: 0x6065acb97383 - std::panic::catch_unwind::h6b3ff07bb5afad93 [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/panic.rs:358:14 [INFO] [stdout] 32: 0x6065acb97383 - test::run_test_in_process::hc7253dd11b39b9f4 [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/test/src/lib.rs:655:27 [INFO] [stdout] 33: 0x6065acb97383 - test::run_test::{{closure}}::hfb2007f8649c30bb [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/test/src/lib.rs:576:43 [INFO] [stdout] 34: 0x6065acb5a465 - test::run_test::{{closure}}::h56a17aa7a282a9f4 [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/test/src/lib.rs:606:41 [INFO] [stdout] 35: 0x6065acb5a465 - std::sys::backtrace::__rust_begin_short_backtrace::hd2d2d2fb8e8c6aac [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/sys/backtrace.rs:152:18 [INFO] [stdout] 36: 0x6065acb5dd4a - std::thread::Builder::spawn_unchecked_::{{closure}}::{{closure}}::h4faa3f9db6133423 [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/thread/mod.rs:559:17 [INFO] [stdout] 37: 0x6065acb5dd4a - as core::ops::function::FnOnce<()>>::call_once::hf2e855a36a4ea846 [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/core/src/panic/unwind_safe.rs:272:9 [INFO] [stdout] 38: 0x6065acb5dd4a - std::panicking::try::do_call::h2f73af3616c35465 [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/panicking.rs:587:40 [INFO] [stdout] 39: 0x6065acb5dd4a - std::panicking::try::hd1660ce9efadef5a [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/panicking.rs:550:19 [INFO] [stdout] 40: 0x6065acb5dd4a - std::panic::catch_unwind::h5ee8d7823b8ca744 [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/panic.rs:358:14 [INFO] [stdout] 41: 0x6065acb5dd4a - std::thread::Builder::spawn_unchecked_::{{closure}}::h53c3a1894dce8407 [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/thread/mod.rs:557:30 [INFO] [stdout] 42: 0x6065acb5dd4a - core::ops::function::FnOnce::call_once{{vtable.shim}}::h048ce291ad4f62bf [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/core/src/ops/function.rs:250:5 [INFO] [stdout] 43: 0x6065acf62e6b - as core::ops::function::FnOnce>::call_once::ha52bedf99a3b4981 [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/alloc/src/boxed.rs:2013:9 [INFO] [stdout] 44: 0x6065acf62e6b - as core::ops::function::FnOnce>::call_once::h567748934d80ccf8 [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/alloc/src/boxed.rs:2013:9 [INFO] [stdout] 45: 0x6065acf62e6b - std::sys::pal::unix::thread::Thread::new::thread_start::h2d970728ae887adc [INFO] [stdout] at /rustc/6067b36314ab5eb2eb47cecc464545ba58e1ad24/library/std/src/sys/pal/unix/thread.rs:106:17 [INFO] [stdout] 46: 0x7e25309feac3 - [INFO] [stdout] 47: 0x7e2530a8fa04 - clone [INFO] [stdout] 48: 0x0 - [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] failures: [INFO] [stdout] io::linux::tests::test_multiple_processes_cannot_open_file [INFO] [stdout] [INFO] [stdout] test result: FAILED. 134 passed; 1 failed; 1 ignored; 0 measured; 0 filtered out; finished in 0.04s [INFO] [stdout] [INFO] [stderr] error: test failed, to rerun pass `-p limbo_core --lib` [INFO] running `Command { std: "docker" "inspect" "a045e73409dabebec367a1acf8473a3ac6c9695e6a9cdf84e83a1aa2d0cfad25", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "a045e73409dabebec367a1acf8473a3ac6c9695e6a9cdf84e83a1aa2d0cfad25", kill_on_drop: false }` [INFO] [stdout] a045e73409dabebec367a1acf8473a3ac6c9695e6a9cdf84e83a1aa2d0cfad25