[INFO] cloning repository https://github.com/JohnDoe6345789/limbo [INFO] running `Command { std: "git" "-c" "credential.helper=" "-c" "credential.helper=/workspace/cargo-home/bin/git-credential-null" "clone" "--bare" "https://github.com/JohnDoe6345789/limbo" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2FJohnDoe6345789%2Flimbo", kill_on_drop: false }` [INFO] [stderr] Cloning into bare repository '/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2FJohnDoe6345789%2Flimbo'... [INFO] running `Command { std: "git" "rev-parse" "HEAD", kill_on_drop: false }` [INFO] [stdout] dbe6b8d899ecfd55d71bc3fae0d9e116c88644d0 [INFO] checking JohnDoe6345789/limbo against try#e983148bd5f0f0db270bfb72149f5e892e68b67f for pr-150322 [INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2FJohnDoe6345789%2Flimbo" "/workspace/builds/worker-1-tc2/source", kill_on_drop: false }` [INFO] [stderr] Cloning into '/workspace/builds/worker-1-tc2/source'... [INFO] [stderr] done. [INFO] removed /workspace/builds/worker-1-tc2/source/rust-toolchain.toml [INFO] started tweaking git repo https://github.com/JohnDoe6345789/limbo [INFO] finished tweaking git repo https://github.com/JohnDoe6345789/limbo [INFO] tweaked toml for git repo https://github.com/JohnDoe6345789/limbo written to /workspace/builds/worker-1-tc2/source/Cargo.toml [INFO] validating manifest of git repo https://github.com/JohnDoe6345789/limbo on toolchain e983148bd5f0f0db270bfb72149f5e892e68b67f [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+e983148bd5f0f0db270bfb72149f5e892e68b67f" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] crate git repo https://github.com/JohnDoe6345789/limbo 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" "+e983148bd5f0f0db270bfb72149f5e892e68b67f" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] [stderr] Blocking waiting for file lock on package cache [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-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:845e597a41426bbf2703be69acdb67d10b6de511142d05cba7bbe119c898b2c7" "/opt/rustwide/cargo-home/bin/cargo" "+e983148bd5f0f0db270bfb72149f5e892e68b67f" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] bdc0d0919cb8d089cbf86946f4bd72e88ab7d71de9259996984110c217cd1bd2 [INFO] running `Command { std: "docker" "start" "-a" "bdc0d0919cb8d089cbf86946f4bd72e88ab7d71de9259996984110c217cd1bd2", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "bdc0d0919cb8d089cbf86946f4bd72e88ab7d71de9259996984110c217cd1bd2", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "bdc0d0919cb8d089cbf86946f4bd72e88ab7d71de9259996984110c217cd1bd2", kill_on_drop: false }` [INFO] [stdout] bdc0d0919cb8d089cbf86946f4bd72e88ab7d71de9259996984110c217cd1bd2 [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" "-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:845e597a41426bbf2703be69acdb67d10b6de511142d05cba7bbe119c898b2c7" "/opt/rustwide/cargo-home/bin/cargo" "+e983148bd5f0f0db270bfb72149f5e892e68b67f" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] c13674b7d24248f17a42869cf29fdabfc595dc8ac0f31e219613decea3ef9872 [INFO] running `Command { std: "docker" "start" "-a" "c13674b7d24248f17a42869cf29fdabfc595dc8ac0f31e219613decea3ef9872", kill_on_drop: false }` [INFO] [stderr] Compiling libc v0.2.168 [INFO] [stderr] Compiling serde v1.0.216 [INFO] [stderr] Compiling once_cell v1.20.2 [INFO] [stderr] Checking bitflags v2.6.0 [INFO] [stderr] Checking log v0.4.22 [INFO] [stderr] Compiling siphasher v0.3.11 [INFO] [stderr] Compiling cc v1.2.3 [INFO] [stderr] Compiling uncased v0.9.10 [INFO] [stderr] Compiling num-traits v0.2.19 [INFO] [stderr] Checking itoa v1.0.14 [INFO] [stderr] Compiling memchr v2.7.4 [INFO] [stderr] Compiling thiserror v2.0.6 [INFO] [stderr] Checking fallible-iterator v0.3.0 [INFO] [stderr] Compiling syn v2.0.90 [INFO] [stderr] Compiling serde_json v1.0.133 [INFO] [stderr] Compiling target-lexicon v0.12.16 [INFO] [stderr] Compiling phf_shared v0.11.2 [INFO] [stderr] Compiling nix v0.29.0 [INFO] [stderr] Checking iana-time-zone v0.1.61 [INFO] [stderr] Compiling io-uring v0.6.4 [INFO] [stderr] Checking nom v7.1.3 [INFO] [stderr] Checking fast-float2 v0.2.3 [INFO] [stderr] Checking bumpalo v3.16.0 [INFO] [stderr] Checking cfg_block v0.1.1 [INFO] [stderr] Checking sieve-cache v0.1.4 [INFO] [stderr] Compiling phf_generator v0.11.2 [INFO] [stderr] Compiling rustix v0.38.42 [INFO] [stderr] Checking linux-raw-sys v0.4.14 [INFO] [stderr] Checking smallvec v1.13.2 [INFO] [stderr] Compiling ahash v0.8.11 [INFO] [stderr] Checking phf v0.11.2 [INFO] [stderr] Compiling phf_codegen v0.11.2 [INFO] [stderr] Checking anstream v0.6.18 [INFO] [stderr] Checking clap_lex v0.7.4 [INFO] [stderr] Checking futures-core v0.3.31 [INFO] [stderr] Compiling semver v1.0.23 [INFO] [stderr] Compiling crossbeam-utils v0.8.20 [INFO] [stderr] Compiling wasm-bindgen-shared v0.2.99 [INFO] [stderr] Checking strsim v0.11.1 [INFO] [stderr] Checking env_filter v0.1.2 [INFO] [stderr] Compiling anyhow v1.0.94 [INFO] [stderr] Checking futures-channel v0.3.31 [INFO] [stderr] Checking pin-project-lite v0.2.15 [INFO] [stderr] Checking env_logger v0.11.5 [INFO] [stderr] Checking clap_builder v4.5.23 [INFO] [stderr] Compiling aho-corasick v1.1.3 [INFO] [stderr] Compiling pyo3-build-config v0.22.6 [INFO] [stderr] Compiling regex-syntax v0.8.5 [INFO] [stderr] Checking either v1.13.0 [INFO] [stderr] Compiling rayon-core v1.12.1 [INFO] [stderr] Compiling rustc_version v0.4.1 [INFO] [stderr] Checking nibble_vec v0.1.0 [INFO] [stderr] Checking half v2.4.1 [INFO] [stderr] Compiling wasm-bindgen v0.2.99 [INFO] [stderr] Checking unicode-width v0.1.14 [INFO] [stderr] Checking uuid v1.11.0 [INFO] [stderr] Compiling sqlite3-parser v0.13.0 (/opt/rustwide/workdir/vendored/sqlite3-parser) [INFO] [stderr] Compiling libmimalloc-sys v0.1.39 [INFO] [stderr] Compiling libsqlite3-sys v0.26.0 [INFO] [stderr] Checking ordered-float v4.5.0 [INFO] [stderr] Checking chrono v0.4.39 [INFO] [stderr] Checking crossbeam-epoch v0.9.18 [INFO] [stderr] Compiling rstest_macros v0.18.2 [INFO] [stderr] Checking endian-type v0.1.2 [INFO] [stderr] Compiling cpp_demangle v0.4.4 [INFO] [stderr] Checking radix_trie v0.2.1 [INFO] [stderr] Checking crossbeam-deque v0.8.5 [INFO] [stderr] Checking debugid v0.8.0 [INFO] [stderr] Checking ciborium-ll v0.2.2 [INFO] [stderr] Compiling findshlibs v0.10.2 [INFO] [stderr] Checking getrandom v0.2.15 [INFO] [stderr] Checking is-terminal v0.4.13 [INFO] [stderr] Checking rand_core v0.6.4 [INFO] [stderr] Checking nix v0.26.4 [INFO] [stderr] Checking env_logger v0.10.2 [INFO] [stderr] Checking tempfile v3.14.0 [INFO] [stderr] Compiling regex-automata v0.4.9 [INFO] [stderr] Checking fd-lock v3.0.13 [INFO] [stderr] Checking mimalloc v0.1.43 [INFO] [stderr] Checking dirs-sys v0.4.1 [INFO] [stderr] Checking memmap2 v0.9.5 [INFO] [stderr] Checking itertools v0.10.5 [INFO] [stderr] Checking fallible-streaming-iterator v0.1.9 [INFO] [stderr] Checking fallible-iterator v0.2.0 [INFO] [stderr] Checking bytemuck v1.20.0 [INFO] [stderr] Checking julian_day_converter v0.3.2 [INFO] [stderr] Checking arrayvec v0.7.6 [INFO] [stderr] Compiling glob v0.3.1 [INFO] [stderr] Checking predicates-core v1.0.8 [INFO] [stderr] Compiling mockall_derive v0.13.1 [INFO] [stderr] Compiling symbolic-demangle v12.12.3 [INFO] [stderr] Checking gimli v0.31.1 [INFO] [stderr] Checking stable_deref_trait v1.2.0 [INFO] [stderr] Compiling relative-path v1.9.3 [INFO] [stderr] Checking rustc-demangle v0.1.24 [INFO] [stderr] Checking symbolic-common v12.12.3 [INFO] [stderr] Checking num-format v0.4.4 [INFO] [stderr] Checking rgb v0.8.50 [INFO] [stderr] Checking miniz_oxide v0.8.0 [INFO] [stderr] Checking plotters v0.3.7 [INFO] [stderr] Compiling pyo3-macros-backend v0.22.6 [INFO] [stderr] Compiling pyo3-ffi v0.22.6 [INFO] [stderr] Checking rustyline v12.0.0 [INFO] [stderr] Compiling pyo3 v0.22.6 [INFO] [stderr] Compiling syn v1.0.109 [INFO] [stderr] Checking dirs v5.0.1 [INFO] [stderr] Checking rayon v1.10.0 [INFO] [stderr] Checking parking_lot_core v0.9.10 [INFO] [stderr] Checking csv-core v0.1.11 [INFO] [stderr] Checking object v0.36.5 [INFO] [stderr] Checking quick-xml v0.26.0 [INFO] [stderr] Checking termtree v0.4.1 [INFO] [stderr] Checking futures-timer v3.0.3 [INFO] [stderr] Compiling pprof v0.14.0 [INFO] [stderr] Checking criterion-plot v0.5.0 [INFO] [stderr] Checking str_stack v0.1.0 [INFO] [stderr] Checking oorandom v11.1.4 [INFO] [stderr] Checking predicates-tree v1.0.11 [INFO] [stderr] Checking parking_lot v0.12.3 [INFO] [stderr] Compiling py-limbo v0.0.10 (/opt/rustwide/workdir/bindings/python) [INFO] [stderr] Compiling wasm-bindgen-backend v0.2.99 [INFO] [stderr] Checking predicates v3.1.2 [INFO] [stderr] Checking unindent v0.2.3 [INFO] [stderr] Checking fragile v2.0.0 [INFO] [stderr] Compiling indoc v2.0.5 [INFO] [stderr] Checking downcast v0.11.0 [INFO] [stderr] Checking ctrlc v3.4.5 [INFO] [stderr] Compiling regex v1.11.1 [INFO] [stderr] Compiling serde_derive v1.0.216 [INFO] [stderr] Compiling zerocopy-derive v0.7.35 [INFO] [stderr] Compiling thiserror-impl v2.0.6 [INFO] [stderr] Compiling thiserror-impl v1.0.69 [INFO] [stderr] Compiling clap_derive v4.5.18 [INFO] [stderr] Compiling futures-macro v0.3.31 [INFO] [stderr] Compiling equator-macro v0.2.1 [INFO] [stderr] Checking addr2line v0.24.2 [INFO] [stderr] Checking equator v0.2.2 [INFO] [stderr] Checking aligned-vec v0.6.1 [INFO] [stderr] Compiling wasm-bindgen-macro-support v0.2.99 [INFO] [stderr] Checking futures-util v0.3.31 [INFO] [stderr] Checking zerocopy v0.7.35 [INFO] [stderr] Compiling cli-table-derive v0.4.6 [INFO] [stderr] Compiling pest v2.7.15 [INFO] [stderr] Checking thiserror v1.0.69 [INFO] [stderr] Checking ppv-lite86 v0.2.20 [INFO] [stderr] Checking hashbrown v0.14.5 [INFO] [stderr] Compiling pest_meta v2.7.15 [INFO] [stderr] Checking rand_chacha v0.3.1 [INFO] [stderr] Checking clap v4.5.23 [INFO] [stderr] Checking rand v0.8.5 [INFO] [stderr] Compiling wasm-bindgen-macro v0.2.99 [INFO] [stderr] Checking mockall v0.13.1 [INFO] [stderr] Checking hashlink v0.8.4 [INFO] [stderr] Checking anarchist-readable-name-generator-lib v0.1.2 [INFO] [stderr] Compiling pyo3-macros v0.22.6 [INFO] [stderr] Compiling pest_generator v2.7.15 [INFO] [stderr] Checking backtrace v0.3.74 [INFO] [stderr] Checking console_error_panic_hook v0.1.7 [INFO] [stderr] Checking js-sys v0.3.76 [INFO] [stderr] Compiling pest_derive v2.7.15 [INFO] [stderr] Checking futures-executor v0.3.31 [INFO] [stderr] Checking futures v0.3.31 [INFO] [stderr] Checking rstest v0.18.2 [INFO] [stderr] Checking indexmap v2.7.0 [INFO] [stderr] Checking ciborium v0.2.2 [INFO] [stderr] Checking csv v1.3.1 [INFO] [stderr] Checking rusqlite v0.29.0 [INFO] [stderr] Checking cli-table v0.4.9 [INFO] [stderr] Checking inferno v0.11.21 [INFO] [stderr] Checking jsonb v0.4.4 [INFO] [stderr] Checking tinytemplate v1.2.1 [INFO] [stderr] Checking criterion v0.5.1 [INFO] [stderr] Checking limbo_core v0.0.10 (/opt/rustwide/workdir/core) [INFO] [stdout] warning: unused import: `debug` [INFO] [stdout] --> core/storage/pager.rs:6:11 [INFO] [stdout] | [INFO] [stdout] 6 | use log::{debug, trace}; [INFO] [stdout] | ^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(unused_imports)]` (part of `#[warn(unused)]`) on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused import: `HashSet` [INFO] [stdout] --> core/storage/wal.rs:1:33 [INFO] [stdout] | [INFO] [stdout] 1 | use std::collections::{HashMap, HashSet}; [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused import: `super::page_cache::PageCacheKey` [INFO] [stdout] --> core/storage/wal.rs:17:5 [INFO] [stdout] | [INFO] [stdout] 17 | use super::page_cache::PageCacheKey; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused import: `optimizer::Optimizable` [INFO] [stdout] --> core/translate/planner.rs:2:5 [INFO] [stdout] | [INFO] [stdout] 2 | optimizer::Optimizable, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: variable does not need to be mutable [INFO] [stdout] --> core/translate/planner.rs:258:13 [INFO] [stdout] | [INFO] [stdout] 258 | mut group_by, [INFO] [stdout] | ----^^^^^^^^ [INFO] [stdout] | | [INFO] [stdout] | help: remove this `mut` [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(unused_mut)]` (part of `#[warn(unused)]`) on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unreachable pattern [INFO] [stdout] --> core/translate/mod.rs:372:9 [INFO] [stdout] | [INFO] [stdout] 372 | _ => todo!("pragma `{name}`"), [INFO] [stdout] | ^ no value can reach this [INFO] [stdout] | [INFO] [stdout] note: multiple earlier patterns match some of the same values [INFO] [stdout] --> core/translate/mod.rs:372:9 [INFO] [stdout] | [INFO] [stdout] 352 | PragmaName::CacheSize => { [INFO] [stdout] | --------------------- matches some of the same values [INFO] [stdout] ... [INFO] [stdout] 368 | PragmaName::JournalMode => { [INFO] [stdout] | ----------------------- matches some of the same values [INFO] [stdout] ... [INFO] [stdout] 372 | _ => todo!("pragma `{name}`"), [INFO] [stdout] | ^ collectively making this unreachable [INFO] [stdout] = note: `#[warn(unreachable_patterns)]` (part of `#[warn(unused)]`) on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unreachable pattern [INFO] [stdout] --> core/translate/mod.rs:399:9 [INFO] [stdout] | [INFO] [stdout] 399 | _ => { [INFO] [stdout] | ^ no value can reach this [INFO] [stdout] | [INFO] [stdout] note: multiple earlier patterns match some of the same values [INFO] [stdout] --> core/translate/mod.rs:399:9 [INFO] [stdout] | [INFO] [stdout] 387 | PragmaName::CacheSize => { [INFO] [stdout] | --------------------- matches some of the same values [INFO] [stdout] ... [INFO] [stdout] 393 | PragmaName::JournalMode => { [INFO] [stdout] | ----------------------- matches some of the same values [INFO] [stdout] ... [INFO] [stdout] 399 | _ => { [INFO] [stdout] | ^ collectively making this unreachable [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused import: `debug` [INFO] [stdout] --> core/storage/pager.rs:6:11 [INFO] [stdout] | [INFO] [stdout] 6 | use log::{debug, trace}; [INFO] [stdout] | ^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(unused_imports)]` (part of `#[warn(unused)]`) on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused import: `HashSet` [INFO] [stdout] --> core/storage/wal.rs:1:33 [INFO] [stdout] | [INFO] [stdout] 1 | use std::collections::{HashMap, HashSet}; [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused import: `super::page_cache::PageCacheKey` [INFO] [stdout] --> core/storage/wal.rs:17:5 [INFO] [stdout] | [INFO] [stdout] 17 | use super::page_cache::PageCacheKey; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused import: `optimizer::Optimizable` [INFO] [stdout] --> core/translate/planner.rs:2:5 [INFO] [stdout] | [INFO] [stdout] 2 | optimizer::Optimizable, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: fields `shared_page_cache` and `shared_wal` are never read [INFO] [stdout] --> core/lib.rs:71:5 [INFO] [stdout] | [INFO] [stdout] 64 | pub struct Database { [INFO] [stdout] | -------- fields in this struct [INFO] [stdout] ... [INFO] [stdout] 71 | shared_page_cache: Arc>, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] 72 | shared_wal: Arc>, [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(dead_code)]` (part of `#[warn(unused)]`) on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: field `io` is never read [INFO] [stdout] --> core/storage/wal.rs:100:5 [INFO] [stdout] | [INFO] [stdout] 99 | pub struct WalFile { [INFO] [stdout] | ------- field in this struct [INFO] [stdout] 100 | io: Arc, [INFO] [stdout] | ^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: field `min_frame` is never read [INFO] [stdout] --> core/storage/wal.rs:119:5 [INFO] [stdout] | [INFO] [stdout] 117 | pub struct WalFileShared { [INFO] [stdout] | ------------- field in this struct [INFO] [stdout] 118 | wal_header: Arc>, [INFO] [stdout] 119 | min_frame: u64, [INFO] [stdout] | ^^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: method `next_free_register` is never used [INFO] [stdout] --> core/vdbe/builder.rs:62:12 [INFO] [stdout] | [INFO] [stdout] 33 | impl ProgramBuilder { [INFO] [stdout] | ------------------- method in this implementation [INFO] [stdout] ... [INFO] [stdout] 62 | pub fn next_free_register(&self) -> usize { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> core/io/memory.rs:29:29 [INFO] [stdout] | [INFO] [stdout] 29 | fn get_or_allocate_page(&self, page_no: usize) -> RefMut { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 29 | fn get_or_allocate_page(&self, page_no: usize) -> RefMut<'_, MemPage> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> core/io/memory.rs:36:17 [INFO] [stdout] | [INFO] [stdout] 36 | fn get_page(&self, page_no: usize) -> Option> { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 36 | fn get_page(&self, page_no: usize) -> Option> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> core/pseudo.rs:66:15 [INFO] [stdout] | [INFO] [stdout] 66 | fn record(&self) -> Result>> { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 66 | fn record(&self) -> Result>> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> core/storage/btree.rs:1733:15 [INFO] [stdout] | [INFO] [stdout] 1733 | fn record(&self) -> Result>> { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 1733 | fn record(&self) -> Result>> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `std::result::Result` that must be used [INFO] [stdout] --> core/storage/pager.rs:423:21 [INFO] [stdout] | [INFO] [stdout] 423 | self.io.run_once(); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] = note: `#[warn(unused_must_use)]` (part of `#[warn(unused)]`) on by default [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 423 | let _ = self.io.run_once(); [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> core/types.rs:439:15 [INFO] [stdout] | [INFO] [stdout] 439 | fn record(&self) -> Result>>; [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 439 | fn record(&self) -> Result>>; [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> core/vdbe/sorter.rs:81:15 [INFO] [stdout] | [INFO] [stdout] 81 | fn record(&self) -> Result>> { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 81 | fn record(&self) -> Result>> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Checking limbo v0.0.10 (/opt/rustwide/workdir/cli) [INFO] [stderr] Checking limbo-wasm v0.0.10 (/opt/rustwide/workdir/bindings/wasm) [INFO] [stderr] Checking core_tester v0.0.10 (/opt/rustwide/workdir/test) [INFO] [stderr] Checking limbo_sim v0.0.10 (/opt/rustwide/workdir/simulator) [INFO] [stderr] Checking limbo_sqlite3 v0.0.10 (/opt/rustwide/workdir/sqlite3) [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: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: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: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: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: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: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: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: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: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: field `delete_percent` is never read [INFO] [stdout] --> simulator/main.rs:35:5 [INFO] [stdout] | [INFO] [stdout] 27 | struct SimulatorOpts { [INFO] [stdout] | ------------- field in this struct [INFO] [stdout] ... [INFO] [stdout] 35 | delete_percent: usize, [INFO] [stdout] | ^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: `SimulatorOpts` has a derived impl for the trait `Debug`, but this is intentionally ignored during dead code analysis [INFO] [stdout] = note: `#[warn(dead_code)]` (part of `#[warn(unused)]`) on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: fields `primary` and `unique` are never read [INFO] [stdout] --> simulator/main.rs:49:5 [INFO] [stdout] | [INFO] [stdout] 46 | struct Column { [INFO] [stdout] | ------ fields in this struct [INFO] [stdout] ... [INFO] [stdout] 49 | primary: bool, [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] 50 | unique: bool, [INFO] [stdout] | ^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: `Column` has a derived impl for the trait `Clone`, but this is intentionally ignored during dead code analysis [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: field `page_size` is never read [INFO] [stdout] --> simulator/main.rs:460:5 [INFO] [stdout] | [INFO] [stdout] 452 | struct SimulatorFile { [INFO] [stdout] | ------------- field in this struct [INFO] [stdout] ... [INFO] [stdout] 460 | page_size: usize, [INFO] [stdout] | ^^^^^^^^^ [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: `#[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: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: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: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: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: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: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: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: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: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: field `db` is never read [INFO] [stdout] --> bindings/wasm/lib.rs:11:5 [INFO] [stdout] | [INFO] [stdout] 10 | pub struct Database { [INFO] [stdout] | -------- field in this struct [INFO] [stdout] 11 | db: Arc, [INFO] [stdout] | ^^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(dead_code)]` (part of `#[warn(unused)]`) on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: field `db` is never read [INFO] [stdout] --> bindings/wasm/lib.rs:11:5 [INFO] [stdout] | [INFO] [stdout] 10 | pub struct Database { [INFO] [stdout] | -------- field in this struct [INFO] [stdout] 11 | db: Arc, [INFO] [stdout] | ^^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(dead_code)]` (part of `#[warn(unused)]`) on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: field `delete_percent` is never read [INFO] [stdout] --> simulator/main.rs:35:5 [INFO] [stdout] | [INFO] [stdout] 27 | struct SimulatorOpts { [INFO] [stdout] | ------------- field in this struct [INFO] [stdout] ... [INFO] [stdout] 35 | delete_percent: usize, [INFO] [stdout] | ^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: `SimulatorOpts` has a derived impl for the trait `Debug`, but this is intentionally ignored during dead code analysis [INFO] [stdout] = note: `#[warn(dead_code)]` (part of `#[warn(unused)]`) on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: fields `primary` and `unique` are never read [INFO] [stdout] --> simulator/main.rs:49:5 [INFO] [stdout] | [INFO] [stdout] 46 | struct Column { [INFO] [stdout] | ------ fields in this struct [INFO] [stdout] ... [INFO] [stdout] 49 | primary: bool, [INFO] [stdout] | ^^^^^^^ [INFO] [stdout] 50 | unique: bool, [INFO] [stdout] | ^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: `Column` has a derived impl for the trait `Clone`, but this is intentionally ignored during dead code analysis [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: field `page_size` is never read [INFO] [stdout] --> simulator/main.rs:460:5 [INFO] [stdout] | [INFO] [stdout] 452 | struct SimulatorFile { [INFO] [stdout] | ------------- field in this struct [INFO] [stdout] ... [INFO] [stdout] 460 | page_size: usize, [INFO] [stdout] | ^^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: variable does not need to be mutable [INFO] [stdout] --> core/translate/planner.rs:258:13 [INFO] [stdout] | [INFO] [stdout] 258 | mut group_by, [INFO] [stdout] | ----^^^^^^^^ [INFO] [stdout] | | [INFO] [stdout] | help: remove this `mut` [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(unused_mut)]` (part of `#[warn(unused)]`) on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unreachable pattern [INFO] [stdout] --> core/translate/mod.rs:372:9 [INFO] [stdout] | [INFO] [stdout] 372 | _ => todo!("pragma `{name}`"), [INFO] [stdout] | ^ no value can reach this [INFO] [stdout] | [INFO] [stdout] note: multiple earlier patterns match some of the same values [INFO] [stdout] --> core/translate/mod.rs:372:9 [INFO] [stdout] | [INFO] [stdout] 352 | PragmaName::CacheSize => { [INFO] [stdout] | --------------------- matches some of the same values [INFO] [stdout] ... [INFO] [stdout] 368 | PragmaName::JournalMode => { [INFO] [stdout] | ----------------------- matches some of the same values [INFO] [stdout] ... [INFO] [stdout] 372 | _ => todo!("pragma `{name}`"), [INFO] [stdout] | ^ collectively making this unreachable [INFO] [stdout] = note: `#[warn(unreachable_patterns)]` (part of `#[warn(unused)]`) on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unreachable pattern [INFO] [stdout] --> core/translate/mod.rs:399:9 [INFO] [stdout] | [INFO] [stdout] 399 | _ => { [INFO] [stdout] | ^ no value can reach this [INFO] [stdout] | [INFO] [stdout] note: multiple earlier patterns match some of the same values [INFO] [stdout] --> core/translate/mod.rs:399:9 [INFO] [stdout] | [INFO] [stdout] 387 | PragmaName::CacheSize => { [INFO] [stdout] | --------------------- matches some of the same values [INFO] [stdout] ... [INFO] [stdout] 393 | PragmaName::JournalMode => { [INFO] [stdout] | ----------------------- matches some of the same values [INFO] [stdout] ... [INFO] [stdout] 399 | _ => { [INFO] [stdout] | ^ collectively making this unreachable [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: fields `shared_page_cache` and `shared_wal` are never read [INFO] [stdout] --> core/lib.rs:71:5 [INFO] [stdout] | [INFO] [stdout] 64 | pub struct Database { [INFO] [stdout] | -------- fields in this struct [INFO] [stdout] ... [INFO] [stdout] 71 | shared_page_cache: Arc>, [INFO] [stdout] | ^^^^^^^^^^^^^^^^^ [INFO] [stdout] 72 | shared_wal: Arc>, [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: `#[warn(dead_code)]` (part of `#[warn(unused)]`) on by default [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: field `io` is never read [INFO] [stdout] --> core/storage/wal.rs:100:5 [INFO] [stdout] | [INFO] [stdout] 99 | pub struct WalFile { [INFO] [stdout] | ------- field in this struct [INFO] [stdout] 100 | io: Arc, [INFO] [stdout] | ^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: field `min_frame` is never read [INFO] [stdout] --> core/storage/wal.rs:119:5 [INFO] [stdout] | [INFO] [stdout] 117 | pub struct WalFileShared { [INFO] [stdout] | ------------- field in this struct [INFO] [stdout] 118 | wal_header: Arc>, [INFO] [stdout] 119 | min_frame: u64, [INFO] [stdout] | ^^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: method `next_free_register` is never used [INFO] [stdout] --> core/vdbe/builder.rs:62:12 [INFO] [stdout] | [INFO] [stdout] 33 | impl ProgramBuilder { [INFO] [stdout] | ------------------- method in this implementation [INFO] [stdout] ... [INFO] [stdout] 62 | pub fn next_free_register(&self) -> usize { [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> core/io/memory.rs:29:29 [INFO] [stdout] | [INFO] [stdout] 29 | fn get_or_allocate_page(&self, page_no: usize) -> RefMut { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 29 | fn get_or_allocate_page(&self, page_no: usize) -> RefMut<'_, MemPage> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> core/io/memory.rs:36:17 [INFO] [stdout] | [INFO] [stdout] 36 | fn get_page(&self, page_no: usize) -> Option> { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 36 | fn get_page(&self, page_no: usize) -> Option> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> core/pseudo.rs:66:15 [INFO] [stdout] | [INFO] [stdout] 66 | fn record(&self) -> Result>> { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 66 | fn record(&self) -> Result>> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> core/storage/btree.rs:1733:15 [INFO] [stdout] | [INFO] [stdout] 1733 | fn record(&self) -> Result>> { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 1733 | fn record(&self) -> Result>> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unused `std::result::Result` that must be used [INFO] [stdout] --> core/storage/pager.rs:423:21 [INFO] [stdout] | [INFO] [stdout] 423 | self.io.run_once(); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: this `Result` may be an `Err` variant, which should be handled [INFO] [stdout] = note: `#[warn(unused_must_use)]` (part of `#[warn(unused)]`) on by default [INFO] [stdout] help: use `let _ = ...` to ignore the resulting value [INFO] [stdout] | [INFO] [stdout] 423 | let _ = self.io.run_once(); [INFO] [stdout] | +++++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> core/types.rs:439:15 [INFO] [stdout] | [INFO] [stdout] 439 | fn record(&self) -> Result>>; [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 439 | fn record(&self) -> Result>>; [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> core/vdbe/sorter.rs:81:15 [INFO] [stdout] | [INFO] [stdout] 81 | fn record(&self) -> Result>> { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 81 | fn record(&self) -> Result>> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> core/vdbe/mod.rs:3822:19 [INFO] [stdout] | [INFO] [stdout] 3822 | fn record(&self) -> Result>> { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 3822 | fn record(&self) -> Result>> { [INFO] [stdout] | +++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 57.44s [INFO] running `Command { std: "docker" "inspect" "c13674b7d24248f17a42869cf29fdabfc595dc8ac0f31e219613decea3ef9872", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "c13674b7d24248f17a42869cf29fdabfc595dc8ac0f31e219613decea3ef9872", kill_on_drop: false }` [INFO] [stdout] c13674b7d24248f17a42869cf29fdabfc595dc8ac0f31e219613decea3ef9872