[INFO] fetching crate wundergraph 0.1.2... [INFO] testing wundergraph-0.1.2 against master#350d0ef0ec0493e6d21cfb265cb8211a0e74d766 for pr-145330-1 [INFO] extracting crate wundergraph 0.1.2 into /workspace/builds/worker-6-tc1/source [INFO] started tweaking crates.io crate wundergraph 0.1.2 [INFO] removed 0 missing tests [INFO] finished tweaking crates.io crate wundergraph 0.1.2 [INFO] tweaked toml for crates.io crate wundergraph 0.1.2 written to /workspace/builds/worker-6-tc1/source/Cargo.toml [INFO] validating manifest of crates.io crate wundergraph 0.1.2 on toolchain 350d0ef0ec0493e6d21cfb265cb8211a0e74d766 [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+350d0ef0ec0493e6d21cfb265cb8211a0e74d766" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+350d0ef0ec0493e6d21cfb265cb8211a0e74d766" "generate-lockfile" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Updating crates.io index [INFO] [stderr] Locking 157 packages to latest compatible versions [INFO] [stderr] Adding criterion v0.3.6 (available: v0.7.0) [INFO] [stderr] Adding diesel v1.4.8 (available: v2.3.2) [INFO] [stderr] Adding diesel_migrations v1.4.0 (available: v2.3.0) [INFO] [stderr] Adding indexmap v1.9.3 (available: v2.11.4) [INFO] [stderr] Adding insta v0.12.0 (available: v1.43.2) [INFO] [stderr] Adding juniper v0.14.2 (available: v0.17.0) [INFO] [stderr] Adding paste v0.1.18 (available: v1.0.15) [INFO] [stderr] Adding thiserror v1.0.69 (available: v2.0.17) [INFO] [stderr] Adding uuid v0.7.4 (available: v1.18.1) [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+350d0ef0ec0493e6d21cfb265cb8211a0e74d766" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Downloading crates ... [INFO] [stderr] Downloaded wundergraph_derive v0.1.0 [INFO] [stderr] Downloaded insta v0.12.0 [INFO] [stderr] Downloaded pq-sys v0.4.8 [INFO] [stderr] Downloaded juniper_codegen v0.14.2 [INFO] [stderr] Downloaded juniper v0.14.2 [INFO] [stderr] Downloaded libsqlite3-sys v0.22.2 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+350d0ef0ec0493e6d21cfb265cb8211a0e74d766" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 73141d69efecae1a89a9c0d50f4c48f9755ce8cef489be75317ca50c829970e4 [INFO] running `Command { std: "docker" "start" "-a" "73141d69efecae1a89a9c0d50f4c48f9755ce8cef489be75317ca50c829970e4", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "73141d69efecae1a89a9c0d50f4c48f9755ce8cef489be75317ca50c829970e4", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "73141d69efecae1a89a9c0d50f4c48f9755ce8cef489be75317ca50c829970e4", kill_on_drop: false }` [INFO] [stdout] 73141d69efecae1a89a9c0d50f4c48f9755ce8cef489be75317ca50c829970e4 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+350d0ef0ec0493e6d21cfb265cb8211a0e74d766" "build" "--frozen" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 2442e7cbb143fe6c091b5e4e7095876c8639df819b451aea9cfaa207f88cc78f [INFO] running `Command { std: "docker" "start" "-a" "2442e7cbb143fe6c091b5e4e7095876c8639df819b451aea9cfaa207f88cc78f", kill_on_drop: false }` [INFO] [stderr] Compiling indexmap v1.9.3 [INFO] [stderr] Compiling syn v1.0.109 [INFO] [stderr] Compiling uuid v0.7.4 [INFO] [stderr] Compiling paste-impl v0.1.18 [INFO] [stderr] Compiling chrono v0.4.42 [INFO] [stderr] Compiling serde v1.0.228 [INFO] [stderr] Compiling scheduled-thread-pool v0.2.7 [INFO] [stderr] Compiling thiserror v1.0.69 [INFO] [stderr] Compiling zerofrom v0.1.6 [INFO] [stderr] Compiling yoke v0.8.0 [INFO] [stderr] Compiling r2d2 v0.8.10 [INFO] [stderr] Compiling zerovec v0.11.4 [INFO] [stderr] Compiling zerotrie v0.2.2 [INFO] [stderr] Compiling paste v0.1.18 [INFO] [stderr] Compiling tinystr v0.8.1 [INFO] [stderr] Compiling potential_utf v0.1.3 [INFO] [stderr] Compiling icu_collections v2.0.0 [INFO] [stderr] Compiling icu_locale_core v2.0.0 [INFO] [stderr] Compiling icu_provider v2.0.0 [INFO] [stderr] Compiling icu_properties v2.0.1 [INFO] [stderr] Compiling icu_normalizer v2.0.0 [INFO] [stderr] Compiling idna_adapter v1.2.1 [INFO] [stderr] Compiling idna v1.1.0 [INFO] [stderr] Compiling url v2.5.7 [INFO] [stderr] Compiling diesel_derives v1.4.1 [INFO] [stderr] Compiling juniper_codegen v0.14.2 [INFO] [stderr] Compiling wundergraph_derive v0.1.0 [INFO] [stderr] Compiling juniper v0.14.2 [INFO] [stderr] Compiling diesel v1.4.8 [INFO] [stderr] Compiling wundergraph v0.1.2 (/opt/rustwide/workdir) [INFO] [stdout] warning: unexpected `cfg` condition value: `32-column-tables` [INFO] [stdout] --> src/helper/primary_keys.rs:84:1 [INFO] [stdout] | [INFO] [stdout] 84 | __diesel_for_each_tuple!(unref_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `64-column-tables` [INFO] [stdout] --> src/helper/primary_keys.rs:84:1 [INFO] [stdout] | [INFO] [stdout] 84 | __diesel_for_each_tuple!(unref_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `128-column-tables` [INFO] [stdout] --> src/helper/primary_keys.rs:84:1 [INFO] [stdout] | [INFO] [stdout] 84 | __diesel_for_each_tuple!(unref_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `32-column-tables` [INFO] [stdout] --> src/helper/primary_keys.rs:199:1 [INFO] [stdout] | [INFO] [stdout] 199 | __diesel_for_each_tuple!(primary_key_input_object_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `64-column-tables` [INFO] [stdout] --> src/helper/primary_keys.rs:199:1 [INFO] [stdout] | [INFO] [stdout] 199 | __diesel_for_each_tuple!(primary_key_input_object_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `128-column-tables` [INFO] [stdout] --> src/helper/primary_keys.rs:199:1 [INFO] [stdout] | [INFO] [stdout] 199 | __diesel_for_each_tuple!(primary_key_input_object_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `32-column-tables` [INFO] [stdout] --> src/helper/tuple.rs:261:1 [INFO] [stdout] | [INFO] [stdout] 261 | __diesel_for_each_tuple!(impl_tuple_macro_wrapper); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `64-column-tables` [INFO] [stdout] --> src/helper/tuple.rs:261:1 [INFO] [stdout] | [INFO] [stdout] 261 | __diesel_for_each_tuple!(impl_tuple_macro_wrapper); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `128-column-tables` [INFO] [stdout] --> src/helper/tuple.rs:261:1 [INFO] [stdout] | [INFO] [stdout] 261 | __diesel_for_each_tuple!(impl_tuple_macro_wrapper); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `32-column-tables` [INFO] [stdout] --> src/graphql_type.rs:122:1 [INFO] [stdout] | [INFO] [stdout] 122 | __diesel_for_each_tuple!(wundergraph_graphql_helper_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `64-column-tables` [INFO] [stdout] --> src/graphql_type.rs:122:1 [INFO] [stdout] | [INFO] [stdout] 122 | __diesel_for_each_tuple!(wundergraph_graphql_helper_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `128-column-tables` [INFO] [stdout] --> src/graphql_type.rs:122:1 [INFO] [stdout] | [INFO] [stdout] 122 | __diesel_for_each_tuple!(wundergraph_graphql_helper_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `32-column-tables` [INFO] [stdout] --> src/query_builder/selection/fields/associations.rs:410:1 [INFO] [stdout] | [INFO] [stdout] 410 | __diesel_for_each_tuple!(wundergraph_impl_resolve_association); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `64-column-tables` [INFO] [stdout] --> src/query_builder/selection/fields/associations.rs:410:1 [INFO] [stdout] | [INFO] [stdout] 410 | __diesel_for_each_tuple!(wundergraph_impl_resolve_association); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `128-column-tables` [INFO] [stdout] --> src/query_builder/selection/fields/associations.rs:410:1 [INFO] [stdout] | [INFO] [stdout] 410 | __diesel_for_each_tuple!(wundergraph_impl_resolve_association); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `32-column-tables` [INFO] [stdout] --> src/query_builder/selection/fields/field_list.rs:135:1 [INFO] [stdout] | [INFO] [stdout] 135 | __diesel_for_each_tuple!(wundergraph_impl_field_list); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `64-column-tables` [INFO] [stdout] --> src/query_builder/selection/fields/field_list.rs:135:1 [INFO] [stdout] | [INFO] [stdout] 135 | __diesel_for_each_tuple!(wundergraph_impl_field_list); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `128-column-tables` [INFO] [stdout] --> src/query_builder/selection/fields/field_list.rs:135:1 [INFO] [stdout] | [INFO] [stdout] 135 | __diesel_for_each_tuple!(wundergraph_impl_field_list); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `32-column-tables` [INFO] [stdout] --> src/query_builder/selection/fields/helper.rs:274:1 [INFO] [stdout] | [INFO] [stdout] 274 | __diesel_for_each_tuple!(wundergraph_impl_field_extractors); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `64-column-tables` [INFO] [stdout] --> src/query_builder/selection/fields/helper.rs:274:1 [INFO] [stdout] | [INFO] [stdout] 274 | __diesel_for_each_tuple!(wundergraph_impl_field_extractors); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `128-column-tables` [INFO] [stdout] --> src/query_builder/selection/fields/helper.rs:274:1 [INFO] [stdout] | [INFO] [stdout] 274 | __diesel_for_each_tuple!(wundergraph_impl_field_extractors); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `32-column-tables` [INFO] [stdout] --> src/query_builder/selection/filter/filter_helper.rs:574:1 [INFO] [stdout] | [INFO] [stdout] 574 | __diesel_for_each_tuple!(__impl_build_filter_for_tuples); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `64-column-tables` [INFO] [stdout] --> src/query_builder/selection/filter/filter_helper.rs:574:1 [INFO] [stdout] | [INFO] [stdout] 574 | __diesel_for_each_tuple!(__impl_build_filter_for_tuples); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `128-column-tables` [INFO] [stdout] --> src/query_builder/selection/filter/filter_helper.rs:574:1 [INFO] [stdout] | [INFO] [stdout] 574 | __diesel_for_each_tuple!(__impl_build_filter_for_tuples); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `32-column-tables` [INFO] [stdout] --> src/query_builder/selection/order.rs:286:1 [INFO] [stdout] | [INFO] [stdout] 286 | __diesel_for_each_tuple!(impl_order_traits); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `64-column-tables` [INFO] [stdout] --> src/query_builder/selection/order.rs:286:1 [INFO] [stdout] | [INFO] [stdout] 286 | __diesel_for_each_tuple!(impl_order_traits); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `128-column-tables` [INFO] [stdout] --> src/query_builder/selection/order.rs:286:1 [INFO] [stdout] | [INFO] [stdout] 286 | __diesel_for_each_tuple!(impl_order_traits); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `32-column-tables` [INFO] [stdout] --> src/query_builder/selection/query_resolver.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | __diesel_for_each_tuple!(wundergraph_value_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `64-column-tables` [INFO] [stdout] --> src/query_builder/selection/query_resolver.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | __diesel_for_each_tuple!(wundergraph_value_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `128-column-tables` [INFO] [stdout] --> src/query_builder/selection/query_resolver.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | __diesel_for_each_tuple!(wundergraph_value_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `32-column-tables` [INFO] [stdout] --> src/query_builder/selection/select.rs:69:1 [INFO] [stdout] | [INFO] [stdout] 69 | __diesel_for_each_tuple!(impl_select_builder); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `64-column-tables` [INFO] [stdout] --> src/query_builder/selection/select.rs:69:1 [INFO] [stdout] | [INFO] [stdout] 69 | __diesel_for_each_tuple!(impl_select_builder); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `128-column-tables` [INFO] [stdout] --> src/query_builder/selection/select.rs:69:1 [INFO] [stdout] | [INFO] [stdout] 69 | __diesel_for_each_tuple!(impl_select_builder); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `32-column-tables` [INFO] [stdout] --> src/query_builder/types/wundergraph_value.rs:240:1 [INFO] [stdout] | [INFO] [stdout] 240 | __diesel_for_each_tuple!(wundergraph_value_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `64-column-tables` [INFO] [stdout] --> src/query_builder/types/wundergraph_value.rs:240:1 [INFO] [stdout] | [INFO] [stdout] 240 | __diesel_for_each_tuple!(wundergraph_value_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `128-column-tables` [INFO] [stdout] --> src/query_builder/types/wundergraph_value.rs:240:1 [INFO] [stdout] | [INFO] [stdout] 240 | __diesel_for_each_tuple!(wundergraph_value_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item [INFO] [stdout] --> src/query_builder/types/placeholder.rs:13:62 [INFO] [stdout] | [INFO] [stdout] 13 | #[derive(Debug, Clone, Copy, PartialEq, Eq, Ord, PartialOrd, FromSqlRow, Hash)] [INFO] [stdout] | ^--------- [INFO] [stdout] | | [INFO] [stdout] | `FromSqlRow` is not local [INFO] [stdout] | move the `impl` block outside of this function `_impl_from_sql_row_for_placeholder` [INFO] [stdout] 14 | pub struct PlaceHolder(Option); [INFO] [stdout] | ----------- `PlaceHolder` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromSqlRow` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromSqlRow` may come from an old version of the `diesel_derives` crate, try updating your dependency with `cargo update -p diesel_derives` [INFO] [stdout] = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl` [INFO] [stdout] = note: `#[warn(non_local_definitions)]` on by default [INFO] [stdout] = note: this warning originates in the derive macro `FromSqlRow` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item [INFO] [stdout] --> src/query_builder/types/placeholder.rs:13:62 [INFO] [stdout] | [INFO] [stdout] 13 | #[derive(Debug, Clone, Copy, PartialEq, Eq, Ord, PartialOrd, FromSqlRow, Hash)] [INFO] [stdout] | ^--------- [INFO] [stdout] | | [INFO] [stdout] | `Queryable` is not local [INFO] [stdout] | move the `impl` block outside of this function `_impl_from_sql_row_for_placeholder` [INFO] [stdout] 14 | pub struct PlaceHolder(Option); [INFO] [stdout] | ----------- `PlaceHolder` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromSqlRow` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromSqlRow` may come from an old version of the `diesel_derives` crate, try updating your dependency with `cargo update -p diesel_derives` [INFO] [stdout] = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl` [INFO] [stdout] = note: this warning originates in the derive macro `FromSqlRow` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 24.48s [INFO] running `Command { std: "docker" "inspect" "2442e7cbb143fe6c091b5e4e7095876c8639df819b451aea9cfaa207f88cc78f", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "2442e7cbb143fe6c091b5e4e7095876c8639df819b451aea9cfaa207f88cc78f", kill_on_drop: false }` [INFO] [stdout] 2442e7cbb143fe6c091b5e4e7095876c8639df819b451aea9cfaa207f88cc78f [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-6-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:e90291280db7d1fac5b66fc6dad9f9662629e7365a55743daf9bdf73ebc4ea79" "/opt/rustwide/cargo-home/bin/cargo" "+350d0ef0ec0493e6d21cfb265cb8211a0e74d766" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 9d2af3d3cb354f05984745b33163e4fcea279c048147e46466e1fce8751d7614 [INFO] running `Command { std: "docker" "start" "-a" "9d2af3d3cb354f05984745b33163e4fcea279c048147e46466e1fce8751d7614", kill_on_drop: false }` [INFO] [stderr] Compiling clicolors-control v1.0.1 [INFO] [stderr] Compiling migrations_internals v1.4.1 [INFO] [stderr] Compiling termios v0.3.3 [INFO] [stderr] Compiling csv v1.3.1 [INFO] [stderr] Compiling serde_yaml v0.8.26 [INFO] [stderr] Compiling serde_cbor v0.11.2 [INFO] [stderr] Compiling uuid v0.8.2 [INFO] [stderr] Compiling tinytemplate v1.2.1 [INFO] [stdout] warning: unexpected `cfg` condition value: `32-column-tables` [INFO] [stdout] --> src/helper/primary_keys.rs:84:1 [INFO] [stdout] | [INFO] [stdout] 84 | __diesel_for_each_tuple!(unref_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `64-column-tables` [INFO] [stdout] --> src/helper/primary_keys.rs:84:1 [INFO] [stdout] | [INFO] [stdout] 84 | __diesel_for_each_tuple!(unref_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `128-column-tables` [INFO] [stdout] --> src/helper/primary_keys.rs:84:1 [INFO] [stdout] | [INFO] [stdout] 84 | __diesel_for_each_tuple!(unref_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `32-column-tables` [INFO] [stdout] --> src/helper/primary_keys.rs:199:1 [INFO] [stdout] | [INFO] [stdout] 199 | __diesel_for_each_tuple!(primary_key_input_object_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `64-column-tables` [INFO] [stdout] --> src/helper/primary_keys.rs:199:1 [INFO] [stdout] | [INFO] [stdout] 199 | __diesel_for_each_tuple!(primary_key_input_object_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `128-column-tables` [INFO] [stdout] --> src/helper/primary_keys.rs:199:1 [INFO] [stdout] | [INFO] [stdout] 199 | __diesel_for_each_tuple!(primary_key_input_object_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `32-column-tables` [INFO] [stdout] --> src/helper/tuple.rs:261:1 [INFO] [stdout] | [INFO] [stdout] 261 | __diesel_for_each_tuple!(impl_tuple_macro_wrapper); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `64-column-tables` [INFO] [stdout] --> src/helper/tuple.rs:261:1 [INFO] [stdout] | [INFO] [stdout] 261 | __diesel_for_each_tuple!(impl_tuple_macro_wrapper); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `128-column-tables` [INFO] [stdout] --> src/helper/tuple.rs:261:1 [INFO] [stdout] | [INFO] [stdout] 261 | __diesel_for_each_tuple!(impl_tuple_macro_wrapper); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `32-column-tables` [INFO] [stdout] --> src/graphql_type.rs:122:1 [INFO] [stdout] | [INFO] [stdout] 122 | __diesel_for_each_tuple!(wundergraph_graphql_helper_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `64-column-tables` [INFO] [stdout] --> src/graphql_type.rs:122:1 [INFO] [stdout] | [INFO] [stdout] 122 | __diesel_for_each_tuple!(wundergraph_graphql_helper_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `128-column-tables` [INFO] [stdout] --> src/graphql_type.rs:122:1 [INFO] [stdout] | [INFO] [stdout] 122 | __diesel_for_each_tuple!(wundergraph_graphql_helper_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `32-column-tables` [INFO] [stdout] --> src/query_builder/selection/fields/associations.rs:410:1 [INFO] [stdout] | [INFO] [stdout] 410 | __diesel_for_each_tuple!(wundergraph_impl_resolve_association); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `64-column-tables` [INFO] [stdout] --> src/query_builder/selection/fields/associations.rs:410:1 [INFO] [stdout] | [INFO] [stdout] 410 | __diesel_for_each_tuple!(wundergraph_impl_resolve_association); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `128-column-tables` [INFO] [stdout] --> src/query_builder/selection/fields/associations.rs:410:1 [INFO] [stdout] | [INFO] [stdout] 410 | __diesel_for_each_tuple!(wundergraph_impl_resolve_association); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `32-column-tables` [INFO] [stdout] --> src/query_builder/selection/fields/field_list.rs:135:1 [INFO] [stdout] | [INFO] [stdout] 135 | __diesel_for_each_tuple!(wundergraph_impl_field_list); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `64-column-tables` [INFO] [stdout] --> src/query_builder/selection/fields/field_list.rs:135:1 [INFO] [stdout] | [INFO] [stdout] 135 | __diesel_for_each_tuple!(wundergraph_impl_field_list); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `128-column-tables` [INFO] [stdout] --> src/query_builder/selection/fields/field_list.rs:135:1 [INFO] [stdout] | [INFO] [stdout] 135 | __diesel_for_each_tuple!(wundergraph_impl_field_list); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `32-column-tables` [INFO] [stdout] --> src/query_builder/selection/fields/helper.rs:274:1 [INFO] [stdout] | [INFO] [stdout] 274 | __diesel_for_each_tuple!(wundergraph_impl_field_extractors); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `64-column-tables` [INFO] [stdout] --> src/query_builder/selection/fields/helper.rs:274:1 [INFO] [stdout] | [INFO] [stdout] 274 | __diesel_for_each_tuple!(wundergraph_impl_field_extractors); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `128-column-tables` [INFO] [stdout] --> src/query_builder/selection/fields/helper.rs:274:1 [INFO] [stdout] | [INFO] [stdout] 274 | __diesel_for_each_tuple!(wundergraph_impl_field_extractors); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `32-column-tables` [INFO] [stdout] --> src/query_builder/selection/filter/filter_helper.rs:574:1 [INFO] [stdout] | [INFO] [stdout] 574 | __diesel_for_each_tuple!(__impl_build_filter_for_tuples); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `64-column-tables` [INFO] [stdout] --> src/query_builder/selection/filter/filter_helper.rs:574:1 [INFO] [stdout] | [INFO] [stdout] 574 | __diesel_for_each_tuple!(__impl_build_filter_for_tuples); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `128-column-tables` [INFO] [stdout] --> src/query_builder/selection/filter/filter_helper.rs:574:1 [INFO] [stdout] | [INFO] [stdout] 574 | __diesel_for_each_tuple!(__impl_build_filter_for_tuples); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `32-column-tables` [INFO] [stdout] --> src/query_builder/selection/order.rs:286:1 [INFO] [stdout] | [INFO] [stdout] 286 | __diesel_for_each_tuple!(impl_order_traits); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `64-column-tables` [INFO] [stdout] --> src/query_builder/selection/order.rs:286:1 [INFO] [stdout] | [INFO] [stdout] 286 | __diesel_for_each_tuple!(impl_order_traits); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `128-column-tables` [INFO] [stdout] --> src/query_builder/selection/order.rs:286:1 [INFO] [stdout] | [INFO] [stdout] 286 | __diesel_for_each_tuple!(impl_order_traits); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `32-column-tables` [INFO] [stdout] --> src/query_builder/selection/query_resolver.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | __diesel_for_each_tuple!(wundergraph_value_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `64-column-tables` [INFO] [stdout] --> src/query_builder/selection/query_resolver.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | __diesel_for_each_tuple!(wundergraph_value_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `128-column-tables` [INFO] [stdout] --> src/query_builder/selection/query_resolver.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | __diesel_for_each_tuple!(wundergraph_value_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `32-column-tables` [INFO] [stdout] --> src/query_builder/selection/select.rs:69:1 [INFO] [stdout] | [INFO] [stdout] 69 | __diesel_for_each_tuple!(impl_select_builder); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `64-column-tables` [INFO] [stdout] --> src/query_builder/selection/select.rs:69:1 [INFO] [stdout] | [INFO] [stdout] 69 | __diesel_for_each_tuple!(impl_select_builder); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `128-column-tables` [INFO] [stdout] --> src/query_builder/selection/select.rs:69:1 [INFO] [stdout] | [INFO] [stdout] 69 | __diesel_for_each_tuple!(impl_select_builder); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `32-column-tables` [INFO] [stdout] --> src/query_builder/types/wundergraph_value.rs:240:1 [INFO] [stdout] | [INFO] [stdout] 240 | __diesel_for_each_tuple!(wundergraph_value_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `64-column-tables` [INFO] [stdout] --> src/query_builder/types/wundergraph_value.rs:240:1 [INFO] [stdout] | [INFO] [stdout] 240 | __diesel_for_each_tuple!(wundergraph_value_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `128-column-tables` [INFO] [stdout] --> src/query_builder/types/wundergraph_value.rs:240:1 [INFO] [stdout] | [INFO] [stdout] 240 | __diesel_for_each_tuple!(wundergraph_value_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item [INFO] [stdout] --> src/query_builder/types/placeholder.rs:13:62 [INFO] [stdout] | [INFO] [stdout] 13 | #[derive(Debug, Clone, Copy, PartialEq, Eq, Ord, PartialOrd, FromSqlRow, Hash)] [INFO] [stdout] | ^--------- [INFO] [stdout] | | [INFO] [stdout] | `FromSqlRow` is not local [INFO] [stdout] | move the `impl` block outside of this function `_impl_from_sql_row_for_placeholder` [INFO] [stdout] 14 | pub struct PlaceHolder(Option); [INFO] [stdout] | ----------- `PlaceHolder` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromSqlRow` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromSqlRow` may come from an old version of the `diesel_derives` crate, try updating your dependency with `cargo update -p diesel_derives` [INFO] [stdout] = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl` [INFO] [stdout] = note: `#[warn(non_local_definitions)]` on by default [INFO] [stdout] = note: this warning originates in the derive macro `FromSqlRow` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item [INFO] [stdout] --> src/query_builder/types/placeholder.rs:13:62 [INFO] [stdout] | [INFO] [stdout] 13 | #[derive(Debug, Clone, Copy, PartialEq, Eq, Ord, PartialOrd, FromSqlRow, Hash)] [INFO] [stdout] | ^--------- [INFO] [stdout] | | [INFO] [stdout] | `Queryable` is not local [INFO] [stdout] | move the `impl` block outside of this function `_impl_from_sql_row_for_placeholder` [INFO] [stdout] 14 | pub struct PlaceHolder(Option); [INFO] [stdout] | ----------- `PlaceHolder` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromSqlRow` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromSqlRow` may come from an old version of the `diesel_derives` crate, try updating your dependency with `cargo update -p diesel_derives` [INFO] [stdout] = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl` [INFO] [stdout] = note: this warning originates in the derive macro `FromSqlRow` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Compiling console v0.9.2 [INFO] [stderr] Compiling migrations_macros v1.4.2 [INFO] [stderr] Compiling criterion v0.3.6 [INFO] [stderr] Compiling insta v0.12.0 [INFO] [stderr] Compiling diesel_migrations v1.4.0 [INFO] [stderr] Compiling wundergraph v0.1.2 (/opt/rustwide/workdir) [INFO] [stdout] error[E0463]: can't find crate for `wundergraph_bench` [INFO] [stdout] --> tests/lib.rs:6:1 [INFO] [stdout] | [INFO] [stdout] 6 | extern crate wundergraph_bench; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ can't find crate [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0463]: can't find crate for `wundergraph_example` [INFO] [stdout] --> tests/lib.rs:7:1 [INFO] [stdout] | [INFO] [stdout] 7 | extern crate wundergraph_example; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ can't find crate [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error: At least one feature of "sqlite" or "postgres" needs to be enabled [INFO] [stdout] --> tests/lib.rs:31:1 [INFO] [stdout] | [INFO] [stdout] 31 | compile_error!("At least one feature of \"sqlite\" or \"postgres\" needs to be enabled"); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] error[E0432]: unresolved import `crate::DbConnection` [INFO] [stdout] --> tests/helper.rs:2:5 [INFO] [stdout] | [INFO] [stdout] 2 | use crate::DbConnection; [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^ no `DbConnection` in the root [INFO] [stdout] | [INFO] [stdout] note: found an item that was configured out [INFO] [stdout] --> tests/lib.rs:25:6 [INFO] [stdout] | [INFO] [stdout] 24 | #[cfg(feature = "postgres")] [INFO] [stdout] | -------------------- the item is gated behind the `postgres` feature [INFO] [stdout] 25 | type DbConnection = diesel::pg::PgConnection; [INFO] [stdout] | ^^^^^^^^^^^^ [INFO] [stdout] note: found an item that was configured out [INFO] [stdout] --> tests/lib.rs:28:6 [INFO] [stdout] | [INFO] [stdout] 27 | #[cfg(feature = "sqlite")] [INFO] [stdout] | ------------------ the item is gated behind the `sqlite` feature [INFO] [stdout] 28 | type DbConnection = diesel::sqlite::SqliteConnection; [INFO] [stdout] | ^^^^^^^^^^^^ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] Some errors have detailed explanations: E0432, E0463. [INFO] [stdout] [INFO] [stdout] For more information about an error, try `rustc --explain E0432`. [INFO] [stdout] [INFO] [stderr] error: could not compile `wundergraph` (test "integration_tests") due to 4 previous errors [INFO] [stderr] warning: build failed, waiting for other jobs to finish... [INFO] [stdout] warning: unexpected `cfg` condition value: `32-column-tables` [INFO] [stdout] --> src/helper/primary_keys.rs:84:1 [INFO] [stdout] | [INFO] [stdout] 84 | __diesel_for_each_tuple!(unref_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `64-column-tables` [INFO] [stdout] --> src/helper/primary_keys.rs:84:1 [INFO] [stdout] | [INFO] [stdout] 84 | __diesel_for_each_tuple!(unref_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `128-column-tables` [INFO] [stdout] --> src/helper/primary_keys.rs:84:1 [INFO] [stdout] | [INFO] [stdout] 84 | __diesel_for_each_tuple!(unref_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `32-column-tables` [INFO] [stdout] --> src/helper/primary_keys.rs:199:1 [INFO] [stdout] | [INFO] [stdout] 199 | __diesel_for_each_tuple!(primary_key_input_object_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `64-column-tables` [INFO] [stdout] --> src/helper/primary_keys.rs:199:1 [INFO] [stdout] | [INFO] [stdout] 199 | __diesel_for_each_tuple!(primary_key_input_object_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `128-column-tables` [INFO] [stdout] --> src/helper/primary_keys.rs:199:1 [INFO] [stdout] | [INFO] [stdout] 199 | __diesel_for_each_tuple!(primary_key_input_object_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `32-column-tables` [INFO] [stdout] --> src/helper/tuple.rs:261:1 [INFO] [stdout] | [INFO] [stdout] 261 | __diesel_for_each_tuple!(impl_tuple_macro_wrapper); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `64-column-tables` [INFO] [stdout] --> src/helper/tuple.rs:261:1 [INFO] [stdout] | [INFO] [stdout] 261 | __diesel_for_each_tuple!(impl_tuple_macro_wrapper); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `128-column-tables` [INFO] [stdout] --> src/helper/tuple.rs:261:1 [INFO] [stdout] | [INFO] [stdout] 261 | __diesel_for_each_tuple!(impl_tuple_macro_wrapper); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `32-column-tables` [INFO] [stdout] --> src/graphql_type.rs:122:1 [INFO] [stdout] | [INFO] [stdout] 122 | __diesel_for_each_tuple!(wundergraph_graphql_helper_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `64-column-tables` [INFO] [stdout] --> src/graphql_type.rs:122:1 [INFO] [stdout] | [INFO] [stdout] 122 | __diesel_for_each_tuple!(wundergraph_graphql_helper_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `128-column-tables` [INFO] [stdout] --> src/graphql_type.rs:122:1 [INFO] [stdout] | [INFO] [stdout] 122 | __diesel_for_each_tuple!(wundergraph_graphql_helper_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `32-column-tables` [INFO] [stdout] --> src/query_builder/selection/fields/associations.rs:410:1 [INFO] [stdout] | [INFO] [stdout] 410 | __diesel_for_each_tuple!(wundergraph_impl_resolve_association); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `64-column-tables` [INFO] [stdout] --> src/query_builder/selection/fields/associations.rs:410:1 [INFO] [stdout] | [INFO] [stdout] 410 | __diesel_for_each_tuple!(wundergraph_impl_resolve_association); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `128-column-tables` [INFO] [stdout] --> src/query_builder/selection/fields/associations.rs:410:1 [INFO] [stdout] | [INFO] [stdout] 410 | __diesel_for_each_tuple!(wundergraph_impl_resolve_association); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `32-column-tables` [INFO] [stdout] --> src/query_builder/selection/fields/field_list.rs:135:1 [INFO] [stdout] | [INFO] [stdout] 135 | __diesel_for_each_tuple!(wundergraph_impl_field_list); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `64-column-tables` [INFO] [stdout] --> src/query_builder/selection/fields/field_list.rs:135:1 [INFO] [stdout] | [INFO] [stdout] 135 | __diesel_for_each_tuple!(wundergraph_impl_field_list); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `128-column-tables` [INFO] [stdout] --> src/query_builder/selection/fields/field_list.rs:135:1 [INFO] [stdout] | [INFO] [stdout] 135 | __diesel_for_each_tuple!(wundergraph_impl_field_list); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `32-column-tables` [INFO] [stdout] --> src/query_builder/selection/fields/helper.rs:274:1 [INFO] [stdout] | [INFO] [stdout] 274 | __diesel_for_each_tuple!(wundergraph_impl_field_extractors); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `64-column-tables` [INFO] [stdout] --> src/query_builder/selection/fields/helper.rs:274:1 [INFO] [stdout] | [INFO] [stdout] 274 | __diesel_for_each_tuple!(wundergraph_impl_field_extractors); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `128-column-tables` [INFO] [stdout] --> src/query_builder/selection/fields/helper.rs:274:1 [INFO] [stdout] | [INFO] [stdout] 274 | __diesel_for_each_tuple!(wundergraph_impl_field_extractors); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `32-column-tables` [INFO] [stdout] --> src/query_builder/selection/filter/filter_helper.rs:574:1 [INFO] [stdout] | [INFO] [stdout] 574 | __diesel_for_each_tuple!(__impl_build_filter_for_tuples); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `64-column-tables` [INFO] [stdout] --> src/query_builder/selection/filter/filter_helper.rs:574:1 [INFO] [stdout] | [INFO] [stdout] 574 | __diesel_for_each_tuple!(__impl_build_filter_for_tuples); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `128-column-tables` [INFO] [stdout] --> src/query_builder/selection/filter/filter_helper.rs:574:1 [INFO] [stdout] | [INFO] [stdout] 574 | __diesel_for_each_tuple!(__impl_build_filter_for_tuples); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `32-column-tables` [INFO] [stdout] --> src/query_builder/selection/order.rs:286:1 [INFO] [stdout] | [INFO] [stdout] 286 | __diesel_for_each_tuple!(impl_order_traits); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `64-column-tables` [INFO] [stdout] --> src/query_builder/selection/order.rs:286:1 [INFO] [stdout] | [INFO] [stdout] 286 | __diesel_for_each_tuple!(impl_order_traits); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `128-column-tables` [INFO] [stdout] --> src/query_builder/selection/order.rs:286:1 [INFO] [stdout] | [INFO] [stdout] 286 | __diesel_for_each_tuple!(impl_order_traits); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `32-column-tables` [INFO] [stdout] --> src/query_builder/selection/query_resolver.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | __diesel_for_each_tuple!(wundergraph_value_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `64-column-tables` [INFO] [stdout] --> src/query_builder/selection/query_resolver.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | __diesel_for_each_tuple!(wundergraph_value_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `128-column-tables` [INFO] [stdout] --> src/query_builder/selection/query_resolver.rs:129:1 [INFO] [stdout] | [INFO] [stdout] 129 | __diesel_for_each_tuple!(wundergraph_value_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `32-column-tables` [INFO] [stdout] --> src/query_builder/selection/select.rs:69:1 [INFO] [stdout] | [INFO] [stdout] 69 | __diesel_for_each_tuple!(impl_select_builder); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `64-column-tables` [INFO] [stdout] --> src/query_builder/selection/select.rs:69:1 [INFO] [stdout] | [INFO] [stdout] 69 | __diesel_for_each_tuple!(impl_select_builder); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `128-column-tables` [INFO] [stdout] --> src/query_builder/selection/select.rs:69:1 [INFO] [stdout] | [INFO] [stdout] 69 | __diesel_for_each_tuple!(impl_select_builder); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `32-column-tables` [INFO] [stdout] --> src/query_builder/types/wundergraph_value.rs:240:1 [INFO] [stdout] | [INFO] [stdout] 240 | __diesel_for_each_tuple!(wundergraph_value_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `64-column-tables` [INFO] [stdout] --> src/query_builder/types/wundergraph_value.rs:240:1 [INFO] [stdout] | [INFO] [stdout] 240 | __diesel_for_each_tuple!(wundergraph_value_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `128-column-tables` [INFO] [stdout] --> src/query_builder/types/wundergraph_value.rs:240:1 [INFO] [stdout] | [INFO] [stdout] 240 | __diesel_for_each_tuple!(wundergraph_value_impl); [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `chrono`, `chrono_internal`, `debug`, `default`, `extras`, `log`, `postgres`, `sqlite`, `uuid`, and `uuid_internal` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `__diesel_for_each_tuple` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the macro `__diesel_for_each_tuple` may come from an old version of the `diesel` crate, try updating your dependency with `cargo update -p diesel` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `__diesel_for_each_tuple` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item [INFO] [stdout] --> src/query_builder/types/placeholder.rs:13:62 [INFO] [stdout] | [INFO] [stdout] 13 | #[derive(Debug, Clone, Copy, PartialEq, Eq, Ord, PartialOrd, FromSqlRow, Hash)] [INFO] [stdout] | ^--------- [INFO] [stdout] | | [INFO] [stdout] | `FromSqlRow` is not local [INFO] [stdout] | move the `impl` block outside of this function `_impl_from_sql_row_for_placeholder` [INFO] [stdout] 14 | pub struct PlaceHolder(Option); [INFO] [stdout] | ----------- `PlaceHolder` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromSqlRow` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromSqlRow` may come from an old version of the `diesel_derives` crate, try updating your dependency with `cargo update -p diesel_derives` [INFO] [stdout] = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl` [INFO] [stdout] = note: `#[warn(non_local_definitions)]` on by default [INFO] [stdout] = note: this warning originates in the derive macro `FromSqlRow` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: non-local `impl` definition, `impl` blocks should be written at the same level as their item [INFO] [stdout] --> src/query_builder/types/placeholder.rs:13:62 [INFO] [stdout] | [INFO] [stdout] 13 | #[derive(Debug, Clone, Copy, PartialEq, Eq, Ord, PartialOrd, FromSqlRow, Hash)] [INFO] [stdout] | ^--------- [INFO] [stdout] | | [INFO] [stdout] | `Queryable` is not local [INFO] [stdout] | move the `impl` block outside of this function `_impl_from_sql_row_for_placeholder` [INFO] [stdout] 14 | pub struct PlaceHolder(Option); [INFO] [stdout] | ----------- `PlaceHolder` is not local [INFO] [stdout] | [INFO] [stdout] = note: the derive macro `FromSqlRow` defines the non-local `impl`, and may need to be changed [INFO] [stdout] = note: the derive macro `FromSqlRow` may come from an old version of the `diesel_derives` crate, try updating your dependency with `cargo update -p diesel_derives` [INFO] [stdout] = note: an `impl` is never scoped, even when it is nested inside an item, as it may impact type checking outside of that item, which can be the case if neither the trait or the self type are at the same nesting level as the `impl` [INFO] [stdout] = note: this warning originates in the derive macro `FromSqlRow` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] running `Command { std: "docker" "inspect" "9d2af3d3cb354f05984745b33163e4fcea279c048147e46466e1fce8751d7614", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "9d2af3d3cb354f05984745b33163e4fcea279c048147e46466e1fce8751d7614", kill_on_drop: false }` [INFO] [stdout] 9d2af3d3cb354f05984745b33163e4fcea279c048147e46466e1fce8751d7614