[INFO] fetching crate product-os-store-macros 0.0.6...
[INFO] testing product-os-store-macros-0.0.6 against beta-2026-04-21 for beta-1.96-2
[INFO] extracting crate product-os-store-macros 0.0.6 into /workspace/builds/worker-3-tc2/source
[INFO] started tweaking crates.io crate product-os-store-macros 0.0.6
[INFO] removed 0 missing examples
[INFO] removed 0 missing tests
[INFO] finished tweaking crates.io crate product-os-store-macros 0.0.6
[INFO] tweaked toml for crates.io crate product-os-store-macros 0.0.6 written to /workspace/builds/worker-3-tc2/source/Cargo.toml
[INFO] validating manifest of crates.io crate product-os-store-macros 0.0.6 on toolchain beta-2026-04-21
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+beta-2026-04-21" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] crate crates.io crate product-os-store-macros 0.0.6 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" "+beta-2026-04-21" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:d429b63d4308055ea97f60fb1d3dfca48854a00942f1bd2ad806beaf015945ec" "/opt/rustwide/cargo-home/bin/cargo" "+beta-2026-04-21" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 63c27d2a06dc7ecb432be7bb0f5955ffe9696f837b110bf8ca1092b88b0998fb
[INFO] running `Command { std: "docker" "start" "-a" "63c27d2a06dc7ecb432be7bb0f5955ffe9696f837b110bf8ca1092b88b0998fb", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "63c27d2a06dc7ecb432be7bb0f5955ffe9696f837b110bf8ca1092b88b0998fb", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "63c27d2a06dc7ecb432be7bb0f5955ffe9696f837b110bf8ca1092b88b0998fb", kill_on_drop: false }`
[INFO] [stdout] 63c27d2a06dc7ecb432be7bb0f5955ffe9696f837b110bf8ca1092b88b0998fb
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "RUSTDOCFLAGS=--cap-lints=warn" "-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:d429b63d4308055ea97f60fb1d3dfca48854a00942f1bd2ad806beaf015945ec" "/opt/rustwide/cargo-home/bin/cargo" "+beta-2026-04-21" "build" "--frozen" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] 87f240df75eca0ec0b4c9a7bc8fa6fcd607515f5d64f62792bf632f0669a7ee8
[INFO] running `Command { std: "docker" "start" "-a" "87f240df75eca0ec0b4c9a7bc8fa6fcd607515f5d64f62792bf632f0669a7ee8", kill_on_drop: false }`
[INFO] [stderr]    Compiling memchr v2.8.0
[INFO] [stderr]    Compiling quote v1.0.44
[INFO] [stderr]    Compiling regex-syntax v0.8.9
[INFO] [stderr]    Compiling unicode-ident v1.0.23
[INFO] [stderr]    Compiling no-std-compat v0.4.1
[INFO] [stderr]    Compiling proc-macro2 v1.0.106
[INFO] [stderr]    Compiling syn v2.0.114
[INFO] [stderr]    Compiling aho-corasick v1.1.4
[INFO] [stderr]    Compiling regex-automata v0.4.14
[INFO] [stderr]    Compiling regex v1.12.3
[INFO] [stderr]    Compiling Inflector v0.11.4
[INFO] [stderr]    Compiling product-os-store-macros v0.0.6 (/opt/rustwide/workdir)
[INFO] [stdout] warning: `panic` is ambiguous
[INFO] [stdout]    --> src/relational.rs:382:14
[INFO] [stdout]     |
[INFO] [stdout] 382 |         _ => panic!("`to_relational_object` has to be used with structs "),
[INFO] [stdout]     |              ^^^^^ ambiguous name
[INFO] [stdout]     |
[INFO] [stdout]     = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
[INFO] [stdout] note: `panic` could refer to the macro imported here
[INFO] [stdout]    --> src/relational.rs:28:5
[INFO] [stdout]     |
[INFO] [stdout]  28 | use std::prelude::v1::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `panic` to disambiguate
[INFO] [stdout]     = help: or use `self::panic` to refer to this macro unambiguously
[INFO] [stdout] note: `panic` could also refer to a macro from prelude
[INFO] [stdout]    --> /rustc/8489f1adbe1c8f8921cf18b9962cf565237a5489/library/core/src/prelude/mod.rs:41:12
[INFO] [stdout]     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]     = note: for more information, see issue #147319 <https://github.com/rust-lang/rust/issues/147319>
[INFO] [stdout]     = note: `#[warn(ambiguous_panic_imports)]` (part of `#[warn(future_incompatible)]`) on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `panic` is ambiguous
[INFO] [stdout]    --> src/relational.rs:429:21
[INFO] [stdout]     |
[INFO] [stdout] 429 |             None => panic!("Problem with field review"),
[INFO] [stdout]     |                     ^^^^^ ambiguous name
[INFO] [stdout]     |
[INFO] [stdout]     = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
[INFO] [stdout] note: `panic` could refer to the macro imported here
[INFO] [stdout]    --> src/relational.rs:28:5
[INFO] [stdout]     |
[INFO] [stdout]  28 | use std::prelude::v1::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `panic` to disambiguate
[INFO] [stdout]     = help: or use `self::panic` to refer to this macro unambiguously
[INFO] [stdout] note: `panic` could also refer to a macro from prelude
[INFO] [stdout]    --> /rustc/8489f1adbe1c8f8921cf18b9962cf565237a5489/library/core/src/prelude/mod.rs:41:12
[INFO] [stdout]     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]     = note: for more information, see issue #147319 <https://github.com/rust-lang/rust/issues/147319>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `panic` is ambiguous
[INFO] [stdout]    --> src/relational.rs:515:43
[INFO] [stdout]     |
[INFO] [stdout] 515 | ...                   if not_null { panic!("Option not allowed - field must be not null: {}", field_name_string); }
[INFO] [stdout]     |                                     ^^^^^ ambiguous name
[INFO] [stdout]     |
[INFO] [stdout]     = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
[INFO] [stdout] note: `panic` could refer to the macro imported here
[INFO] [stdout]    --> src/relational.rs:28:5
[INFO] [stdout]     |
[INFO] [stdout]  28 | use std::prelude::v1::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `panic` to disambiguate
[INFO] [stdout]     = help: or use `self::panic` to refer to this macro unambiguously
[INFO] [stdout] note: `panic` could also refer to a macro from prelude
[INFO] [stdout]    --> /rustc/8489f1adbe1c8f8921cf18b9962cf565237a5489/library/core/src/prelude/mod.rs:41:12
[INFO] [stdout]     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]     = note: for more information, see issue #147319 <https://github.com/rust-lang/rust/issues/147319>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `panic` is ambiguous
[INFO] [stdout]    --> src/relational.rs:537:33
[INFO] [stdout]     |
[INFO] [stdout] 537 |                         None => panic!("Problem with field name building"),
[INFO] [stdout]     |                                 ^^^^^ ambiguous name
[INFO] [stdout]     |
[INFO] [stdout]     = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
[INFO] [stdout] note: `panic` could refer to the macro imported here
[INFO] [stdout]    --> src/relational.rs:28:5
[INFO] [stdout]     |
[INFO] [stdout]  28 | use std::prelude::v1::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `panic` to disambiguate
[INFO] [stdout]     = help: or use `self::panic` to refer to this macro unambiguously
[INFO] [stdout] note: `panic` could also refer to a macro from prelude
[INFO] [stdout]    --> /rustc/8489f1adbe1c8f8921cf18b9962cf565237a5489/library/core/src/prelude/mod.rs:41:12
[INFO] [stdout]     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]     = note: for more information, see issue #147319 <https://github.com/rust-lang/rust/issues/147319>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `panic` is ambiguous
[INFO] [stdout]    --> src/relational.rs:619:38
[INFO] [stdout]     |
[INFO] [stdout] 619 | ...                   _ => panic!("Types do not match for String")
[INFO] [stdout]     |                            ^^^^^ ambiguous name
[INFO] [stdout]     |
[INFO] [stdout]     = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
[INFO] [stdout] note: `panic` could refer to the macro imported here
[INFO] [stdout]    --> src/relational.rs:28:5
[INFO] [stdout]     |
[INFO] [stdout]  28 | use std::prelude::v1::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `panic` to disambiguate
[INFO] [stdout]     = help: or use `self::panic` to refer to this macro unambiguously
[INFO] [stdout] note: `panic` could also refer to a macro from prelude
[INFO] [stdout]    --> /rustc/8489f1adbe1c8f8921cf18b9962cf565237a5489/library/core/src/prelude/mod.rs:41:12
[INFO] [stdout]     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]     = note: for more information, see issue #147319 <https://github.com/rust-lang/rust/issues/147319>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `panic` is ambiguous
[INFO] [stdout]    --> src/relational.rs:641:46
[INFO] [stdout]     |
[INFO] [stdout] 641 | ...                   _ => panic!("Types do not match for String")
[INFO] [stdout]     |                            ^^^^^ ambiguous name
[INFO] [stdout]     |
[INFO] [stdout]     = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
[INFO] [stdout] note: `panic` could refer to the macro imported here
[INFO] [stdout]    --> src/relational.rs:28:5
[INFO] [stdout]     |
[INFO] [stdout]  28 | use std::prelude::v1::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `panic` to disambiguate
[INFO] [stdout]     = help: or use `self::panic` to refer to this macro unambiguously
[INFO] [stdout] note: `panic` could also refer to a macro from prelude
[INFO] [stdout]    --> /rustc/8489f1adbe1c8f8921cf18b9962cf565237a5489/library/core/src/prelude/mod.rs:41:12
[INFO] [stdout]     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]     = note: for more information, see issue #147319 <https://github.com/rust-lang/rust/issues/147319>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `panic` is ambiguous
[INFO] [stdout]    --> src/relational.rs:971:38
[INFO] [stdout]     |
[INFO] [stdout] 971 | ...                   _ => panic!("Types do not match for integer")
[INFO] [stdout]     |                            ^^^^^ ambiguous name
[INFO] [stdout]     |
[INFO] [stdout]     = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
[INFO] [stdout] note: `panic` could refer to the macro imported here
[INFO] [stdout]    --> src/relational.rs:28:5
[INFO] [stdout]     |
[INFO] [stdout]  28 | use std::prelude::v1::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `panic` to disambiguate
[INFO] [stdout]     = help: or use `self::panic` to refer to this macro unambiguously
[INFO] [stdout] note: `panic` could also refer to a macro from prelude
[INFO] [stdout]    --> /rustc/8489f1adbe1c8f8921cf18b9962cf565237a5489/library/core/src/prelude/mod.rs:41:12
[INFO] [stdout]     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]     = note: for more information, see issue #147319 <https://github.com/rust-lang/rust/issues/147319>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `panic` is ambiguous
[INFO] [stdout]     --> src/relational.rs:1315:38
[INFO] [stdout]      |
[INFO] [stdout] 1315 | ...                   _ => panic!("Types do not match for DateTime")
[INFO] [stdout]      |                            ^^^^^ ambiguous name
[INFO] [stdout]      |
[INFO] [stdout]      = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
[INFO] [stdout] note: `panic` could refer to the macro imported here
[INFO] [stdout]     --> src/relational.rs:28:5
[INFO] [stdout]      |
[INFO] [stdout]   28 | use std::prelude::v1::*;
[INFO] [stdout]      |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      = help: consider adding an explicit import of `panic` to disambiguate
[INFO] [stdout]      = help: or use `self::panic` to refer to this macro unambiguously
[INFO] [stdout] note: `panic` could also refer to a macro from prelude
[INFO] [stdout]     --> /rustc/8489f1adbe1c8f8921cf18b9962cf565237a5489/library/core/src/prelude/mod.rs:41:12
[INFO] [stdout]      = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]      = note: for more information, see issue #147319 <https://github.com/rust-lang/rust/issues/147319>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `panic` is ambiguous
[INFO] [stdout]     --> src/relational.rs:1371:38
[INFO] [stdout]      |
[INFO] [stdout] 1371 | ...                   _ => panic!("Types do not match for uuid")
[INFO] [stdout]      |                            ^^^^^ ambiguous name
[INFO] [stdout]      |
[INFO] [stdout]      = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
[INFO] [stdout] note: `panic` could refer to the macro imported here
[INFO] [stdout]     --> src/relational.rs:28:5
[INFO] [stdout]      |
[INFO] [stdout]   28 | use std::prelude::v1::*;
[INFO] [stdout]      |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      = help: consider adding an explicit import of `panic` to disambiguate
[INFO] [stdout]      = help: or use `self::panic` to refer to this macro unambiguously
[INFO] [stdout] note: `panic` could also refer to a macro from prelude
[INFO] [stdout]     --> /rustc/8489f1adbe1c8f8921cf18b9962cf565237a5489/library/core/src/prelude/mod.rs:41:12
[INFO] [stdout]      = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]      = note: for more information, see issue #147319 <https://github.com/rust-lang/rust/issues/147319>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `panic` is ambiguous
[INFO] [stdout]     --> src/relational.rs:1430:38
[INFO] [stdout]      |
[INFO] [stdout] 1430 | ...                   _ => panic!("Types do not match for json")
[INFO] [stdout]      |                            ^^^^^ ambiguous name
[INFO] [stdout]      |
[INFO] [stdout]      = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
[INFO] [stdout] note: `panic` could refer to the macro imported here
[INFO] [stdout]     --> src/relational.rs:28:5
[INFO] [stdout]      |
[INFO] [stdout]   28 | use std::prelude::v1::*;
[INFO] [stdout]      |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      = help: consider adding an explicit import of `panic` to disambiguate
[INFO] [stdout]      = help: or use `self::panic` to refer to this macro unambiguously
[INFO] [stdout] note: `panic` could also refer to a macro from prelude
[INFO] [stdout]     --> /rustc/8489f1adbe1c8f8921cf18b9962cf565237a5489/library/core/src/prelude/mod.rs:41:12
[INFO] [stdout]      = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]      = note: for more information, see issue #147319 <https://github.com/rust-lang/rust/issues/147319>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `panic` is ambiguous
[INFO] [stdout]     --> src/relational.rs:1452:46
[INFO] [stdout]      |
[INFO] [stdout] 1452 | ...                   _ => panic!("Types do not match for json")
[INFO] [stdout]      |                            ^^^^^ ambiguous name
[INFO] [stdout]      |
[INFO] [stdout]      = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
[INFO] [stdout] note: `panic` could refer to the macro imported here
[INFO] [stdout]     --> src/relational.rs:28:5
[INFO] [stdout]      |
[INFO] [stdout]   28 | use std::prelude::v1::*;
[INFO] [stdout]      |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      = help: consider adding an explicit import of `panic` to disambiguate
[INFO] [stdout]      = help: or use `self::panic` to refer to this macro unambiguously
[INFO] [stdout] note: `panic` could also refer to a macro from prelude
[INFO] [stdout]     --> /rustc/8489f1adbe1c8f8921cf18b9962cf565237a5489/library/core/src/prelude/mod.rs:41:12
[INFO] [stdout]      = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]      = note: for more information, see issue #147319 <https://github.com/rust-lang/rust/issues/147319>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `panic` is ambiguous
[INFO] [stdout]     --> src/relational.rs:1568:22
[INFO] [stdout]      |
[INFO] [stdout] 1568 |                 _ => panic!("Type not handled for {}: {:?}", field_name_string, field_type.type_id())
[INFO] [stdout]      |                      ^^^^^ ambiguous name
[INFO] [stdout]      |
[INFO] [stdout]      = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
[INFO] [stdout] note: `panic` could refer to the macro imported here
[INFO] [stdout]     --> src/relational.rs:28:5
[INFO] [stdout]      |
[INFO] [stdout]   28 | use std::prelude::v1::*;
[INFO] [stdout]      |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      = help: consider adding an explicit import of `panic` to disambiguate
[INFO] [stdout]      = help: or use `self::panic` to refer to this macro unambiguously
[INFO] [stdout] note: `panic` could also refer to a macro from prelude
[INFO] [stdout]     --> /rustc/8489f1adbe1c8f8921cf18b9962cf565237a5489/library/core/src/prelude/mod.rs:41:12
[INFO] [stdout]      = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]      = note: for more information, see issue #147319 <https://github.com/rust-lang/rust/issues/147319>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `panic` is ambiguous
[INFO] [stdout]    --> src/type_parsing.rs:150:38
[INFO] [stdout]     |
[INFO] [stdout] 150 | ...                   _ => panic!("Types with depth greater than one for angle bracketing not permitted")
[INFO] [stdout]     |                            ^^^^^ ambiguous name
[INFO] [stdout]     |
[INFO] [stdout]     = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
[INFO] [stdout] note: `panic` could refer to the macro imported here
[INFO] [stdout]    --> src/type_parsing.rs:6:5
[INFO] [stdout]     |
[INFO] [stdout]   6 | use std::prelude::v1::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `panic` to disambiguate
[INFO] [stdout]     = help: or use `self::panic` to refer to this macro unambiguously
[INFO] [stdout] note: `panic` could also refer to a macro from prelude
[INFO] [stdout]    --> /rustc/8489f1adbe1c8f8921cf18b9962cf565237a5489/library/core/src/prelude/mod.rs:41:12
[INFO] [stdout]     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]     = note: for more information, see issue #147319 <https://github.com/rust-lang/rust/issues/147319>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr]     Finished `dev` profile [unoptimized + debuginfo] target(s) in 10.05s
[INFO] running `Command { std: "docker" "inspect" "87f240df75eca0ec0b4c9a7bc8fa6fcd607515f5d64f62792bf632f0669a7ee8", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "87f240df75eca0ec0b4c9a7bc8fa6fcd607515f5d64f62792bf632f0669a7ee8", kill_on_drop: false }`
[INFO] [stdout] 87f240df75eca0ec0b4c9a7bc8fa6fcd607515f5d64f62792bf632f0669a7ee8
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "RUSTDOCFLAGS=--cap-lints=warn" "-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:d429b63d4308055ea97f60fb1d3dfca48854a00942f1bd2ad806beaf015945ec" "/opt/rustwide/cargo-home/bin/cargo" "+beta-2026-04-21" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] f142f03a01b3956b02dfc3ae774bca0f5fc76d195bd705b735af5a33bfe125a7
[INFO] running `Command { std: "docker" "start" "-a" "f142f03a01b3956b02dfc3ae774bca0f5fc76d195bd705b735af5a33bfe125a7", kill_on_drop: false }`
[INFO] [stderr]    Compiling serde_core v1.0.228
[INFO] [stderr]    Compiling aho-corasick v1.1.4
[INFO] [stderr]    Compiling regex-syntax v0.8.9
[INFO] [stderr]    Compiling libc v0.2.180
[INFO] [stderr]    Compiling unicode-ident v1.0.23
[INFO] [stderr]    Compiling getrandom v0.3.4
[INFO] [stderr]    Compiling zmij v1.0.20
[INFO] [stderr]    Compiling serde_json v1.0.149
[INFO] [stderr]    Compiling serde v1.0.228
[INFO] [stderr]    Compiling itoa v1.0.17
[INFO] [stderr]    Compiling no-std-compat v0.4.1
[INFO] [stderr]    Compiling proc-macro2 v1.0.106
[INFO] [stderr]    Compiling quote v1.0.44
[INFO] [stderr]    Compiling chrono v0.4.43
[INFO] [stderr]    Compiling syn v2.0.114
[INFO] [stderr]    Compiling regex-automata v0.4.14
[INFO] [stderr]    Compiling uuid v1.20.0
[INFO] [stderr]    Compiling regex v1.12.3
[INFO] [stderr]    Compiling Inflector v0.11.4
[INFO] [stderr]    Compiling product-os-store-macros v0.0.6 (/opt/rustwide/workdir)
[INFO] [stdout] warning: `panic` is ambiguous
[INFO] [stdout]    --> src/relational.rs:382:14
[INFO] [stdout]     |
[INFO] [stdout] 382 |         _ => panic!("`to_relational_object` has to be used with structs "),
[INFO] [stdout]     |              ^^^^^ ambiguous name
[INFO] [stdout]     |
[INFO] [stdout]     = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
[INFO] [stdout] note: `panic` could refer to the macro imported here
[INFO] [stdout]    --> src/relational.rs:28:5
[INFO] [stdout]     |
[INFO] [stdout]  28 | use std::prelude::v1::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `panic` to disambiguate
[INFO] [stdout]     = help: or use `self::panic` to refer to this macro unambiguously
[INFO] [stdout] note: `panic` could also refer to a macro from prelude
[INFO] [stdout]    --> /rustc/8489f1adbe1c8f8921cf18b9962cf565237a5489/library/core/src/prelude/mod.rs:41:12
[INFO] [stdout]     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]     = note: for more information, see issue #147319 <https://github.com/rust-lang/rust/issues/147319>
[INFO] [stdout]     = note: `#[warn(ambiguous_panic_imports)]` (part of `#[warn(future_incompatible)]`) on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `panic` is ambiguous
[INFO] [stdout]    --> src/relational.rs:429:21
[INFO] [stdout]     |
[INFO] [stdout] 429 |             None => panic!("Problem with field review"),
[INFO] [stdout]     |                     ^^^^^ ambiguous name
[INFO] [stdout]     |
[INFO] [stdout]     = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
[INFO] [stdout] note: `panic` could refer to the macro imported here
[INFO] [stdout]    --> src/relational.rs:28:5
[INFO] [stdout]     |
[INFO] [stdout]  28 | use std::prelude::v1::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `panic` to disambiguate
[INFO] [stdout]     = help: or use `self::panic` to refer to this macro unambiguously
[INFO] [stdout] note: `panic` could also refer to a macro from prelude
[INFO] [stdout]    --> /rustc/8489f1adbe1c8f8921cf18b9962cf565237a5489/library/core/src/prelude/mod.rs:41:12
[INFO] [stdout]     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]     = note: for more information, see issue #147319 <https://github.com/rust-lang/rust/issues/147319>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `panic` is ambiguous
[INFO] [stdout]    --> src/relational.rs:515:43
[INFO] [stdout]     |
[INFO] [stdout] 515 | ...                   if not_null { panic!("Option not allowed - field must be not null: {}", field_name_string); }
[INFO] [stdout]     |                                     ^^^^^ ambiguous name
[INFO] [stdout]     |
[INFO] [stdout]     = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
[INFO] [stdout] note: `panic` could refer to the macro imported here
[INFO] [stdout]    --> src/relational.rs:28:5
[INFO] [stdout]     |
[INFO] [stdout]  28 | use std::prelude::v1::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `panic` to disambiguate
[INFO] [stdout]     = help: or use `self::panic` to refer to this macro unambiguously
[INFO] [stdout] note: `panic` could also refer to a macro from prelude
[INFO] [stdout]    --> /rustc/8489f1adbe1c8f8921cf18b9962cf565237a5489/library/core/src/prelude/mod.rs:41:12
[INFO] [stdout]     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]     = note: for more information, see issue #147319 <https://github.com/rust-lang/rust/issues/147319>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `panic` is ambiguous
[INFO] [stdout]    --> src/relational.rs:537:33
[INFO] [stdout]     |
[INFO] [stdout] 537 |                         None => panic!("Problem with field name building"),
[INFO] [stdout]     |                                 ^^^^^ ambiguous name
[INFO] [stdout]     |
[INFO] [stdout]     = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
[INFO] [stdout] note: `panic` could refer to the macro imported here
[INFO] [stdout]    --> src/relational.rs:28:5
[INFO] [stdout]     |
[INFO] [stdout]  28 | use std::prelude::v1::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `panic` to disambiguate
[INFO] [stdout]     = help: or use `self::panic` to refer to this macro unambiguously
[INFO] [stdout] note: `panic` could also refer to a macro from prelude
[INFO] [stdout]    --> /rustc/8489f1adbe1c8f8921cf18b9962cf565237a5489/library/core/src/prelude/mod.rs:41:12
[INFO] [stdout]     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]     = note: for more information, see issue #147319 <https://github.com/rust-lang/rust/issues/147319>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `panic` is ambiguous
[INFO] [stdout]    --> src/relational.rs:619:38
[INFO] [stdout]     |
[INFO] [stdout] 619 | ...                   _ => panic!("Types do not match for String")
[INFO] [stdout]     |                            ^^^^^ ambiguous name
[INFO] [stdout]     |
[INFO] [stdout]     = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
[INFO] [stdout] note: `panic` could refer to the macro imported here
[INFO] [stdout]    --> src/relational.rs:28:5
[INFO] [stdout]     |
[INFO] [stdout]  28 | use std::prelude::v1::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `panic` to disambiguate
[INFO] [stdout]     = help: or use `self::panic` to refer to this macro unambiguously
[INFO] [stdout] note: `panic` could also refer to a macro from prelude
[INFO] [stdout]    --> /rustc/8489f1adbe1c8f8921cf18b9962cf565237a5489/library/core/src/prelude/mod.rs:41:12
[INFO] [stdout]     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]     = note: for more information, see issue #147319 <https://github.com/rust-lang/rust/issues/147319>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `panic` is ambiguous
[INFO] [stdout]    --> src/relational.rs:641:46
[INFO] [stdout]     |
[INFO] [stdout] 641 | ...                   _ => panic!("Types do not match for String")
[INFO] [stdout]     |                            ^^^^^ ambiguous name
[INFO] [stdout]     |
[INFO] [stdout]     = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
[INFO] [stdout] note: `panic` could refer to the macro imported here
[INFO] [stdout]    --> src/relational.rs:28:5
[INFO] [stdout]     |
[INFO] [stdout]  28 | use std::prelude::v1::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `panic` to disambiguate
[INFO] [stdout]     = help: or use `self::panic` to refer to this macro unambiguously
[INFO] [stdout] note: `panic` could also refer to a macro from prelude
[INFO] [stdout]    --> /rustc/8489f1adbe1c8f8921cf18b9962cf565237a5489/library/core/src/prelude/mod.rs:41:12
[INFO] [stdout]     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]     = note: for more information, see issue #147319 <https://github.com/rust-lang/rust/issues/147319>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `panic` is ambiguous
[INFO] [stdout]    --> src/relational.rs:971:38
[INFO] [stdout]     |
[INFO] [stdout] 971 | ...                   _ => panic!("Types do not match for integer")
[INFO] [stdout]     |                            ^^^^^ ambiguous name
[INFO] [stdout]     |
[INFO] [stdout]     = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
[INFO] [stdout] note: `panic` could refer to the macro imported here
[INFO] [stdout]    --> src/relational.rs:28:5
[INFO] [stdout]     |
[INFO] [stdout]  28 | use std::prelude::v1::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `panic` to disambiguate
[INFO] [stdout]     = help: or use `self::panic` to refer to this macro unambiguously
[INFO] [stdout] note: `panic` could also refer to a macro from prelude
[INFO] [stdout]    --> /rustc/8489f1adbe1c8f8921cf18b9962cf565237a5489/library/core/src/prelude/mod.rs:41:12
[INFO] [stdout]     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]     = note: for more information, see issue #147319 <https://github.com/rust-lang/rust/issues/147319>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `panic` is ambiguous
[INFO] [stdout]     --> src/relational.rs:1315:38
[INFO] [stdout]      |
[INFO] [stdout] 1315 | ...                   _ => panic!("Types do not match for DateTime")
[INFO] [stdout]      |                            ^^^^^ ambiguous name
[INFO] [stdout]      |
[INFO] [stdout]      = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
[INFO] [stdout] note: `panic` could refer to the macro imported here
[INFO] [stdout]     --> src/relational.rs:28:5
[INFO] [stdout]      |
[INFO] [stdout]   28 | use std::prelude::v1::*;
[INFO] [stdout]      |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      = help: consider adding an explicit import of `panic` to disambiguate
[INFO] [stdout]      = help: or use `self::panic` to refer to this macro unambiguously
[INFO] [stdout] note: `panic` could also refer to a macro from prelude
[INFO] [stdout]     --> /rustc/8489f1adbe1c8f8921cf18b9962cf565237a5489/library/core/src/prelude/mod.rs:41:12
[INFO] [stdout]      = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]      = note: for more information, see issue #147319 <https://github.com/rust-lang/rust/issues/147319>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `panic` is ambiguous
[INFO] [stdout]     --> src/relational.rs:1371:38
[INFO] [stdout]      |
[INFO] [stdout] 1371 | ...                   _ => panic!("Types do not match for uuid")
[INFO] [stdout]      |                            ^^^^^ ambiguous name
[INFO] [stdout]      |
[INFO] [stdout]      = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
[INFO] [stdout] note: `panic` could refer to the macro imported here
[INFO] [stdout]     --> src/relational.rs:28:5
[INFO] [stdout]      |
[INFO] [stdout]   28 | use std::prelude::v1::*;
[INFO] [stdout]      |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      = help: consider adding an explicit import of `panic` to disambiguate
[INFO] [stdout]      = help: or use `self::panic` to refer to this macro unambiguously
[INFO] [stdout] note: `panic` could also refer to a macro from prelude
[INFO] [stdout]     --> /rustc/8489f1adbe1c8f8921cf18b9962cf565237a5489/library/core/src/prelude/mod.rs:41:12
[INFO] [stdout]      = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]      = note: for more information, see issue #147319 <https://github.com/rust-lang/rust/issues/147319>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `panic` is ambiguous
[INFO] [stdout]     --> src/relational.rs:1430:38
[INFO] [stdout]      |
[INFO] [stdout] 1430 | ...                   _ => panic!("Types do not match for json")
[INFO] [stdout]      |                            ^^^^^ ambiguous name
[INFO] [stdout]      |
[INFO] [stdout]      = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
[INFO] [stdout] note: `panic` could refer to the macro imported here
[INFO] [stdout]     --> src/relational.rs:28:5
[INFO] [stdout]      |
[INFO] [stdout]   28 | use std::prelude::v1::*;
[INFO] [stdout]      |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      = help: consider adding an explicit import of `panic` to disambiguate
[INFO] [stdout]      = help: or use `self::panic` to refer to this macro unambiguously
[INFO] [stdout] note: `panic` could also refer to a macro from prelude
[INFO] [stdout]     --> /rustc/8489f1adbe1c8f8921cf18b9962cf565237a5489/library/core/src/prelude/mod.rs:41:12
[INFO] [stdout]      = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]      = note: for more information, see issue #147319 <https://github.com/rust-lang/rust/issues/147319>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `panic` is ambiguous
[INFO] [stdout]     --> src/relational.rs:1452:46
[INFO] [stdout]      |
[INFO] [stdout] 1452 | ...                   _ => panic!("Types do not match for json")
[INFO] [stdout]      |                            ^^^^^ ambiguous name
[INFO] [stdout]      |
[INFO] [stdout]      = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
[INFO] [stdout] note: `panic` could refer to the macro imported here
[INFO] [stdout]     --> src/relational.rs:28:5
[INFO] [stdout]      |
[INFO] [stdout]   28 | use std::prelude::v1::*;
[INFO] [stdout]      |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      = help: consider adding an explicit import of `panic` to disambiguate
[INFO] [stdout]      = help: or use `self::panic` to refer to this macro unambiguously
[INFO] [stdout] note: `panic` could also refer to a macro from prelude
[INFO] [stdout]     --> /rustc/8489f1adbe1c8f8921cf18b9962cf565237a5489/library/core/src/prelude/mod.rs:41:12
[INFO] [stdout]      = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]      = note: for more information, see issue #147319 <https://github.com/rust-lang/rust/issues/147319>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `panic` is ambiguous
[INFO] [stdout]     --> src/relational.rs:1568:22
[INFO] [stdout]      |
[INFO] [stdout] 1568 |                 _ => panic!("Type not handled for {}: {:?}", field_name_string, field_type.type_id())
[INFO] [stdout]      |                      ^^^^^ ambiguous name
[INFO] [stdout]      |
[INFO] [stdout]      = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
[INFO] [stdout] note: `panic` could refer to the macro imported here
[INFO] [stdout]     --> src/relational.rs:28:5
[INFO] [stdout]      |
[INFO] [stdout]   28 | use std::prelude::v1::*;
[INFO] [stdout]      |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      = help: consider adding an explicit import of `panic` to disambiguate
[INFO] [stdout]      = help: or use `self::panic` to refer to this macro unambiguously
[INFO] [stdout] note: `panic` could also refer to a macro from prelude
[INFO] [stdout]     --> /rustc/8489f1adbe1c8f8921cf18b9962cf565237a5489/library/core/src/prelude/mod.rs:41:12
[INFO] [stdout]      = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]      = note: for more information, see issue #147319 <https://github.com/rust-lang/rust/issues/147319>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `panic` is ambiguous
[INFO] [stdout]    --> src/type_parsing.rs:150:38
[INFO] [stdout]     |
[INFO] [stdout] 150 | ...                   _ => panic!("Types with depth greater than one for angle bracketing not permitted")
[INFO] [stdout]     |                            ^^^^^ ambiguous name
[INFO] [stdout]     |
[INFO] [stdout]     = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
[INFO] [stdout] note: `panic` could refer to the macro imported here
[INFO] [stdout]    --> src/type_parsing.rs:6:5
[INFO] [stdout]     |
[INFO] [stdout]   6 | use std::prelude::v1::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `panic` to disambiguate
[INFO] [stdout]     = help: or use `self::panic` to refer to this macro unambiguously
[INFO] [stdout] note: `panic` could also refer to a macro from prelude
[INFO] [stdout]    --> /rustc/8489f1adbe1c8f8921cf18b9962cf565237a5489/library/core/src/prelude/mod.rs:41:12
[INFO] [stdout]     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]     = note: for more information, see issue #147319 <https://github.com/rust-lang/rust/issues/147319>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `panic` is ambiguous
[INFO] [stdout]    --> src/relational.rs:382:14
[INFO] [stdout]     |
[INFO] [stdout] 382 |         _ => panic!("`to_relational_object` has to be used with structs "),
[INFO] [stdout]     |              ^^^^^ ambiguous name
[INFO] [stdout]     |
[INFO] [stdout]     = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
[INFO] [stdout] note: `panic` could refer to the macro imported here
[INFO] [stdout]    --> src/relational.rs:28:5
[INFO] [stdout]     |
[INFO] [stdout]  28 | use std::prelude::v1::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `panic` to disambiguate
[INFO] [stdout]     = help: or use `self::panic` to refer to this macro unambiguously
[INFO] [stdout] note: `panic` could also refer to a macro from prelude
[INFO] [stdout]    --> /rustc/8489f1adbe1c8f8921cf18b9962cf565237a5489/library/core/src/prelude/mod.rs:41:12
[INFO] [stdout]     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]     = note: for more information, see issue #147319 <https://github.com/rust-lang/rust/issues/147319>
[INFO] [stdout]     = note: `#[warn(ambiguous_panic_imports)]` (part of `#[warn(future_incompatible)]`) on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `panic` is ambiguous
[INFO] [stdout]    --> src/relational.rs:429:21
[INFO] [stdout]     |
[INFO] [stdout] 429 |             None => panic!("Problem with field review"),
[INFO] [stdout]     |                     ^^^^^ ambiguous name
[INFO] [stdout]     |
[INFO] [stdout]     = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
[INFO] [stdout] note: `panic` could refer to the macro imported here
[INFO] [stdout]    --> src/relational.rs:28:5
[INFO] [stdout]     |
[INFO] [stdout]  28 | use std::prelude::v1::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `panic` to disambiguate
[INFO] [stdout]     = help: or use `self::panic` to refer to this macro unambiguously
[INFO] [stdout] note: `panic` could also refer to a macro from prelude
[INFO] [stdout]    --> /rustc/8489f1adbe1c8f8921cf18b9962cf565237a5489/library/core/src/prelude/mod.rs:41:12
[INFO] [stdout]     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]     = note: for more information, see issue #147319 <https://github.com/rust-lang/rust/issues/147319>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `panic` is ambiguous
[INFO] [stdout]    --> src/relational.rs:515:43
[INFO] [stdout]     |
[INFO] [stdout] 515 | ...                   if not_null { panic!("Option not allowed - field must be not null: {}", field_name_string); }
[INFO] [stdout]     |                                     ^^^^^ ambiguous name
[INFO] [stdout]     |
[INFO] [stdout]     = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
[INFO] [stdout] note: `panic` could refer to the macro imported here
[INFO] [stdout]    --> src/relational.rs:28:5
[INFO] [stdout]     |
[INFO] [stdout]  28 | use std::prelude::v1::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `panic` to disambiguate
[INFO] [stdout]     = help: or use `self::panic` to refer to this macro unambiguously
[INFO] [stdout] note: `panic` could also refer to a macro from prelude
[INFO] [stdout]    --> /rustc/8489f1adbe1c8f8921cf18b9962cf565237a5489/library/core/src/prelude/mod.rs:41:12
[INFO] [stdout]     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]     = note: for more information, see issue #147319 <https://github.com/rust-lang/rust/issues/147319>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `panic` is ambiguous
[INFO] [stdout]    --> src/relational.rs:537:33
[INFO] [stdout]     |
[INFO] [stdout] 537 |                         None => panic!("Problem with field name building"),
[INFO] [stdout]     |                                 ^^^^^ ambiguous name
[INFO] [stdout]     |
[INFO] [stdout]     = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
[INFO] [stdout] note: `panic` could refer to the macro imported here
[INFO] [stdout]    --> src/relational.rs:28:5
[INFO] [stdout]     |
[INFO] [stdout]  28 | use std::prelude::v1::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `panic` to disambiguate
[INFO] [stdout]     = help: or use `self::panic` to refer to this macro unambiguously
[INFO] [stdout] note: `panic` could also refer to a macro from prelude
[INFO] [stdout]    --> /rustc/8489f1adbe1c8f8921cf18b9962cf565237a5489/library/core/src/prelude/mod.rs:41:12
[INFO] [stdout]     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]     = note: for more information, see issue #147319 <https://github.com/rust-lang/rust/issues/147319>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `panic` is ambiguous
[INFO] [stdout]    --> src/relational.rs:619:38
[INFO] [stdout]     |
[INFO] [stdout] 619 | ...                   _ => panic!("Types do not match for String")
[INFO] [stdout]     |                            ^^^^^ ambiguous name
[INFO] [stdout]     |
[INFO] [stdout]     = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
[INFO] [stdout] note: `panic` could refer to the macro imported here
[INFO] [stdout]    --> src/relational.rs:28:5
[INFO] [stdout]     |
[INFO] [stdout]  28 | use std::prelude::v1::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `panic` to disambiguate
[INFO] [stdout]     = help: or use `self::panic` to refer to this macro unambiguously
[INFO] [stdout] note: `panic` could also refer to a macro from prelude
[INFO] [stdout]    --> /rustc/8489f1adbe1c8f8921cf18b9962cf565237a5489/library/core/src/prelude/mod.rs:41:12
[INFO] [stdout]     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]     = note: for more information, see issue #147319 <https://github.com/rust-lang/rust/issues/147319>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `panic` is ambiguous
[INFO] [stdout]    --> src/relational.rs:641:46
[INFO] [stdout]     |
[INFO] [stdout] 641 | ...                   _ => panic!("Types do not match for String")
[INFO] [stdout]     |                            ^^^^^ ambiguous name
[INFO] [stdout]     |
[INFO] [stdout]     = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
[INFO] [stdout] note: `panic` could refer to the macro imported here
[INFO] [stdout]    --> src/relational.rs:28:5
[INFO] [stdout]     |
[INFO] [stdout]  28 | use std::prelude::v1::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `panic` to disambiguate
[INFO] [stdout]     = help: or use `self::panic` to refer to this macro unambiguously
[INFO] [stdout] note: `panic` could also refer to a macro from prelude
[INFO] [stdout]    --> /rustc/8489f1adbe1c8f8921cf18b9962cf565237a5489/library/core/src/prelude/mod.rs:41:12
[INFO] [stdout]     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]     = note: for more information, see issue #147319 <https://github.com/rust-lang/rust/issues/147319>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `panic` is ambiguous
[INFO] [stdout]    --> src/relational.rs:971:38
[INFO] [stdout]     |
[INFO] [stdout] 971 | ...                   _ => panic!("Types do not match for integer")
[INFO] [stdout]     |                            ^^^^^ ambiguous name
[INFO] [stdout]     |
[INFO] [stdout]     = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
[INFO] [stdout] note: `panic` could refer to the macro imported here
[INFO] [stdout]    --> src/relational.rs:28:5
[INFO] [stdout]     |
[INFO] [stdout]  28 | use std::prelude::v1::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `panic` to disambiguate
[INFO] [stdout]     = help: or use `self::panic` to refer to this macro unambiguously
[INFO] [stdout] note: `panic` could also refer to a macro from prelude
[INFO] [stdout]    --> /rustc/8489f1adbe1c8f8921cf18b9962cf565237a5489/library/core/src/prelude/mod.rs:41:12
[INFO] [stdout]     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]     = note: for more information, see issue #147319 <https://github.com/rust-lang/rust/issues/147319>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `panic` is ambiguous
[INFO] [stdout]     --> src/relational.rs:1315:38
[INFO] [stdout]      |
[INFO] [stdout] 1315 | ...                   _ => panic!("Types do not match for DateTime")
[INFO] [stdout]      |                            ^^^^^ ambiguous name
[INFO] [stdout]      |
[INFO] [stdout]      = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
[INFO] [stdout] note: `panic` could refer to the macro imported here
[INFO] [stdout]     --> src/relational.rs:28:5
[INFO] [stdout]      |
[INFO] [stdout]   28 | use std::prelude::v1::*;
[INFO] [stdout]      |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      = help: consider adding an explicit import of `panic` to disambiguate
[INFO] [stdout]      = help: or use `self::panic` to refer to this macro unambiguously
[INFO] [stdout] note: `panic` could also refer to a macro from prelude
[INFO] [stdout]     --> /rustc/8489f1adbe1c8f8921cf18b9962cf565237a5489/library/core/src/prelude/mod.rs:41:12
[INFO] [stdout]      = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]      = note: for more information, see issue #147319 <https://github.com/rust-lang/rust/issues/147319>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `panic` is ambiguous
[INFO] [stdout]     --> src/relational.rs:1371:38
[INFO] [stdout]      |
[INFO] [stdout] 1371 | ...                   _ => panic!("Types do not match for uuid")
[INFO] [stdout]      |                            ^^^^^ ambiguous name
[INFO] [stdout]      |
[INFO] [stdout]      = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
[INFO] [stdout] note: `panic` could refer to the macro imported here
[INFO] [stdout]     --> src/relational.rs:28:5
[INFO] [stdout]      |
[INFO] [stdout]   28 | use std::prelude::v1::*;
[INFO] [stdout]      |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      = help: consider adding an explicit import of `panic` to disambiguate
[INFO] [stdout]      = help: or use `self::panic` to refer to this macro unambiguously
[INFO] [stdout] note: `panic` could also refer to a macro from prelude
[INFO] [stdout]     --> /rustc/8489f1adbe1c8f8921cf18b9962cf565237a5489/library/core/src/prelude/mod.rs:41:12
[INFO] [stdout]      = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]      = note: for more information, see issue #147319 <https://github.com/rust-lang/rust/issues/147319>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `panic` is ambiguous
[INFO] [stdout]     --> src/relational.rs:1430:38
[INFO] [stdout]      |
[INFO] [stdout] 1430 | ...                   _ => panic!("Types do not match for json")
[INFO] [stdout]      |                            ^^^^^ ambiguous name
[INFO] [stdout]      |
[INFO] [stdout]      = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
[INFO] [stdout] note: `panic` could refer to the macro imported here
[INFO] [stdout]     --> src/relational.rs:28:5
[INFO] [stdout]      |
[INFO] [stdout]   28 | use std::prelude::v1::*;
[INFO] [stdout]      |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      = help: consider adding an explicit import of `panic` to disambiguate
[INFO] [stdout]      = help: or use `self::panic` to refer to this macro unambiguously
[INFO] [stdout] note: `panic` could also refer to a macro from prelude
[INFO] [stdout]     --> /rustc/8489f1adbe1c8f8921cf18b9962cf565237a5489/library/core/src/prelude/mod.rs:41:12
[INFO] [stdout]      = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]      = note: for more information, see issue #147319 <https://github.com/rust-lang/rust/issues/147319>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `panic` is ambiguous
[INFO] [stdout]     --> src/relational.rs:1452:46
[INFO] [stdout]      |
[INFO] [stdout] 1452 | ...                   _ => panic!("Types do not match for json")
[INFO] [stdout]      |                            ^^^^^ ambiguous name
[INFO] [stdout]      |
[INFO] [stdout]      = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
[INFO] [stdout] note: `panic` could refer to the macro imported here
[INFO] [stdout]     --> src/relational.rs:28:5
[INFO] [stdout]      |
[INFO] [stdout]   28 | use std::prelude::v1::*;
[INFO] [stdout]      |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      = help: consider adding an explicit import of `panic` to disambiguate
[INFO] [stdout]      = help: or use `self::panic` to refer to this macro unambiguously
[INFO] [stdout] note: `panic` could also refer to a macro from prelude
[INFO] [stdout]     --> /rustc/8489f1adbe1c8f8921cf18b9962cf565237a5489/library/core/src/prelude/mod.rs:41:12
[INFO] [stdout]      = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]      = note: for more information, see issue #147319 <https://github.com/rust-lang/rust/issues/147319>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `panic` is ambiguous
[INFO] [stdout]     --> src/relational.rs:1568:22
[INFO] [stdout]      |
[INFO] [stdout] 1568 |                 _ => panic!("Type not handled for {}: {:?}", field_name_string, field_type.type_id())
[INFO] [stdout]      |                      ^^^^^ ambiguous name
[INFO] [stdout]      |
[INFO] [stdout]      = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
[INFO] [stdout] note: `panic` could refer to the macro imported here
[INFO] [stdout]     --> src/relational.rs:28:5
[INFO] [stdout]      |
[INFO] [stdout]   28 | use std::prelude::v1::*;
[INFO] [stdout]      |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]      = help: consider adding an explicit import of `panic` to disambiguate
[INFO] [stdout]      = help: or use `self::panic` to refer to this macro unambiguously
[INFO] [stdout] note: `panic` could also refer to a macro from prelude
[INFO] [stdout]     --> /rustc/8489f1adbe1c8f8921cf18b9962cf565237a5489/library/core/src/prelude/mod.rs:41:12
[INFO] [stdout]      = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]      = note: for more information, see issue #147319 <https://github.com/rust-lang/rust/issues/147319>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: `panic` is ambiguous
[INFO] [stdout]    --> src/type_parsing.rs:150:38
[INFO] [stdout]     |
[INFO] [stdout] 150 | ...                   _ => panic!("Types with depth greater than one for angle bracketing not permitted")
[INFO] [stdout]     |                            ^^^^^ ambiguous name
[INFO] [stdout]     |
[INFO] [stdout]     = note: ambiguous because of a conflict between a name from a glob import and an outer scope during import or macro resolution
[INFO] [stdout] note: `panic` could refer to the macro imported here
[INFO] [stdout]    --> src/type_parsing.rs:6:5
[INFO] [stdout]     |
[INFO] [stdout]   6 | use std::prelude::v1::*;
[INFO] [stdout]     |     ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     = help: consider adding an explicit import of `panic` to disambiguate
[INFO] [stdout]     = help: or use `self::panic` to refer to this macro unambiguously
[INFO] [stdout] note: `panic` could also refer to a macro from prelude
[INFO] [stdout]    --> /rustc/8489f1adbe1c8f8921cf18b9962cf565237a5489/library/core/src/prelude/mod.rs:41:12
[INFO] [stdout]     = warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
[INFO] [stdout]     = note: for more information, see issue #147319 <https://github.com/rust-lang/rust/issues/147319>
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find `Serialize` in `serde`
[INFO] [stdout]    --> tests/test_helpers.rs:74:33
[INFO] [stdout]     |
[INFO] [stdout]  74 | #[derive(Debug, Default, serde::Serialize, serde::Deserialize)]
[INFO] [stdout]     |                                 ^^^^^^^^^ could not find `Serialize` in `serde`
[INFO] [stdout]     |
[INFO] [stdout] note: found an item that was configured out
[INFO] [stdout]    --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/serde-1.0.228/src/lib.rs:279:37
[INFO] [stdout]     |
[INFO] [stdout] 277 | #[cfg(feature = "serde_derive")]
[INFO] [stdout]     |       ------------------------ the item is gated behind the `serde_derive` feature
[INFO] [stdout] 278 | #[cfg_attr(docsrs, doc(cfg(feature = "derive")))]
[INFO] [stdout] 279 | pub use serde_derive::{Deserialize, Serialize};
[INFO] [stdout]     |                                     ^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find `Deserialize` in `serde`
[INFO] [stdout]    --> tests/test_helpers.rs:74:51
[INFO] [stdout]     |
[INFO] [stdout]  74 | #[derive(Debug, Default, serde::Serialize, serde::Deserialize)]
[INFO] [stdout]     |                                                   ^^^^^^^^^^^ could not find `Deserialize` in `serde`
[INFO] [stdout]     |
[INFO] [stdout] note: found an item that was configured out
[INFO] [stdout]    --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/serde-1.0.228/src/lib.rs:279:24
[INFO] [stdout]     |
[INFO] [stdout] 277 | #[cfg(feature = "serde_derive")]
[INFO] [stdout]     |       ------------------------ the item is gated behind the `serde_derive` feature
[INFO] [stdout] 278 | #[cfg_attr(docsrs, doc(cfg(feature = "derive")))]
[INFO] [stdout] 279 | pub use serde_derive::{Deserialize, Serialize};
[INFO] [stdout]     |                        ^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] Table name generated: TypeDemos
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: is_active
[INFO] [stdout] Full type string: bool
[INFO] [stdout] Base type string: bool
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: description
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: small_number
[INFO] [stdout] Full type string: i16
[INFO] [stdout] Base type string: i16
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: medium_number
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: large_number
[INFO] [stdout] Full type string: i64
[INFO] [stdout] Base type string: i64
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: temperature
[INFO] [stdout] Full type string: f32
[INFO] [stdout] Base type string: f32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: precise_value
[INFO] [stdout] Full type string: f64
[INFO] [stdout] Base type string: f64
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: binary_data
[INFO] [stdout] Full type string: Vec<u8>
[INFO] [stdout] Base type string: Vec
[INFO] [stdout] Full sub type string: u8
[INFO] [stdout] Base Sub type string: u8
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: optional_text
[INFO] [stdout] Full type string: Option<String>
[INFO] [stdout] Base type string: Option
[INFO] [stdout] Full sub type string: String
[INFO] [stdout] Base Sub type string: String
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: optional_number
[INFO] [stdout] Full type string: Option<i32>
[INFO] [stdout] Base type string: Option
[INFO] [stdout] Full sub type string: i32
[INFO] [stdout] Base Sub type string: i32
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: optional_flag
[INFO] [stdout] Full type string: Option<bool>
[INFO] [stdout] Base type string: Option
[INFO] [stdout] Full sub type string: bool
[INFO] [stdout] Base Sub type string: bool
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] error[E0432]: unresolved import `product_os_store`
[INFO] [stdout]   --> examples/type_mapping.rs:16:5
[INFO] [stdout]    |
[INFO] [stdout] 16 | use product_os_store::ProductOSRelationalObject;
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] Table name generated: Users
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: name
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: active
[INFO] [stdout] Full type string: bool
[INFO] [stdout] Base type string: bool
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: Users
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: name
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: Posts
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: user_id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: title
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: Users
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: Users
[INFO] [stdout] Field: name
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: email
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: Users
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: email
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: Users
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: name
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: Flags
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: enabled
[INFO] [stdout] Full type string: bool
[INFO] [stdout] Base type string: bool
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: active
[INFO] [stdout] Full type string: Option<bool>
[INFO] [stdout] Base type string: Option
[INFO] [stdout] Full sub type string: bool
[INFO] [stdout] Base Sub type string: bool
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: Products
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: name
[INFO] [stdout] Table name generated: Texts
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: name
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: description
[INFO] [stdout] Full type string: Option<String>
[INFO] [stdout] Base type string: Option
[INFO] [stdout] Full sub type string: String
[INFO] [stdout] Base Sub type string: String
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: Categories
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: name
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: ByteDatas
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]   --> tests/test_helpers.rs:96:8
[INFO] [stdout]    |
[INFO] [stdout] 96 |     T: product_os_store::ProductOSRelationalObject
[INFO] [stdout]    |        ^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] For more information about this error, try `rustc --explain E0433`.
[INFO] [stdout] 
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: byte_val
[INFO] [stdout] Full type string: u8
[INFO] [stdout] Base type string: u8
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: optional_byte
[INFO] [stdout] Full type string: Option<u8>
[INFO] [stdout] Base type string: Option
[INFO] [stdout] Full sub type string: u8
[INFO] [stdout] Base Sub type string: u8
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Table name generated: Data
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: value
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: SmallInts
[INFO] [stdout] Table name generated: User
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: name
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: Users
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: name
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: value
[INFO] [stdout] Full type string: u16
[INFO] [stdout] Base type string: u16
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: optional_value
[INFO] [stdout] Full type string: Option<u16>
[INFO] [stdout] Base type string: Option
[INFO] [stdout] Full sub type string: u16
[INFO] [stdout] Base Sub type string: u16
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: IntDatas
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: value
[INFO] [stdout] Full type string: u32
[INFO] [stdout] Base type string: u32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: optional_value
[INFO] [stdout] Full type string: Option<u32>
[INFO] [stdout] Base type string: Option
[INFO] [stdout] Full sub type string: u32
[INFO] [stdout] Base Sub type string: u32
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: SmallInts
[INFO] [stdout] Field: id
[INFO] [stdout] Table name generated: Users
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: value
[INFO] [stdout] Full type string: i16
[INFO] [stdout] Base type string: i16
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: optional_value
[INFO] [stdout] Full type string: Option<i16>
[INFO] [stdout] Base type string: Option
[INFO] [stdout] Full sub type string: i16
[INFO] [stdout] Base Sub type string: i16
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: UserProfiles
[INFO] [stdout] Field: name
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Field: email
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: active
[INFO] [stdout] Full type string: bool
[INFO] [stdout] Base type string: bool
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: phone
[INFO] [stdout] Full type string: Option<String>
[INFO] [stdout] Base type string: Option
[INFO] [stdout] Full sub type string: String
[INFO] [stdout] Base Sub type string: String
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: IntDatas
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: value
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: optional_value
[INFO] [stdout] Field: user_id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: UserData
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Full type string: Option<i32>
[INFO] [stdout] Base type string: Option
[INFO] [stdout] Full sub type string: i32
[INFO] [stdout] Base Sub type string: i32
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: BigInts
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Field: user_id
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: value
[INFO] [stdout] Full type string: i64
[INFO] [stdout] Base type string: i64
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: optional_value
[INFO] [stdout] Full type string: Option<i64>
[INFO] [stdout] Base type string: Option
[INFO] [stdout] Full sub type string: i64
[INFO] [stdout] Base Sub type string: i64
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: Xs
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: value
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] error[E0432]: unresolved import `product_os_store`
[INFO] [stdout]   --> examples/basic_usage.rs:17:5
[INFO] [stdout]    |
[INFO] [stdout] 17 | use product_os_store::ProductOSRelationalObject;
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] Table name generated: FloatDatas
[INFO] [stdout] Field: id
[INFO] [stdout] Table name generated: APIs
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Field: id
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: value
[INFO] [stdout] Full type string: f32
[INFO] [stdout] Field: endpoint
[INFO] [stdout] Base type string: f32
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: optional_value
[INFO] [stdout] Full type string: Option<f32>
[INFO] [stdout] Base type string: Option
[INFO] [stdout] Full sub type string: f32
[INFO] [stdout] Base Sub type string: f32
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: Organizations
[INFO] [stdout] Table name generated: Statuses
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: name
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: name
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: description
[INFO] [stdout] Full type string: Option<String>
[INFO] [stdout] Base type string: Option
[INFO] [stdout] Full sub type string: String
[INFO] [stdout] Base Sub type string: String
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: DoubleDatas
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: value
[INFO] [stdout] Full type string: f64
[INFO] [stdout] Base type string: f64
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: optional_value
[INFO] [stdout] Full type string: Option<f64>
[INFO] [stdout] Table name generated: Users
[INFO] [stdout] Base type string: Option
[INFO] [stdout] Full sub type string: f64
[INFO] [stdout] Base Sub type string: f64
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: Companies
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: name
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: email
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: username
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: organization_id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: full_name
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: phone
[INFO] [stdout] Full type string: Option<String>
[INFO] [stdout] Base type string: Option
[INFO] [stdout] Full sub type string: String
[INFO] [stdout] Base Sub type string: String
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: is_active
[INFO] [stdout] Full type string: bool
[INFO] [stdout] Base type string: bool
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: BinaryDatas
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: data
[INFO] [stdout] Full type string: Vec<u8>
[INFO] [stdout] Base type string: Vec
[INFO] [stdout] Full sub type string: u8
[INFO] [stdout] Base Sub type string: u8
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: optional_data
[INFO] [stdout] Table name generated: History
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: event
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Full type string: Option<Vec<u8>>
[INFO] [stdout] Base type string: Option
[INFO] [stdout] Full sub type string: Vec<u8>
[INFO] [stdout] Base Sub type string: Vec
[INFO] [stdout] Full sub type 2 string: u8
[INFO] [stdout] Base Sub 2 type string: u8
[INFO] [stdout] Table name generated: ListDatas
[INFO] [stdout] Table name generated: Branches
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: Posts
[INFO] [stdout] Field: id
[INFO] [stdout] Field: name
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: Person
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: author_id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: title
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: content
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: slug
[INFO] [stdout] Full type string: Option<String>
[INFO] [stdout] Base type string: Option
[INFO] [stdout] Full sub type string: String
[INFO] [stdout] Base Sub type string: String
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: name
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: tags
[INFO] [stdout] Full type string: Vec<String>
[INFO] [stdout] Base type string: Vec
[INFO] [stdout] Full sub type string: String
[INFO] [stdout] Base Sub type string: String
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: numbers
[INFO] [stdout] Full type string: Vec<i32>
[INFO] [stdout] Base type string: Vec
[INFO] [stdout] Full sub type string: i32
[INFO] [stdout] Base Sub type string: i32
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: published
[INFO] [stdout] Full type string: bool
[INFO] [stdout] Base type string: bool
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: UuidDatas
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: uuid
[INFO] [stdout] Full type string: Uuid
[INFO] [stdout] Base type string: Uuid
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: optional_uuid
[INFO] [stdout] Full type string: Option<Uuid>
[INFO] [stdout] Base type string: Option
[INFO] [stdout] Full sub type string: Uuid
[INFO] [stdout] Base Sub type string: Uuid
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] error[E0432]: unresolved import `product_os_store`
[INFO] [stdout]  --> tests/table_naming_tests.rs:6:5
[INFO] [stdout]   |
[INFO] [stdout] 6 | use product_os_store::{ProductOSRelationalObject, RelationalRow};
[INFO] [stdout]   |     ^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]   |
[INFO] [stdout]   = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] Table name generated: JsonDatas
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: data
[INFO] [stdout] Full type string: Value
[INFO] [stdout] Base type string: Value
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: optional_data
[INFO] [stdout] Full type string: Option<Value>
[INFO] [stdout] Base type string: Option
[INFO] [stdout] Full sub type string: Value
[INFO] [stdout] Base Sub type string: Value
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: CustomDatas
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]   --> examples/type_mapping.rs:19:10
[INFO] [stdout]    |
[INFO] [stdout] 19 | #[derive(ProductOSRelational, Debug, Default, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: custom
[INFO] [stdout] Full type string: CustomType
[INFO] [stdout] Base type string: CustomType
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Base field mapping type: TokenStream [Ident { ident: "CustomType", span: #0 bytes(7783..7793) }]
[INFO] [stdout] Field: optional_custom
[INFO] [stdout] Full type string: Option<CustomType>
[INFO] [stdout] Base type string: Option
[INFO] [stdout] Full sub type string: CustomType
[INFO] [stdout] Base Sub type string: CustomType
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: Completes
[INFO] [stdout] error[E0432]: unresolved import `product_os_store`
[INFO] [stdout]   --> examples/constraints.rs:16:5
[INFO] [stdout]    |
[INFO] [stdout] 16 | use product_os_store::ProductOSRelationalObject;
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: name
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: Optionals
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: optional_string
[INFO] [stdout] Full type string: Option<String>
[INFO] [stdout] Base type string: Option
[INFO] [stdout] Full sub type string: String
[INFO] [stdout] Base Sub type string: String
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: optional_int
[INFO] [stdout] Full type string: Option<i32>
[INFO] [stdout] Base type string: Option
[INFO] [stdout] Full sub type string: i32
[INFO] [stdout] Base Sub type string: i32
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: optional_bool
[INFO] [stdout] Full type string: Option<bool>
[INFO] [stdout] Base type string: Option
[INFO] [stdout] Full sub type string: bool
[INFO] [stdout] Base Sub type string: bool
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: optional_float
[INFO] [stdout] Full type string: Option<f64>
[INFO] [stdout] Base type string: Option
[INFO] [stdout] Full sub type string: f64
[INFO] [stdout] Base Sub type string: f64
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] error[E0432]: unresolved import `product_os_store`
[INFO] [stdout]  --> tests/derive_macro_tests.rs:7:5
[INFO] [stdout]   |
[INFO] [stdout] 7 | use product_os_store::{ProductOSRelationalObject, RelationalRow};
[INFO] [stdout]   |     ^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]   |
[INFO] [stdout]   = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0432]: unresolved import `product_os_store`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:368:9
[INFO] [stdout]     |
[INFO] [stdout] 368 |     use product_os_store::Expression;
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0432]: unresolved import `product_os_store`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:373:9
[INFO] [stdout]     |
[INFO] [stdout] 373 |     use product_os_store::Fields;
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0432]: unresolved import `product_os_store`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:386:9
[INFO] [stdout]     |
[INFO] [stdout] 386 |     use product_os_store::{Target, Action};
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find `Serialize` in `serde`
[INFO] [stdout]    --> tests/test_helpers.rs:74:33
[INFO] [stdout]     |
[INFO] [stdout]  74 | #[derive(Debug, Default, serde::Serialize, serde::Deserialize)]
[INFO] [stdout]     |                                 ^^^^^^^^^ could not find `Serialize` in `serde`
[INFO] [stdout]     |
[INFO] [stdout] note: found an item that was configured out
[INFO] [stdout]    --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/serde-1.0.228/src/lib.rs:279:37
[INFO] [stdout]     |
[INFO] [stdout] 277 | #[cfg(feature = "serde_derive")]
[INFO] [stdout]     |       ------------------------ the item is gated behind the `serde_derive` feature
[INFO] [stdout] 278 | #[cfg_attr(docsrs, doc(cfg(feature = "derive")))]
[INFO] [stdout] 279 | pub use serde_derive::{Deserialize, Serialize};
[INFO] [stdout]     |                                     ^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find `Deserialize` in `serde`
[INFO] [stdout]    --> tests/test_helpers.rs:74:51
[INFO] [stdout]     |
[INFO] [stdout]  74 | #[derive(Debug, Default, serde::Serialize, serde::Deserialize)]
[INFO] [stdout]     |                                                   ^^^^^^^^^^^ could not find `Deserialize` in `serde`
[INFO] [stdout]     |
[INFO] [stdout] note: found an item that was configured out
[INFO] [stdout]    --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/serde-1.0.228/src/lib.rs:279:24
[INFO] [stdout]     |
[INFO] [stdout] 277 | #[cfg(feature = "serde_derive")]
[INFO] [stdout]     |       ------------------------ the item is gated behind the `serde_derive` feature
[INFO] [stdout] 278 | #[cfg_attr(docsrs, doc(cfg(feature = "derive")))]
[INFO] [stdout] 279 | pub use serde_derive::{Deserialize, Serialize};
[INFO] [stdout]     |                        ^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find `Serialize` in `serde`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:276:58
[INFO] [stdout]     |
[INFO] [stdout] 276 |     #[derive(ProductOSRelational, Debug, Default, serde::Serialize, serde::Deserialize)]
[INFO] [stdout]     |                                                          ^^^^^^^^^ could not find `Serialize` in `serde`
[INFO] [stdout]     |
[INFO] [stdout] note: found an item that was configured out
[INFO] [stdout]    --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/serde-1.0.228/src/lib.rs:279:37
[INFO] [stdout]     |
[INFO] [stdout] 277 | #[cfg(feature = "serde_derive")]
[INFO] [stdout]     |       ------------------------ the item is gated behind the `serde_derive` feature
[INFO] [stdout] 278 | #[cfg_attr(docsrs, doc(cfg(feature = "derive")))]
[INFO] [stdout] 279 | pub use serde_derive::{Deserialize, Serialize};
[INFO] [stdout]     |                                     ^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find `Deserialize` in `serde`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:276:76
[INFO] [stdout]     |
[INFO] [stdout] 276 |     #[derive(ProductOSRelational, Debug, Default, serde::Serialize, serde::Deserialize)]
[INFO] [stdout]     |                                                                            ^^^^^^^^^^^ could not find `Deserialize` in `serde`
[INFO] [stdout]     |
[INFO] [stdout] note: found an item that was configured out
[INFO] [stdout]    --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/serde-1.0.228/src/lib.rs:279:24
[INFO] [stdout]     |
[INFO] [stdout] 277 | #[cfg(feature = "serde_derive")]
[INFO] [stdout]     |       ------------------------ the item is gated behind the `serde_derive` feature
[INFO] [stdout] 278 | #[cfg_attr(docsrs, doc(cfg(feature = "derive")))]
[INFO] [stdout] 279 | pub use serde_derive::{Deserialize, Serialize};
[INFO] [stdout]     |                        ^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find `Serialize` in `serde`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:332:44
[INFO] [stdout]     |
[INFO] [stdout] 332 |     #[derive(Debug, Default, Clone, serde::Serialize, serde::Deserialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^ could not find `Serialize` in `serde`
[INFO] [stdout]     |
[INFO] [stdout] note: found an item that was configured out
[INFO] [stdout]    --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/serde-1.0.228/src/lib.rs:279:37
[INFO] [stdout]     |
[INFO] [stdout] 277 | #[cfg(feature = "serde_derive")]
[INFO] [stdout]     |       ------------------------ the item is gated behind the `serde_derive` feature
[INFO] [stdout] 278 | #[cfg_attr(docsrs, doc(cfg(feature = "derive")))]
[INFO] [stdout] 279 | pub use serde_derive::{Deserialize, Serialize};
[INFO] [stdout]     |                                     ^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find `Deserialize` in `serde`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:332:62
[INFO] [stdout]     |
[INFO] [stdout] 332 |     #[derive(Debug, Default, Clone, serde::Serialize, serde::Deserialize)]
[INFO] [stdout]     |                                                              ^^^^^^^^^^^ could not find `Deserialize` in `serde`
[INFO] [stdout]     |
[INFO] [stdout] note: found an item that was configured out
[INFO] [stdout]    --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/serde-1.0.228/src/lib.rs:279:24
[INFO] [stdout]     |
[INFO] [stdout] 277 | #[cfg(feature = "serde_derive")]
[INFO] [stdout]     |       ------------------------ the item is gated behind the `serde_derive` feature
[INFO] [stdout] 278 | #[cfg_attr(docsrs, doc(cfg(feature = "derive")))]
[INFO] [stdout] 279 | pub use serde_derive::{Deserialize, Serialize};
[INFO] [stdout]     |                        ^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]   --> examples/basic_usage.rs:20:10
[INFO] [stdout]    |
[INFO] [stdout] 20 | #[derive(ProductOSRelational, Debug, Default, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `product-os-store-macros` (test "test_helpers") due to 3 previous errors
[INFO] [stderr] warning: build failed, waiting for other jobs to finish...
[INFO] [stdout] Table name generated: Users
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: name
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: Categories
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: name
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: Persons
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: name
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: Data
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: value
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: Metadata
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: info
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] error[E0432]: unresolved import `product_os_store`
[INFO] [stdout]   --> examples/table_naming.rs:15:5
[INFO] [stdout]    |
[INFO] [stdout] 15 | use product_os_store::ProductOSRelationalObject;
[INFO] [stdout]    |     ^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] Table name generated: TestStructs
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: TestStruct
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: Test1s
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: Test2s
[INFO] [stdout] Field: parent_id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]   --> examples/constraints.rs:19:10
[INFO] [stdout]    |
[INFO] [stdout] 19 | #[derive(ProductOSRelational, Debug, Default, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] Table name generated: Test3s
[INFO] [stdout] Field: required
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: Test4s
[INFO] [stdout] Field: email
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: TestStructs
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: name
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: TestStructs
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: TestStructs
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: TestStructs
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: TestStructs
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: TestStructs
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: TestStructs
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: TestStructs
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: TestStructs
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: TestStructs
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: TestStructs
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: TestStructs
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: TestStructs
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]   --> tests/table_naming_tests.rs:15:14
[INFO] [stdout]    |
[INFO] [stdout] 15 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]   --> tests/derive_macro_tests.rs:17:14
[INFO] [stdout]    |
[INFO] [stdout] 17 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] Table name generated: TestStructs
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: TestStructs
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: TestStructs
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: name
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: TestStructs
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: TestStructs
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: Firsts
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: Seconds
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] error[E0432]: unresolved import `product_os_store`
[INFO] [stdout]  --> tests/api_stability_tests.rs:7:5
[INFO] [stdout]   |
[INFO] [stdout] 7 | use product_os_store::{
[INFO] [stdout]   |     ^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]   |
[INFO] [stdout]   = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0432]: unresolved import `product_os_store`
[INFO] [stdout]    --> tests/api_stability_tests.rs:173:9
[INFO] [stdout]     |
[INFO] [stdout] 173 |     use product_os_store::RelationalRow;
[INFO] [stdout]     |         ^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]   --> examples/table_naming.rs:18:10
[INFO] [stdout]    |
[INFO] [stdout] 18 | #[derive(ProductOSRelational, Debug, Default, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]   --> tests/api_stability_tests.rs:15:14
[INFO] [stdout]    |
[INFO] [stdout] 15 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] Table name generated: WithIds
[INFO] [stdout] Field: name
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: active
[INFO] [stdout] Full type string: bool
[INFO] [stdout] Base type string: bool
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: WithIdentities
[INFO] [stdout] Field: name
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: active
[INFO] [stdout] Full type string: bool
[INFO] [stdout] Base type string: bool
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: WithBoths
[INFO] [stdout] Field: name
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: BoolTests
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: flag
[INFO] [stdout] Full type string: bool
[INFO] [stdout] Base type string: bool
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: StringTests
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: text
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: U8Tests
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: byte_val
[INFO] [stdout] Full type string: u8
[INFO] [stdout] Base type string: u8
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: U16Tests
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: value
[INFO] [stdout] Full type string: u16
[INFO] [stdout] Base type string: u16
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: U32Tests
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: value
[INFO] [stdout] Full type string: u32
[INFO] [stdout] Base type string: u32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: I16Tests
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: value
[INFO] [stdout] Full type string: i16
[INFO] [stdout] Base type string: i16
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: I32Tests
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: value
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: I64Tests
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: value
[INFO] [stdout] Full type string: i64
[INFO] [stdout] Base type string: i64
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: F32Tests
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: value
[INFO] [stdout] Full type string: f32
[INFO] [stdout] Base type string: f32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: F64Tests
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: value
[INFO] [stdout] Full type string: f64
[INFO] [stdout] Base type string: f64
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: VecU8Tests
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: data
[INFO] [stdout] Full type string: Vec<u8>
[INFO] [stdout] Base type string: Vec
[INFO] [stdout] Full sub type string: u8
[INFO] [stdout] Base Sub type string: u8
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: VecTests
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: tags
[INFO] [stdout] Full type string: Vec<String>
[INFO] [stdout] Base type string: Vec
[INFO] [stdout] Full sub type string: String
[INFO] [stdout] Base Sub type string: String
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: UuidTests
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: uuid
[INFO] [stdout] Full type string: Uuid
[INFO] [stdout] Base type string: Uuid
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: JsonTests
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: data
[INFO] [stdout] Full type string: Value
[INFO] [stdout] Base type string: Value
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: CustomTests
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: custom
[INFO] [stdout] Full type string: CustomData
[INFO] [stdout] Base type string: CustomData
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Base field mapping type: TokenStream [Ident { ident: "CustomData", span: #0 bytes(6586..6596) }]
[INFO] [stdout] Table name generated: OptionTests
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: optional_field
[INFO] [stdout] Full type string: Option<String>
[INFO] [stdout] Base type string: Option
[INFO] [stdout] Full sub type string: String
[INFO] [stdout] Base Sub type string: String
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: RequiredTests
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: required_field
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: PKTests
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: name
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: FKTests
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: parent_id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: NotNullTests
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: required
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: UniqueTests
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Field: email
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: Test1s
[INFO] [stdout] Field: id
[INFO] [stdout] Full type string: i32
[INFO] [stdout] Base type string: i32
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] Table name generated: Test2s
[INFO] [stdout] Field: email
[INFO] [stdout] Full type string: String
[INFO] [stdout] Base type string: String
[INFO] [stdout] Full sub type string: 
[INFO] [stdout] Base Sub type string: 
[INFO] [stdout] Full sub type 2 string: 
[INFO] [stdout] Base Sub 2 type string: 
[INFO] [stdout] error[E0432]: unresolved import `product_os_store`
[INFO] [stdout]  --> tests/field_mapping_tests.rs:6:5
[INFO] [stdout]   |
[INFO] [stdout] 6 | use product_os_store::{ProductOSRelationalObject, RelationalRow};
[INFO] [stdout]   |     ^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]   |
[INFO] [stdout]   = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find `Serialize` in `serde`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:216:58
[INFO] [stdout]     |
[INFO] [stdout] 216 |     #[derive(ProductOSRelational, Debug, Default, serde::Serialize, serde::Deserialize)]
[INFO] [stdout]     |                                                          ^^^^^^^^^ could not find `Serialize` in `serde`
[INFO] [stdout]     |
[INFO] [stdout] note: found an item that was configured out
[INFO] [stdout]    --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/serde-1.0.228/src/lib.rs:279:37
[INFO] [stdout]     |
[INFO] [stdout] 277 | #[cfg(feature = "serde_derive")]
[INFO] [stdout]     |       ------------------------ the item is gated behind the `serde_derive` feature
[INFO] [stdout] 278 | #[cfg_attr(docsrs, doc(cfg(feature = "derive")))]
[INFO] [stdout] 279 | pub use serde_derive::{Deserialize, Serialize};
[INFO] [stdout]     |                                     ^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find `Deserialize` in `serde`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:216:76
[INFO] [stdout]     |
[INFO] [stdout] 216 |     #[derive(ProductOSRelational, Debug, Default, serde::Serialize, serde::Deserialize)]
[INFO] [stdout]     |                                                                            ^^^^^^^^^^^ could not find `Deserialize` in `serde`
[INFO] [stdout]     |
[INFO] [stdout] note: found an item that was configured out
[INFO] [stdout]    --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/serde-1.0.228/src/lib.rs:279:24
[INFO] [stdout]     |
[INFO] [stdout] 277 | #[cfg(feature = "serde_derive")]
[INFO] [stdout]     |       ------------------------ the item is gated behind the `serde_derive` feature
[INFO] [stdout] 278 | #[cfg_attr(docsrs, doc(cfg(feature = "derive")))]
[INFO] [stdout] 279 | pub use serde_derive::{Deserialize, Serialize};
[INFO] [stdout]     |                        ^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find `Serialize` in `serde`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:269:44
[INFO] [stdout]     |
[INFO] [stdout] 269 |     #[derive(Debug, Default, Clone, serde::Serialize, serde::Deserialize)]
[INFO] [stdout]     |                                            ^^^^^^^^^ could not find `Serialize` in `serde`
[INFO] [stdout]     |
[INFO] [stdout] note: found an item that was configured out
[INFO] [stdout]    --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/serde-1.0.228/src/lib.rs:279:37
[INFO] [stdout]     |
[INFO] [stdout] 277 | #[cfg(feature = "serde_derive")]
[INFO] [stdout]     |       ------------------------ the item is gated behind the `serde_derive` feature
[INFO] [stdout] 278 | #[cfg_attr(docsrs, doc(cfg(feature = "derive")))]
[INFO] [stdout] 279 | pub use serde_derive::{Deserialize, Serialize};
[INFO] [stdout]     |                                     ^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find `Deserialize` in `serde`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:269:62
[INFO] [stdout]     |
[INFO] [stdout] 269 |     #[derive(Debug, Default, Clone, serde::Serialize, serde::Deserialize)]
[INFO] [stdout]     |                                                              ^^^^^^^^^^^ could not find `Deserialize` in `serde`
[INFO] [stdout]     |
[INFO] [stdout] note: found an item that was configured out
[INFO] [stdout]    --> /opt/rustwide/cargo-home/registry/src/index.crates.io-1949cf8c6b5b557f/serde-1.0.228/src/lib.rs:279:24
[INFO] [stdout]     |
[INFO] [stdout] 277 | #[cfg(feature = "serde_derive")]
[INFO] [stdout]     |       ------------------------ the item is gated behind the `serde_derive` feature
[INFO] [stdout] 278 | #[cfg_attr(docsrs, doc(cfg(feature = "derive")))]
[INFO] [stdout] 279 | pub use serde_derive::{Deserialize, Serialize};
[INFO] [stdout]     |                        ^^^^^^^^^^^
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]   --> tests/field_mapping_tests.rs:14:14
[INFO] [stdout]    |
[INFO] [stdout] 14 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]   --> examples/table_naming.rs:27:10
[INFO] [stdout]    |
[INFO] [stdout] 27 | #[derive(ProductOSRelational, Debug, Default, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]   --> tests/api_stability_tests.rs:26:14
[INFO] [stdout]    |
[INFO] [stdout] 26 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]   --> tests/field_mapping_tests.rs:30:14
[INFO] [stdout]    |
[INFO] [stdout] 30 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]   --> tests/table_naming_tests.rs:30:14
[INFO] [stdout]    |
[INFO] [stdout] 30 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]   --> tests/derive_macro_tests.rs:32:14
[INFO] [stdout]    |
[INFO] [stdout] 32 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]   --> examples/constraints.rs:33:10
[INFO] [stdout]    |
[INFO] [stdout] 33 | #[derive(ProductOSRelational, Debug, Default, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find type `RelationalRow` in this scope
[INFO] [stdout]   --> examples/type_mapping.rs:19:10
[INFO] [stdout]    |
[INFO] [stdout] 19 | #[derive(ProductOSRelational, Debug, Default, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]   --> examples/type_mapping.rs:19:10
[INFO] [stdout]    |
[INFO] [stdout] 19 | #[derive(ProductOSRelational, Debug, Default, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]   --> examples/type_mapping.rs:19:10
[INFO] [stdout]    |
[INFO] [stdout] 19 | #[derive(ProductOSRelational, Debug, Default, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] Some errors have detailed explanations: E0425, E0432, E0433.
[INFO] [stdout] 
[INFO] [stdout] For more information about an error, try `rustc --explain E0425`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `product-os-store-macros` (example "type_mapping") due to 3 previous errors; 2 warnings emitted
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]   --> tests/api_stability_tests.rs:39:14
[INFO] [stdout]    |
[INFO] [stdout] 39 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]   --> examples/table_naming.rs:36:10
[INFO] [stdout]    |
[INFO] [stdout] 36 | #[derive(ProductOSRelational, Debug, Default, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]   --> tests/derive_macro_tests.rs:48:14
[INFO] [stdout]    |
[INFO] [stdout] 48 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]   --> tests/table_naming_tests.rs:45:14
[INFO] [stdout]    |
[INFO] [stdout] 45 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find type `RelationalRow` in this scope
[INFO] [stdout]   --> examples/basic_usage.rs:20:10
[INFO] [stdout]    |
[INFO] [stdout] 20 | #[derive(ProductOSRelational, Debug, Default, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]   --> examples/basic_usage.rs:20:10
[INFO] [stdout]    |
[INFO] [stdout] 20 | #[derive(ProductOSRelational, Debug, Default, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]   --> examples/basic_usage.rs:20:10
[INFO] [stdout]    |
[INFO] [stdout] 20 | #[derive(ProductOSRelational, Debug, Default, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] Some errors have detailed explanations: E0425, E0432, E0433.
[INFO] [stdout] 
[INFO] [stdout] For more information about an error, try `rustc --explain E0425`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `product-os-store-macros` (example "basic_usage") due to 3 previous errors; 2 warnings emitted
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]   --> tests/field_mapping_tests.rs:46:14
[INFO] [stdout]    |
[INFO] [stdout] 46 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]   --> tests/api_stability_tests.rs:46:14
[INFO] [stdout]    |
[INFO] [stdout] 46 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]   --> examples/table_naming.rs:45:10
[INFO] [stdout]    |
[INFO] [stdout] 45 | #[derive(ProductOSRelational, Debug, Default, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]   --> tests/table_naming_tests.rs:60:14
[INFO] [stdout]    |
[INFO] [stdout] 60 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]   --> tests/derive_macro_tests.rs:64:14
[INFO] [stdout]    |
[INFO] [stdout] 64 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]   --> tests/field_mapping_tests.rs:62:14
[INFO] [stdout]    |
[INFO] [stdout] 62 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]   --> tests/api_stability_tests.rs:53:14
[INFO] [stdout]    |
[INFO] [stdout] 53 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]   --> examples/table_naming.rs:55:10
[INFO] [stdout]    |
[INFO] [stdout] 55 | #[derive(ProductOSRelational, Debug, Default, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]   --> tests/field_mapping_tests.rs:76:14
[INFO] [stdout]    |
[INFO] [stdout] 76 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]   --> examples/constraints.rs:63:10
[INFO] [stdout]    |
[INFO] [stdout] 63 | #[derive(ProductOSRelational, Debug, Default, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]   --> tests/table_naming_tests.rs:76:14
[INFO] [stdout]    |
[INFO] [stdout] 76 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]   --> tests/api_stability_tests.rs:60:14
[INFO] [stdout]    |
[INFO] [stdout] 60 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]   --> tests/derive_macro_tests.rs:79:14
[INFO] [stdout]    |
[INFO] [stdout] 79 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]   --> tests/field_mapping_tests.rs:90:14
[INFO] [stdout]    |
[INFO] [stdout] 90 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]   --> tests/api_stability_tests.rs:78:14
[INFO] [stdout]    |
[INFO] [stdout] 78 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/field_mapping_tests.rs:104:14
[INFO] [stdout]     |
[INFO] [stdout] 104 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]   --> tests/table_naming_tests.rs:92:14
[INFO] [stdout]    |
[INFO] [stdout] 92 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find type `RelationalRow` in this scope
[INFO] [stdout]   --> examples/table_naming.rs:18:10
[INFO] [stdout]    |
[INFO] [stdout] 18 | #[derive(ProductOSRelational, Debug, Default, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find type `RelationalRow` in this scope
[INFO] [stdout]   --> examples/table_naming.rs:27:10
[INFO] [stdout]    |
[INFO] [stdout] 27 | #[derive(ProductOSRelational, Debug, Default, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find type `RelationalRow` in this scope
[INFO] [stdout]   --> examples/table_naming.rs:36:10
[INFO] [stdout]    |
[INFO] [stdout] 36 | #[derive(ProductOSRelational, Debug, Default, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find type `RelationalRow` in this scope
[INFO] [stdout]   --> examples/table_naming.rs:45:10
[INFO] [stdout]    |
[INFO] [stdout] 45 | #[derive(ProductOSRelational, Debug, Default, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find type `RelationalRow` in this scope
[INFO] [stdout]   --> examples/table_naming.rs:55:10
[INFO] [stdout]    |
[INFO] [stdout] 55 | #[derive(ProductOSRelational, Debug, Default, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]   --> examples/table_naming.rs:18:10
[INFO] [stdout]    |
[INFO] [stdout] 18 | #[derive(ProductOSRelational, Debug, Default, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]   --> examples/table_naming.rs:18:10
[INFO] [stdout]    |
[INFO] [stdout] 18 | #[derive(ProductOSRelational, Debug, Default, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]   --> examples/table_naming.rs:27:10
[INFO] [stdout]    |
[INFO] [stdout] 27 | #[derive(ProductOSRelational, Debug, Default, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]   --> examples/table_naming.rs:27:10
[INFO] [stdout]    |
[INFO] [stdout] 27 | #[derive(ProductOSRelational, Debug, Default, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]   --> examples/table_naming.rs:36:10
[INFO] [stdout]    |
[INFO] [stdout] 36 | #[derive(ProductOSRelational, Debug, Default, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]   --> examples/table_naming.rs:36:10
[INFO] [stdout]    |
[INFO] [stdout] 36 | #[derive(ProductOSRelational, Debug, Default, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]   --> examples/table_naming.rs:45:10
[INFO] [stdout]    |
[INFO] [stdout] 45 | #[derive(ProductOSRelational, Debug, Default, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]   --> examples/table_naming.rs:45:10
[INFO] [stdout]    |
[INFO] [stdout] 45 | #[derive(ProductOSRelational, Debug, Default, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]   --> examples/table_naming.rs:55:10
[INFO] [stdout]    |
[INFO] [stdout] 55 | #[derive(ProductOSRelational, Debug, Default, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]   --> examples/table_naming.rs:55:10
[INFO] [stdout]    |
[INFO] [stdout] 55 | #[derive(ProductOSRelational, Debug, Default, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] Some errors have detailed explanations: E0425, E0432, E0433.
[INFO] [stdout] 
[INFO] [stdout] For more information about an error, try `rustc --explain E0425`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `product-os-store-macros` (example "table_naming") due to 11 previous errors; 10 warnings emitted
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]   --> tests/derive_macro_tests.rs:94:14
[INFO] [stdout]    |
[INFO] [stdout] 94 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find type `RelationalRow` in this scope
[INFO] [stdout]   --> examples/constraints.rs:19:10
[INFO] [stdout]    |
[INFO] [stdout] 19 | #[derive(ProductOSRelational, Debug, Default, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find type `RelationalRow` in this scope
[INFO] [stdout]   --> examples/constraints.rs:33:10
[INFO] [stdout]    |
[INFO] [stdout] 33 | #[derive(ProductOSRelational, Debug, Default, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0425]: cannot find type `RelationalRow` in this scope
[INFO] [stdout]   --> examples/constraints.rs:63:10
[INFO] [stdout]    |
[INFO] [stdout] 63 | #[derive(ProductOSRelational, Debug, Default, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^^^^^^^^^^^ not found in this scope
[INFO] [stdout]    |
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]   --> examples/constraints.rs:19:10
[INFO] [stdout]    |
[INFO] [stdout] 19 | #[derive(ProductOSRelational, Debug, Default, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]   --> examples/constraints.rs:19:10
[INFO] [stdout]    |
[INFO] [stdout] 19 | #[derive(ProductOSRelational, Debug, Default, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]   --> examples/constraints.rs:33:10
[INFO] [stdout]    |
[INFO] [stdout] 33 | #[derive(ProductOSRelational, Debug, Default, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]   --> examples/constraints.rs:33:10
[INFO] [stdout]    |
[INFO] [stdout] 33 | #[derive(ProductOSRelational, Debug, Default, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]   --> examples/constraints.rs:63:10
[INFO] [stdout]    |
[INFO] [stdout] 63 | #[derive(ProductOSRelational, Debug, Default, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]   --> examples/constraints.rs:63:10
[INFO] [stdout]    |
[INFO] [stdout] 63 | #[derive(ProductOSRelational, Debug, Default, Clone)]
[INFO] [stdout]    |          ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] Some errors have detailed explanations: E0425, E0432, E0433.
[INFO] [stdout] 
[INFO] [stdout] For more information about an error, try `rustc --explain E0425`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `product-os-store-macros` (example "constraints") due to 7 previous errors; 6 warnings emitted
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/field_mapping_tests.rs:118:14
[INFO] [stdout]     |
[INFO] [stdout] 118 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]   --> tests/api_stability_tests.rs:93:14
[INFO] [stdout]    |
[INFO] [stdout] 93 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]    = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/table_naming_tests.rs:108:14
[INFO] [stdout]     |
[INFO] [stdout] 108 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/derive_macro_tests.rs:111:14
[INFO] [stdout]     |
[INFO] [stdout] 111 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/table_naming_tests.rs:123:14
[INFO] [stdout]     |
[INFO] [stdout] 123 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/field_mapping_tests.rs:132:14
[INFO] [stdout]     |
[INFO] [stdout] 132 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/api_stability_tests.rs:105:14
[INFO] [stdout]     |
[INFO] [stdout] 105 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/field_mapping_tests.rs:146:14
[INFO] [stdout]     |
[INFO] [stdout] 146 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/derive_macro_tests.rs:126:14
[INFO] [stdout]     |
[INFO] [stdout] 126 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/api_stability_tests.rs:119:14
[INFO] [stdout]     |
[INFO] [stdout] 119 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/table_naming_tests.rs:139:14
[INFO] [stdout]     |
[INFO] [stdout] 139 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/field_mapping_tests.rs:160:14
[INFO] [stdout]     |
[INFO] [stdout] 160 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/derive_macro_tests.rs:141:14
[INFO] [stdout]     |
[INFO] [stdout] 141 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/api_stability_tests.rs:137:14
[INFO] [stdout]     |
[INFO] [stdout] 137 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/table_naming_tests.rs:154:14
[INFO] [stdout]     |
[INFO] [stdout] 154 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/field_mapping_tests.rs:174:14
[INFO] [stdout]     |
[INFO] [stdout] 174 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/api_stability_tests.rs:156:14
[INFO] [stdout]     |
[INFO] [stdout] 156 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/derive_macro_tests.rs:156:14
[INFO] [stdout]     |
[INFO] [stdout] 156 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/table_naming_tests.rs:169:14
[INFO] [stdout]     |
[INFO] [stdout] 169 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/api_stability_tests.rs:168:14
[INFO] [stdout]     |
[INFO] [stdout] 168 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/field_mapping_tests.rs:188:14
[INFO] [stdout]     |
[INFO] [stdout] 188 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/table_naming_tests.rs:184:14
[INFO] [stdout]     |
[INFO] [stdout] 184 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/derive_macro_tests.rs:171:14
[INFO] [stdout]     |
[INFO] [stdout] 171 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/field_mapping_tests.rs:202:14
[INFO] [stdout]     |
[INFO] [stdout] 202 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/api_stability_tests.rs:182:14
[INFO] [stdout]     |
[INFO] [stdout] 182 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/table_naming_tests.rs:199:14
[INFO] [stdout]     |
[INFO] [stdout] 199 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/api_stability_tests.rs:195:14
[INFO] [stdout]     |
[INFO] [stdout] 195 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/derive_macro_tests.rs:186:14
[INFO] [stdout]     |
[INFO] [stdout] 186 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/field_mapping_tests.rs:216:14
[INFO] [stdout]     |
[INFO] [stdout] 216 |     #[derive(ProductOSRelational, Debug, Default, serde::Serialize, serde::Deserialize)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/api_stability_tests.rs:208:14
[INFO] [stdout]     |
[INFO] [stdout] 208 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/table_naming_tests.rs:215:14
[INFO] [stdout]     |
[INFO] [stdout] 215 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/derive_macro_tests.rs:201:14
[INFO] [stdout]     |
[INFO] [stdout] 201 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/api_stability_tests.rs:221:14
[INFO] [stdout]     |
[INFO] [stdout] 221 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/field_mapping_tests.rs:241:14
[INFO] [stdout]     |
[INFO] [stdout] 241 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/table_naming_tests.rs:230:14
[INFO] [stdout]     |
[INFO] [stdout] 230 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/field_mapping_tests.rs:255:14
[INFO] [stdout]     |
[INFO] [stdout] 255 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/api_stability_tests.rs:234:14
[INFO] [stdout]     |
[INFO] [stdout] 234 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/derive_macro_tests.rs:216:14
[INFO] [stdout]     |
[INFO] [stdout] 216 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]   --> tests/table_naming_tests.rs:15:14
[INFO] [stdout]    |
[INFO] [stdout] 15 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]   --> tests/table_naming_tests.rs:15:14
[INFO] [stdout]    |
[INFO] [stdout] 15 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]   --> tests/table_naming_tests.rs:30:14
[INFO] [stdout]    |
[INFO] [stdout] 30 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]   --> tests/table_naming_tests.rs:30:14
[INFO] [stdout]    |
[INFO] [stdout] 30 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]   --> tests/table_naming_tests.rs:45:14
[INFO] [stdout]    |
[INFO] [stdout] 45 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]   --> tests/table_naming_tests.rs:45:14
[INFO] [stdout]    |
[INFO] [stdout] 45 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]   --> tests/table_naming_tests.rs:60:14
[INFO] [stdout]    |
[INFO] [stdout] 60 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]   --> tests/table_naming_tests.rs:60:14
[INFO] [stdout]    |
[INFO] [stdout] 60 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]   --> tests/table_naming_tests.rs:76:14
[INFO] [stdout]    |
[INFO] [stdout] 76 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]   --> tests/table_naming_tests.rs:76:14
[INFO] [stdout]    |
[INFO] [stdout] 76 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]   --> tests/table_naming_tests.rs:92:14
[INFO] [stdout]    |
[INFO] [stdout] 92 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]   --> tests/table_naming_tests.rs:92:14
[INFO] [stdout]    |
[INFO] [stdout] 92 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/table_naming_tests.rs:108:14
[INFO] [stdout]     |
[INFO] [stdout] 108 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/table_naming_tests.rs:108:14
[INFO] [stdout]     |
[INFO] [stdout] 108 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/table_naming_tests.rs:123:14
[INFO] [stdout]     |
[INFO] [stdout] 123 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/table_naming_tests.rs:123:14
[INFO] [stdout]     |
[INFO] [stdout] 123 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/table_naming_tests.rs:139:14
[INFO] [stdout]     |
[INFO] [stdout] 139 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/table_naming_tests.rs:139:14
[INFO] [stdout]     |
[INFO] [stdout] 139 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/table_naming_tests.rs:154:14
[INFO] [stdout]     |
[INFO] [stdout] 154 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/table_naming_tests.rs:154:14
[INFO] [stdout]     |
[INFO] [stdout] 154 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/table_naming_tests.rs:169:14
[INFO] [stdout]     |
[INFO] [stdout] 169 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/table_naming_tests.rs:169:14
[INFO] [stdout]     |
[INFO] [stdout] 169 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/table_naming_tests.rs:184:14
[INFO] [stdout]     |
[INFO] [stdout] 184 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/table_naming_tests.rs:184:14
[INFO] [stdout]     |
[INFO] [stdout] 184 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/table_naming_tests.rs:199:14
[INFO] [stdout]     |
[INFO] [stdout] 199 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/table_naming_tests.rs:199:14
[INFO] [stdout]     |
[INFO] [stdout] 199 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/table_naming_tests.rs:215:14
[INFO] [stdout]     |
[INFO] [stdout] 215 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/table_naming_tests.rs:215:14
[INFO] [stdout]     |
[INFO] [stdout] 215 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/table_naming_tests.rs:230:14
[INFO] [stdout]     |
[INFO] [stdout] 230 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/table_naming_tests.rs:230:14
[INFO] [stdout]     |
[INFO] [stdout] 230 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `product-os-store-macros` (test "table_naming_tests") due to 16 previous errors; 30 warnings emitted
[INFO] [stdout] Some errors have detailed explanations: E0432, E0433.
[INFO] [stdout] 
[INFO] [stdout] For more information about an error, try `rustc --explain E0432`.
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/field_mapping_tests.rs:274:14
[INFO] [stdout]     |
[INFO] [stdout] 274 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/api_stability_tests.rs:248:14
[INFO] [stdout]     |
[INFO] [stdout] 248 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/derive_macro_tests.rs:231:14
[INFO] [stdout]     |
[INFO] [stdout] 231 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/field_mapping_tests.rs:288:14
[INFO] [stdout]     |
[INFO] [stdout] 288 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/api_stability_tests.rs:267:14
[INFO] [stdout]     |
[INFO] [stdout] 267 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/field_mapping_tests.rs:303:14
[INFO] [stdout]     |
[INFO] [stdout] 303 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/derive_macro_tests.rs:246:14
[INFO] [stdout]     |
[INFO] [stdout] 246 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/api_stability_tests.rs:281:14
[INFO] [stdout]     |
[INFO] [stdout] 281 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/field_mapping_tests.rs:318:14
[INFO] [stdout]     |
[INFO] [stdout] 318 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/derive_macro_tests.rs:261:14
[INFO] [stdout]     |
[INFO] [stdout] 261 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/api_stability_tests.rs:297:14
[INFO] [stdout]     |
[INFO] [stdout] 297 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/derive_macro_tests.rs:276:14
[INFO] [stdout]     |
[INFO] [stdout] 276 |     #[derive(ProductOSRelational, Debug, Default, serde::Serialize, serde::Deserialize)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/field_mapping_tests.rs:333:14
[INFO] [stdout]     |
[INFO] [stdout] 333 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/api_stability_tests.rs:338:14
[INFO] [stdout]     |
[INFO] [stdout] 338 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/derive_macro_tests.rs:302:14
[INFO] [stdout]     |
[INFO] [stdout] 302 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/api_stability_tests.rs:350:14
[INFO] [stdout]     |
[INFO] [stdout] 350 |     #[derive(ProductOSRelational, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/field_mapping_tests.rs:348:14
[INFO] [stdout]     |
[INFO] [stdout] 348 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/api_stability_tests.rs:369:14
[INFO] [stdout]     |
[INFO] [stdout] 369 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/derive_macro_tests.rs:317:14
[INFO] [stdout]     |
[INFO] [stdout] 317 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/field_mapping_tests.rs:363:14
[INFO] [stdout]     |
[INFO] [stdout] 363 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/api_stability_tests.rs:374:14
[INFO] [stdout]     |
[INFO] [stdout] 374 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/derive_macro_tests.rs:338:14
[INFO] [stdout]     |
[INFO] [stdout] 338 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/field_mapping_tests.rs:403:14
[INFO] [stdout]     |
[INFO] [stdout] 403 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]   --> tests/api_stability_tests.rs:15:14
[INFO] [stdout]    |
[INFO] [stdout] 15 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]   --> tests/api_stability_tests.rs:15:14
[INFO] [stdout]    |
[INFO] [stdout] 15 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]   --> tests/api_stability_tests.rs:26:14
[INFO] [stdout]    |
[INFO] [stdout] 26 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]   --> tests/api_stability_tests.rs:26:14
[INFO] [stdout]    |
[INFO] [stdout] 26 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]   --> tests/api_stability_tests.rs:39:14
[INFO] [stdout]    |
[INFO] [stdout] 39 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]   --> tests/api_stability_tests.rs:39:14
[INFO] [stdout]    |
[INFO] [stdout] 39 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]   --> tests/api_stability_tests.rs:46:14
[INFO] [stdout]    |
[INFO] [stdout] 46 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]   --> tests/api_stability_tests.rs:46:14
[INFO] [stdout]    |
[INFO] [stdout] 46 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]   --> tests/api_stability_tests.rs:53:14
[INFO] [stdout]    |
[INFO] [stdout] 53 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]   --> tests/api_stability_tests.rs:53:14
[INFO] [stdout]    |
[INFO] [stdout] 53 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]   --> tests/api_stability_tests.rs:60:14
[INFO] [stdout]    |
[INFO] [stdout] 60 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]   --> tests/api_stability_tests.rs:60:14
[INFO] [stdout]    |
[INFO] [stdout] 60 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]   --> tests/api_stability_tests.rs:78:14
[INFO] [stdout]    |
[INFO] [stdout] 78 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]   --> tests/api_stability_tests.rs:78:14
[INFO] [stdout]    |
[INFO] [stdout] 78 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]   --> tests/api_stability_tests.rs:93:14
[INFO] [stdout]    |
[INFO] [stdout] 93 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]   --> tests/api_stability_tests.rs:93:14
[INFO] [stdout]    |
[INFO] [stdout] 93 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/api_stability_tests.rs:105:14
[INFO] [stdout]     |
[INFO] [stdout] 105 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/api_stability_tests.rs:105:14
[INFO] [stdout]     |
[INFO] [stdout] 105 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/api_stability_tests.rs:119:14
[INFO] [stdout]     |
[INFO] [stdout] 119 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/api_stability_tests.rs:119:14
[INFO] [stdout]     |
[INFO] [stdout] 119 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/api_stability_tests.rs:137:14
[INFO] [stdout]     |
[INFO] [stdout] 137 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/api_stability_tests.rs:137:14
[INFO] [stdout]     |
[INFO] [stdout] 137 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/api_stability_tests.rs:156:14
[INFO] [stdout]     |
[INFO] [stdout] 156 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/api_stability_tests.rs:156:14
[INFO] [stdout]     |
[INFO] [stdout] 156 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/api_stability_tests.rs:168:14
[INFO] [stdout]     |
[INFO] [stdout] 168 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/api_stability_tests.rs:168:14
[INFO] [stdout]     |
[INFO] [stdout] 168 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/api_stability_tests.rs:182:14
[INFO] [stdout]     |
[INFO] [stdout] 182 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/api_stability_tests.rs:182:14
[INFO] [stdout]     |
[INFO] [stdout] 182 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/api_stability_tests.rs:195:14
[INFO] [stdout]     |
[INFO] [stdout] 195 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/api_stability_tests.rs:195:14
[INFO] [stdout]     |
[INFO] [stdout] 195 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/api_stability_tests.rs:208:14
[INFO] [stdout]     |
[INFO] [stdout] 208 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/api_stability_tests.rs:208:14
[INFO] [stdout]     |
[INFO] [stdout] 208 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/api_stability_tests.rs:221:14
[INFO] [stdout]     |
[INFO] [stdout] 221 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/api_stability_tests.rs:221:14
[INFO] [stdout]     |
[INFO] [stdout] 221 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/api_stability_tests.rs:234:14
[INFO] [stdout]     |
[INFO] [stdout] 234 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/api_stability_tests.rs:234:14
[INFO] [stdout]     |
[INFO] [stdout] 234 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/api_stability_tests.rs:248:14
[INFO] [stdout]     |
[INFO] [stdout] 248 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/api_stability_tests.rs:248:14
[INFO] [stdout]     |
[INFO] [stdout] 248 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/api_stability_tests.rs:267:14
[INFO] [stdout]     |
[INFO] [stdout] 267 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/api_stability_tests.rs:267:14
[INFO] [stdout]     |
[INFO] [stdout] 267 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/api_stability_tests.rs:281:14
[INFO] [stdout]     |
[INFO] [stdout] 281 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/api_stability_tests.rs:281:14
[INFO] [stdout]     |
[INFO] [stdout] 281 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/api_stability_tests.rs:297:14
[INFO] [stdout]     |
[INFO] [stdout] 297 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/api_stability_tests.rs:297:14
[INFO] [stdout]     |
[INFO] [stdout] 297 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/api_stability_tests.rs:338:14
[INFO] [stdout]     |
[INFO] [stdout] 338 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/api_stability_tests.rs:338:14
[INFO] [stdout]     |
[INFO] [stdout] 338 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/api_stability_tests.rs:350:14
[INFO] [stdout]     |
[INFO] [stdout] 350 |     #[derive(ProductOSRelational, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/api_stability_tests.rs:350:14
[INFO] [stdout]     |
[INFO] [stdout] 350 |     #[derive(ProductOSRelational, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/api_stability_tests.rs:369:14
[INFO] [stdout]     |
[INFO] [stdout] 369 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/api_stability_tests.rs:369:14
[INFO] [stdout]     |
[INFO] [stdout] 369 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/api_stability_tests.rs:374:14
[INFO] [stdout]     |
[INFO] [stdout] 374 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/api_stability_tests.rs:374:14
[INFO] [stdout]     |
[INFO] [stdout] 374 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] Some errors have detailed explanations: E0432, E0433.
[INFO] [stdout] 
[INFO] [stdout] For more information about an error, try `rustc --explain E0432`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `product-os-store-macros` (test "api_stability_tests") due to 28 previous errors; 52 warnings emitted
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/field_mapping_tests.rs:410:14
[INFO] [stdout]     |
[INFO] [stdout] 410 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/derive_macro_tests.rs:353:14
[INFO] [stdout]     |
[INFO] [stdout] 353 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused imports: `DateTime` and `Utc`
[INFO] [stdout]  --> tests/field_mapping_tests.rs:7:14
[INFO] [stdout]   |
[INFO] [stdout] 7 | use chrono::{DateTime, Utc};
[INFO] [stdout]   |              ^^^^^^^^  ^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: `#[warn(unused_imports)]` (part of `#[warn(unused)]`) on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]   --> tests/field_mapping_tests.rs:14:14
[INFO] [stdout]    |
[INFO] [stdout] 14 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]   --> tests/field_mapping_tests.rs:14:14
[INFO] [stdout]    |
[INFO] [stdout] 14 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]   --> tests/field_mapping_tests.rs:30:14
[INFO] [stdout]    |
[INFO] [stdout] 30 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]   --> tests/field_mapping_tests.rs:30:14
[INFO] [stdout]    |
[INFO] [stdout] 30 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]   --> tests/field_mapping_tests.rs:46:14
[INFO] [stdout]    |
[INFO] [stdout] 46 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]   --> tests/field_mapping_tests.rs:46:14
[INFO] [stdout]    |
[INFO] [stdout] 46 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]   --> tests/field_mapping_tests.rs:62:14
[INFO] [stdout]    |
[INFO] [stdout] 62 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]   --> tests/field_mapping_tests.rs:62:14
[INFO] [stdout]    |
[INFO] [stdout] 62 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]   --> tests/field_mapping_tests.rs:76:14
[INFO] [stdout]    |
[INFO] [stdout] 76 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]   --> tests/field_mapping_tests.rs:76:14
[INFO] [stdout]    |
[INFO] [stdout] 76 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]   --> tests/field_mapping_tests.rs:90:14
[INFO] [stdout]    |
[INFO] [stdout] 90 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]   --> tests/field_mapping_tests.rs:90:14
[INFO] [stdout]    |
[INFO] [stdout] 90 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:104:14
[INFO] [stdout]     |
[INFO] [stdout] 104 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:104:14
[INFO] [stdout]     |
[INFO] [stdout] 104 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:118:14
[INFO] [stdout]     |
[INFO] [stdout] 118 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:118:14
[INFO] [stdout]     |
[INFO] [stdout] 118 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:132:14
[INFO] [stdout]     |
[INFO] [stdout] 132 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:132:14
[INFO] [stdout]     |
[INFO] [stdout] 132 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:146:14
[INFO] [stdout]     |
[INFO] [stdout] 146 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:146:14
[INFO] [stdout]     |
[INFO] [stdout] 146 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:160:14
[INFO] [stdout]     |
[INFO] [stdout] 160 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:160:14
[INFO] [stdout]     |
[INFO] [stdout] 160 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:174:14
[INFO] [stdout]     |
[INFO] [stdout] 174 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:174:14
[INFO] [stdout]     |
[INFO] [stdout] 174 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:188:14
[INFO] [stdout]     |
[INFO] [stdout] 188 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:188:14
[INFO] [stdout]     |
[INFO] [stdout] 188 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:202:14
[INFO] [stdout]     |
[INFO] [stdout] 202 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:202:14
[INFO] [stdout]     |
[INFO] [stdout] 202 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:216:14
[INFO] [stdout]     |
[INFO] [stdout] 216 |     #[derive(ProductOSRelational, Debug, Default, serde::Serialize, serde::Deserialize)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:216:14
[INFO] [stdout]     |
[INFO] [stdout] 216 |     #[derive(ProductOSRelational, Debug, Default, serde::Serialize, serde::Deserialize)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:241:14
[INFO] [stdout]     |
[INFO] [stdout] 241 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:241:14
[INFO] [stdout]     |
[INFO] [stdout] 241 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:255:14
[INFO] [stdout]     |
[INFO] [stdout] 255 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:255:14
[INFO] [stdout]     |
[INFO] [stdout] 255 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:274:14
[INFO] [stdout]     |
[INFO] [stdout] 274 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:274:14
[INFO] [stdout]     |
[INFO] [stdout] 274 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:288:14
[INFO] [stdout]     |
[INFO] [stdout] 288 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:288:14
[INFO] [stdout]     |
[INFO] [stdout] 288 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:303:14
[INFO] [stdout]     |
[INFO] [stdout] 303 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:303:14
[INFO] [stdout]     |
[INFO] [stdout] 303 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:318:14
[INFO] [stdout]     |
[INFO] [stdout] 318 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:318:14
[INFO] [stdout]     |
[INFO] [stdout] 318 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:333:14
[INFO] [stdout]     |
[INFO] [stdout] 333 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:333:14
[INFO] [stdout]     |
[INFO] [stdout] 333 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:348:14
[INFO] [stdout]     |
[INFO] [stdout] 348 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:348:14
[INFO] [stdout]     |
[INFO] [stdout] 348 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:363:14
[INFO] [stdout]     |
[INFO] [stdout] 363 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:363:14
[INFO] [stdout]     |
[INFO] [stdout] 363 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:403:14
[INFO] [stdout]     |
[INFO] [stdout] 403 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:403:14
[INFO] [stdout]     |
[INFO] [stdout] 403 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:410:14
[INFO] [stdout]     |
[INFO] [stdout] 410 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/field_mapping_tests.rs:410:14
[INFO] [stdout]     |
[INFO] [stdout] 410 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] Some errors have detailed explanations: E0432, E0433.
[INFO] [stdout] 
[INFO] [stdout] For more information about an error, try `rustc --explain E0432`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `product-os-store-macros` (test "field_mapping_tests") due to 31 previous errors; 53 warnings emitted
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]    --> tests/derive_macro_tests.rs:396:14
[INFO] [stdout]     |
[INFO] [stdout] 396 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]     |
[INFO] [stdout]     = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout]     = note: this error originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unused imports: `DateTime` and `Utc`
[INFO] [stdout]  --> tests/derive_macro_tests.rs:8:14
[INFO] [stdout]   |
[INFO] [stdout] 8 | use chrono::{DateTime, Utc};
[INFO] [stdout]   |              ^^^^^^^^  ^^^
[INFO] [stdout]   |
[INFO] [stdout]   = note: `#[warn(unused_imports)]` (part of `#[warn(unused)]`) on by default
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]   --> tests/derive_macro_tests.rs:17:14
[INFO] [stdout]    |
[INFO] [stdout] 17 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]   --> tests/derive_macro_tests.rs:17:14
[INFO] [stdout]    |
[INFO] [stdout] 17 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]   --> tests/derive_macro_tests.rs:32:14
[INFO] [stdout]    |
[INFO] [stdout] 32 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]   --> tests/derive_macro_tests.rs:32:14
[INFO] [stdout]    |
[INFO] [stdout] 32 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]   --> tests/derive_macro_tests.rs:48:14
[INFO] [stdout]    |
[INFO] [stdout] 48 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]   --> tests/derive_macro_tests.rs:48:14
[INFO] [stdout]    |
[INFO] [stdout] 48 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]   --> tests/derive_macro_tests.rs:64:14
[INFO] [stdout]    |
[INFO] [stdout] 64 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]   --> tests/derive_macro_tests.rs:64:14
[INFO] [stdout]    |
[INFO] [stdout] 64 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]   --> tests/derive_macro_tests.rs:79:14
[INFO] [stdout]    |
[INFO] [stdout] 79 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]   --> tests/derive_macro_tests.rs:79:14
[INFO] [stdout]    |
[INFO] [stdout] 79 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]   --> tests/derive_macro_tests.rs:94:14
[INFO] [stdout]    |
[INFO] [stdout] 94 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]   --> tests/derive_macro_tests.rs:94:14
[INFO] [stdout]    |
[INFO] [stdout] 94 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]    |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]    = note: expected values for `feature` are: `default`
[INFO] [stdout]    = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]    = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]    = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]    = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:111:14
[INFO] [stdout]     |
[INFO] [stdout] 111 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:111:14
[INFO] [stdout]     |
[INFO] [stdout] 111 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:126:14
[INFO] [stdout]     |
[INFO] [stdout] 126 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:126:14
[INFO] [stdout]     |
[INFO] [stdout] 126 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:141:14
[INFO] [stdout]     |
[INFO] [stdout] 141 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:141:14
[INFO] [stdout]     |
[INFO] [stdout] 141 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:156:14
[INFO] [stdout]     |
[INFO] [stdout] 156 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:156:14
[INFO] [stdout]     |
[INFO] [stdout] 156 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:171:14
[INFO] [stdout]     |
[INFO] [stdout] 171 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:171:14
[INFO] [stdout]     |
[INFO] [stdout] 171 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:186:14
[INFO] [stdout]     |
[INFO] [stdout] 186 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:186:14
[INFO] [stdout]     |
[INFO] [stdout] 186 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:201:14
[INFO] [stdout]     |
[INFO] [stdout] 201 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:201:14
[INFO] [stdout]     |
[INFO] [stdout] 201 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:216:14
[INFO] [stdout]     |
[INFO] [stdout] 216 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:216:14
[INFO] [stdout]     |
[INFO] [stdout] 216 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:231:14
[INFO] [stdout]     |
[INFO] [stdout] 231 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:231:14
[INFO] [stdout]     |
[INFO] [stdout] 231 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:246:14
[INFO] [stdout]     |
[INFO] [stdout] 246 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:246:14
[INFO] [stdout]     |
[INFO] [stdout] 246 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:261:14
[INFO] [stdout]     |
[INFO] [stdout] 261 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:261:14
[INFO] [stdout]     |
[INFO] [stdout] 261 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:276:14
[INFO] [stdout]     |
[INFO] [stdout] 276 |     #[derive(ProductOSRelational, Debug, Default, serde::Serialize, serde::Deserialize)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:276:14
[INFO] [stdout]     |
[INFO] [stdout] 276 |     #[derive(ProductOSRelational, Debug, Default, serde::Serialize, serde::Deserialize)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:302:14
[INFO] [stdout]     |
[INFO] [stdout] 302 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:302:14
[INFO] [stdout]     |
[INFO] [stdout] 302 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:317:14
[INFO] [stdout]     |
[INFO] [stdout] 317 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:317:14
[INFO] [stdout]     |
[INFO] [stdout] 317 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:338:14
[INFO] [stdout]     |
[INFO] [stdout] 338 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:338:14
[INFO] [stdout]     |
[INFO] [stdout] 338 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:353:14
[INFO] [stdout]     |
[INFO] [stdout] 353 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:353:14
[INFO] [stdout]     |
[INFO] [stdout] 353 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `postgres_relational_store`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:396:14
[INFO] [stdout]     |
[INFO] [stdout] 396 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] warning: unexpected `cfg` condition value: `sqlite_relational_store`
[INFO] [stdout]    --> tests/derive_macro_tests.rs:396:14
[INFO] [stdout]     |
[INFO] [stdout] 396 |     #[derive(ProductOSRelational, Debug, Default)]
[INFO] [stdout]     |              ^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]     |
[INFO] [stdout]     = note: expected values for `feature` are: `default`
[INFO] [stdout]     = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate
[INFO] [stdout]     = help: try referring to `ProductOSRelational` crate for guidance on how handle this unexpected cfg
[INFO] [stdout]     = help: the derive macro `ProductOSRelational` may come from an old version of the `product_os_store_macros` crate, try updating your dependency with `cargo update -p product_os_store_macros`
[INFO] [stdout]     = note: see <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]     = note: this warning originates in the derive macro `ProductOSRelational` (in Nightly builds, run with -Z macro-backtrace for more info)
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] error[E0433]: cannot find module or crate `product_os_store` in this scope
[INFO] [stdout]   --> tests/test_helpers.rs:96:8
[INFO] [stdout]    |
[INFO] [stdout] 96 |     T: product_os_store::ProductOSRelationalObject
[INFO] [stdout]    |        ^^^^^^^^^^^^^^^^ use of unresolved module or unlinked crate `product_os_store`
[INFO] [stdout]    |
[INFO] [stdout]    = help: if you wanted to use a crate named `product_os_store`, use `cargo add product_os_store` to add it to your `Cargo.toml`
[INFO] [stdout] 
[INFO] [stdout] 
[INFO] [stdout] Some errors have detailed explanations: E0432, E0433.
[INFO] [stdout] 
[INFO] [stdout] For more information about an error, try `rustc --explain E0432`.
[INFO] [stdout] 
[INFO] [stderr] error: could not compile `product-os-store-macros` (test "derive_macro_tests") due to 34 previous errors; 47 warnings emitted
[INFO] running `Command { std: "docker" "inspect" "f142f03a01b3956b02dfc3ae774bca0f5fc76d195bd705b735af5a33bfe125a7", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "f142f03a01b3956b02dfc3ae774bca0f5fc76d195bd705b735af5a33bfe125a7", kill_on_drop: false }`
[INFO] [stdout] f142f03a01b3956b02dfc3ae774bca0f5fc76d195bd705b735af5a33bfe125a7
