[INFO] fetching crate eio-okta-data 0.2.1... [INFO] testing eio-okta-data-0.2.1 against beta-2025-01-12 for beta-1.85-1 [INFO] extracting crate eio-okta-data 0.2.1 into /workspace/builds/worker-3-tc2/source [INFO] validating manifest of crates.io crate eio-okta-data 0.2.1 on toolchain beta-2025-01-12 [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+beta-2025-01-12" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] started tweaking crates.io crate eio-okta-data 0.2.1 [INFO] removed 0 missing examples [INFO] finished tweaking crates.io crate eio-okta-data 0.2.1 [INFO] tweaked toml for crates.io crate eio-okta-data 0.2.1 written to /workspace/builds/worker-3-tc2/source/Cargo.toml [INFO] crate crates.io crate eio-okta-data 0.2.1 already has a lockfile, it will not be regenerated [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+beta-2025-01-12" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Updating crates.io index [INFO] [stderr] Downloading crates ... [INFO] [stderr] Downloaded struct-patch v0.8.6 [INFO] [stderr] Downloaded remain v0.2.14 [INFO] [stderr] Downloaded validator v0.19.0 [INFO] [stderr] Downloaded struct-patch-derive v0.8.6 [INFO] [stderr] Downloaded validator_derive v0.19.0 [INFO] [stderr] Downloaded comparable_derive v0.5.5 [INFO] [stderr] Downloaded test-strategy v0.4.0 [INFO] [stderr] Downloaded comparable v0.5.5 [INFO] [stderr] Downloaded comparable_helper v0.5.5 [INFO] [stderr] Downloaded email_address v0.2.9 [INFO] [stderr] Downloaded proptest-macro v0.1.0 [INFO] [stderr] Downloaded proptest-derive v0.5.1 [INFO] [stderr] Downloaded mediatype v0.19.18 [INFO] [stderr] Downloaded fake v3.1.0 [INFO] [stderr] Downloaded constcat v0.5.1 [INFO] [stderr] Downloaded dummy v0.9.1 [INFO] [stderr] Downloaded proptest v1.6.0 [INFO] [stderr] Downloaded syn v2.0.95 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:86ea7c7af713d31e8cfdb68a6d0db50b5cf7cbeecde3d112f9f257f747318d36" "/opt/rustwide/cargo-home/bin/cargo" "+beta-2025-01-12" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] [stdout] 6c137f6fee84d77a0b344f17e35974fe414ae95b671c44eb7dee5945dc12e334 [INFO] running `Command { std: "docker" "start" "-a" "6c137f6fee84d77a0b344f17e35974fe414ae95b671c44eb7dee5945dc12e334", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "6c137f6fee84d77a0b344f17e35974fe414ae95b671c44eb7dee5945dc12e334", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "6c137f6fee84d77a0b344f17e35974fe414ae95b671c44eb7dee5945dc12e334", kill_on_drop: false }` [INFO] [stdout] 6c137f6fee84d77a0b344f17e35974fe414ae95b671c44eb7dee5945dc12e334 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "RUSTDOCFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:86ea7c7af713d31e8cfdb68a6d0db50b5cf7cbeecde3d112f9f257f747318d36" "/opt/rustwide/cargo-home/bin/cargo" "+beta-2025-01-12" "build" "--frozen" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 304d0949588d30e2e82eae66b755a5648252076beb7e180aa9bda2e6c503b458 [INFO] running `Command { std: "docker" "start" "-a" "304d0949588d30e2e82eae66b755a5648252076beb7e180aa9bda2e6c503b458", kill_on_drop: false }` [INFO] [stderr] Compiling proc-macro2 v1.0.92 [INFO] [stderr] Compiling unicode-ident v1.0.14 [INFO] [stderr] Compiling serde v1.0.217 [INFO] [stderr] Compiling stable_deref_trait v1.2.0 [INFO] [stderr] Compiling ident_case v1.0.1 [INFO] [stderr] Compiling strsim v0.11.1 [INFO] [stderr] Compiling fnv v1.0.7 [INFO] [stderr] Compiling writeable v0.5.5 [INFO] [stderr] Compiling litemap v0.7.4 [INFO] [stderr] Compiling libc v0.2.169 [INFO] [stderr] Compiling autocfg v1.4.0 [INFO] [stderr] Compiling icu_locid_transform_data v1.5.0 [INFO] [stderr] Compiling byteorder v1.5.0 [INFO] [stderr] Compiling equivalent v1.0.1 [INFO] [stderr] Compiling icu_properties_data v1.5.0 [INFO] [stderr] Compiling hashbrown v0.15.2 [INFO] [stderr] Compiling ryu v1.0.18 [INFO] [stderr] Compiling utf8_iter v1.0.4 [INFO] [stderr] Compiling serde_json v1.0.134 [INFO] [stderr] Compiling utf16_iter v1.0.5 [INFO] [stderr] Compiling memchr v2.7.4 [INFO] [stderr] Compiling itoa v1.0.14 [INFO] [stderr] Compiling syn v1.0.109 [INFO] [stderr] Compiling num-traits v0.2.19 [INFO] [stderr] Compiling icu_normalizer_data v1.5.0 [INFO] [stderr] Compiling unicode-segmentation v1.12.0 [INFO] [stderr] Compiling write16 v1.0.0 [INFO] [stderr] Compiling smallvec v1.13.2 [INFO] [stderr] Compiling anyhow v1.0.95 [INFO] [stderr] Compiling heck v0.5.0 [INFO] [stderr] Compiling quote v1.0.38 [INFO] [stderr] Compiling getrandom v0.2.15 [INFO] [stderr] Compiling indexmap v2.7.0 [INFO] [stderr] Compiling convert_case v0.6.0 [INFO] [stderr] Compiling rustversion v1.0.19 [INFO] [stderr] Compiling regex-syntax v0.8.5 [INFO] [stderr] Compiling syn v2.0.95 [INFO] [stderr] Compiling proc-macro-error-attr2 v2.0.0 [INFO] [stderr] Compiling percent-encoding v2.3.1 [INFO] [stderr] Compiling version_check v0.9.5 [INFO] [stderr] Compiling form_urlencoded v1.2.1 [INFO] [stderr] Compiling schemars v0.8.21 [INFO] [stderr] Compiling serde_yml v0.0.12 [INFO] [stderr] Compiling diff v0.1.13 [INFO] [stderr] Compiling yansi v1.0.1 [INFO] [stderr] Compiling convert_case v0.4.0 [INFO] [stderr] Compiling anstyle v1.0.10 [INFO] [stderr] Compiling once_cell v1.20.2 [INFO] [stderr] Compiling clap_lex v0.7.4 [INFO] [stderr] Compiling pretty_assertions v1.4.1 [INFO] [stderr] Compiling libyml v0.0.5 [INFO] [stderr] Compiling macro_rules_attribute-proc_macro v0.2.0 [INFO] [stderr] Compiling clap_builder v4.5.23 [INFO] [stderr] Compiling dyn-clone v1.0.17 [INFO] [stderr] Compiling lazy_static v1.5.0 [INFO] [stderr] Compiling unarray v0.1.4 [INFO] [stderr] Compiling deunicode v1.6.0 [INFO] [stderr] Compiling bitflags v2.6.0 [INFO] [stderr] Compiling macro_rules_attribute v0.2.0 [INFO] [stderr] Compiling constcat v0.5.1 [INFO] [stderr] Compiling regex-automata v0.4.9 [INFO] [stderr] Compiling comparable_derive v0.5.5 [INFO] [stderr] Compiling comparable_helper v0.5.5 [INFO] [stderr] Compiling regex v1.11.1 [INFO] [stderr] Compiling synstructure v0.13.1 [INFO] [stderr] Compiling darling_core v0.20.10 [INFO] [stderr] Compiling serde_derive_internals v0.29.1 [INFO] [stderr] Compiling proc-macro-error2 v2.0.1 [INFO] [stderr] Compiling serde_derive v1.0.217 [INFO] [stderr] Compiling zerofrom-derive v0.1.5 [INFO] [stderr] Compiling yoke-derive v0.7.5 [INFO] [stderr] Compiling zerovec-derive v0.10.3 [INFO] [stderr] Compiling displaydoc v0.2.5 [INFO] [stderr] Compiling icu_provider_macros v1.5.0 [INFO] [stderr] Compiling zerocopy-derive v0.7.35 [INFO] [stderr] Compiling derive_arbitrary v1.4.1 [INFO] [stderr] Compiling structmeta-derive v0.3.0 [INFO] [stderr] Compiling zerocopy v0.7.35 [INFO] [stderr] Compiling enum-ordinalize-derive v4.3.1 [INFO] [stderr] Compiling proptest-macro v0.1.0 [INFO] [stderr] Compiling zerofrom v0.1.5 [INFO] [stderr] Compiling yoke v0.7.5 [INFO] [stderr] Compiling arbitrary v1.4.1 [INFO] [stderr] Compiling ppv-lite86 v0.2.20 [INFO] [stderr] Compiling zerovec v0.10.4 [INFO] [stderr] Compiling schemars_derive v0.8.21 [INFO] [stderr] Compiling clap_derive v4.5.18 [INFO] [stderr] Compiling darling_macro v0.20.10 [INFO] [stderr] Compiling enum-ordinalize v4.3.0 [INFO] [stderr] Compiling struct-patch-derive v0.8.6 [INFO] [stderr] Compiling structmeta v0.3.0 [INFO] [stderr] Compiling strum_macros v0.26.4 [INFO] [stderr] Compiling tinystr v0.7.6 [INFO] [stderr] Compiling icu_collections v1.5.0 [INFO] [stderr] Compiling icu_locid v1.5.0 [INFO] [stderr] Compiling darling v0.20.10 [INFO] [stderr] Compiling derive_builder_core v0.20.2 [INFO] [stderr] Compiling validator_derive v0.19.0 [INFO] [stderr] Compiling icu_provider v1.5.0 [INFO] [stderr] Compiling dummy v0.9.1 [INFO] [stderr] Compiling icu_locid_transform v1.5.0 [INFO] [stderr] Compiling struct-patch v0.8.6 [INFO] [stderr] Compiling test-strategy v0.4.0 [INFO] [stderr] Compiling derive_builder_macro v0.20.2 [INFO] [stderr] Compiling educe v0.6.0 [INFO] [stderr] Compiling clap v4.5.23 [INFO] [stderr] Compiling proptest-derive v0.5.1 [INFO] [stderr] Compiling icu_properties v1.5.1 [INFO] [stderr] Compiling strum v0.26.3 [INFO] [stderr] Compiling derive_builder v0.20.2 [INFO] [stderr] Compiling remain v0.2.14 [INFO] [stderr] Compiling rand_core v0.6.4 [INFO] [stderr] Compiling chrono v0.4.39 [INFO] [stderr] Compiling email_address v0.2.9 [INFO] [stderr] Compiling mediatype v0.19.18 [INFO] [stderr] Compiling comparable v0.5.5 [INFO] [stderr] Compiling rand_chacha v0.3.1 [INFO] [stderr] Compiling rand_xorshift v0.3.0 [INFO] [stderr] Compiling rand v0.8.5 [INFO] [stderr] Compiling icu_normalizer v1.5.0 [INFO] [stderr] Compiling idna_adapter v1.2.0 [INFO] [stderr] Compiling proptest v1.6.0 [INFO] [stderr] Compiling idna v1.0.3 [INFO] [stderr] Compiling fake v3.1.0 [INFO] [stderr] Compiling url v2.5.4 [INFO] [stderr] Compiling validator v0.19.0 [INFO] [stderr] Compiling eio-okta-data v0.2.1 (/opt/rustwide/workdir) [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/parameters/path_group_id.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs_with_args!)] [INFO] [stdout] | ------------------------------------------ in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [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 derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/parameters/path_user_id.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs_with_args!)] [INFO] [stdout] | ------------------------------------------ in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/parameters/query_after.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs_with_args!)] [INFO] [stdout] | ------------------------------------------ in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/parameters/query_filter.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs_with_args!)] [INFO] [stdout] | ------------------------------------------ in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/parameters/query_limit.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs_with_args!)] [INFO] [stdout] | ------------------------------------------ in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/parameters/query_user_expand.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs_with_args!)] [INFO] [stdout] | ------------------------------------------ in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/authentication_provider.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/group.rs:51:1 [INFO] [stdout] | [INFO] [stdout] 51 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/group.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/group_profile.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/href_hints.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/href_object.rs:3:1 [INFO] [stdout] | [INFO] [stdout] 3 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/links_self.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/password_credential.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/password_credential_hash.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/password_credential_hook.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/recovery_question_credential.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/user.rs:81:1 [INFO] [stdout] | [INFO] [stdout] 81 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/user.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/user_credentials.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/user_profile.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/user_type.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (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 2m 07s [INFO] running `Command { std: "docker" "inspect" "304d0949588d30e2e82eae66b755a5648252076beb7e180aa9bda2e6c503b458", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "304d0949588d30e2e82eae66b755a5648252076beb7e180aa9bda2e6c503b458", kill_on_drop: false }` [INFO] [stdout] 304d0949588d30e2e82eae66b755a5648252076beb7e180aa9bda2e6c503b458 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "RUSTDOCFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:86ea7c7af713d31e8cfdb68a6d0db50b5cf7cbeecde3d112f9f257f747318d36" "/opt/rustwide/cargo-home/bin/cargo" "+beta-2025-01-12" "test" "--frozen" "--no-run" "--message-format=json", kill_on_drop: false }` [INFO] [stdout] 6ddbc90546209d39e03ba21b1d36a5842bbe77680e87da8efbf0a1505cfb3bfa [INFO] running `Command { std: "docker" "start" "-a" "6ddbc90546209d39e03ba21b1d36a5842bbe77680e87da8efbf0a1505cfb3bfa", kill_on_drop: false }` [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/parameters/path_group_id.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs_with_args!)] [INFO] [stdout] | ------------------------------------------ in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [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 derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/parameters/path_user_id.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs_with_args!)] [INFO] [stdout] | ------------------------------------------ in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/parameters/query_after.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs_with_args!)] [INFO] [stdout] | ------------------------------------------ in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/parameters/query_filter.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs_with_args!)] [INFO] [stdout] | ------------------------------------------ in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/parameters/query_limit.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs_with_args!)] [INFO] [stdout] | ------------------------------------------ in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/parameters/query_user_expand.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs_with_args!)] [INFO] [stdout] | ------------------------------------------ in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/authentication_provider.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/group.rs:51:1 [INFO] [stdout] | [INFO] [stdout] 51 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/group.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/group_profile.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/href_hints.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/href_object.rs:3:1 [INFO] [stdout] | [INFO] [stdout] 3 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/links_self.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/password_credential.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/password_credential_hash.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/password_credential_hook.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/recovery_question_credential.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/user.rs:81:1 [INFO] [stdout] | [INFO] [stdout] 81 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/user.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Compiling eio-okta-data v0.2.1 (/opt/rustwide/workdir) [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/user_credentials.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/user_profile.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/user_type.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/parameters/path_group_id.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs_with_args!)] [INFO] [stdout] | ------------------------------------------ in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [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 derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/parameters/path_user_id.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs_with_args!)] [INFO] [stdout] | ------------------------------------------ in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/parameters/query_after.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs_with_args!)] [INFO] [stdout] | ------------------------------------------ in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/parameters/query_filter.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs_with_args!)] [INFO] [stdout] | ------------------------------------------ in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/parameters/query_limit.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs_with_args!)] [INFO] [stdout] | ------------------------------------------ in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/parameters/query_user_expand.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs_with_args!)] [INFO] [stdout] | ------------------------------------------ in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/authentication_provider.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/group.rs:51:1 [INFO] [stdout] | [INFO] [stdout] 51 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/group.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/group_profile.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/href_hints.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/href_object.rs:3:1 [INFO] [stdout] | [INFO] [stdout] 3 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/links_self.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/password_credential.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/password_credential_hash.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/password_credential_hook.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/recovery_question_credential.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/user.rs:81:1 [INFO] [stdout] | [INFO] [stdout] 81 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/user.rs:4:1 [INFO] [stdout] | [INFO] [stdout] 4 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/user_credentials.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/user_profile.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `merge` [INFO] [stdout] --> src/lib.rs:59:47 [INFO] [stdout] | [INFO] [stdout] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stdout] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] ::: src/v2024_07_0/management/components/schemas/user_type.rs:1:1 [INFO] [stdout] | [INFO] [stdout] 1 | #[crate::apply(crate::structs!)] [INFO] [stdout] | -------------------------------- in this procedural macro expansion [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Finished `test` profile [unoptimized + debuginfo] target(s) in 37.19s [INFO] running `Command { std: "docker" "inspect" "6ddbc90546209d39e03ba21b1d36a5842bbe77680e87da8efbf0a1505cfb3bfa", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "6ddbc90546209d39e03ba21b1d36a5842bbe77680e87da8efbf0a1505cfb3bfa", kill_on_drop: false }` [INFO] [stdout] 6ddbc90546209d39e03ba21b1d36a5842bbe77680e87da8efbf0a1505cfb3bfa [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-3-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=warn" "-e" "RUSTDOCFLAGS=--cap-lints=warn" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:86ea7c7af713d31e8cfdb68a6d0db50b5cf7cbeecde3d112f9f257f747318d36" "/opt/rustwide/cargo-home/bin/cargo" "+beta-2025-01-12" "test" "--frozen", kill_on_drop: false }` [INFO] [stdout] 3cd31fc589be44acc299054a54e4cb207610d8f19563151550af63c6168cd3c2 [INFO] running `Command { std: "docker" "start" "-a" "3cd31fc589be44acc299054a54e4cb207610d8f19563151550af63c6168cd3c2", kill_on_drop: false }` [INFO] [stderr] warning: unexpected `cfg` condition value: `merge` [INFO] [stderr] --> src/lib.rs:59:47 [INFO] [stderr] | [INFO] [stderr] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/v2024_07_0/management/components/parameters/path_group_id.rs:1:1 [INFO] [stderr] | [INFO] [stderr] 1 | #[crate::apply(crate::structs_with_args!)] [INFO] [stderr] | ------------------------------------------ in this procedural macro expansion [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stderr] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `merge` [INFO] [stderr] --> src/lib.rs:59:47 [INFO] [stderr] | [INFO] [stderr] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/v2024_07_0/management/components/parameters/path_user_id.rs:1:1 [INFO] [stderr] | [INFO] [stderr] 1 | #[crate::apply(crate::structs_with_args!)] [INFO] [stderr] | ------------------------------------------ in this procedural macro expansion [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `merge` [INFO] [stderr] --> src/lib.rs:59:47 [INFO] [stderr] | [INFO] [stderr] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/v2024_07_0/management/components/parameters/query_after.rs:1:1 [INFO] [stderr] | [INFO] [stderr] 1 | #[crate::apply(crate::structs_with_args!)] [INFO] [stderr] | ------------------------------------------ in this procedural macro expansion [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `merge` [INFO] [stderr] --> src/lib.rs:59:47 [INFO] [stderr] | [INFO] [stderr] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/v2024_07_0/management/components/parameters/query_filter.rs:1:1 [INFO] [stderr] | [INFO] [stderr] 1 | #[crate::apply(crate::structs_with_args!)] [INFO] [stderr] | ------------------------------------------ in this procedural macro expansion [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `merge` [INFO] [stderr] --> src/lib.rs:59:47 [INFO] [stderr] | [INFO] [stderr] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/v2024_07_0/management/components/parameters/query_limit.rs:1:1 [INFO] [stderr] | [INFO] [stderr] 1 | #[crate::apply(crate::structs_with_args!)] [INFO] [stderr] | ------------------------------------------ in this procedural macro expansion [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `merge` [INFO] [stderr] --> src/lib.rs:59:47 [INFO] [stderr] | [INFO] [stderr] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/v2024_07_0/management/components/parameters/query_user_expand.rs:1:1 [INFO] [stderr] | [INFO] [stderr] 1 | #[crate::apply(crate::structs_with_args!)] [INFO] [stderr] | ------------------------------------------ in this procedural macro expansion [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `merge` [INFO] [stderr] --> src/lib.rs:59:47 [INFO] [stderr] | [INFO] [stderr] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/v2024_07_0/management/components/schemas/authentication_provider.rs:1:1 [INFO] [stderr] | [INFO] [stderr] 1 | #[crate::apply(crate::structs!)] [INFO] [stderr] | -------------------------------- in this procedural macro expansion [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `merge` [INFO] [stderr] --> src/lib.rs:59:47 [INFO] [stderr] | [INFO] [stderr] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/v2024_07_0/management/components/schemas/group.rs:51:1 [INFO] [stderr] | [INFO] [stderr] 51 | #[crate::apply(crate::structs!)] [INFO] [stderr] | -------------------------------- in this procedural macro expansion [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `merge` [INFO] [stderr] --> src/lib.rs:59:47 [INFO] [stderr] | [INFO] [stderr] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/v2024_07_0/management/components/schemas/group.rs:4:1 [INFO] [stderr] | [INFO] [stderr] 4 | #[crate::apply(crate::structs!)] [INFO] [stderr] | -------------------------------- in this procedural macro expansion [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `merge` [INFO] [stderr] --> src/lib.rs:59:47 [INFO] [stderr] | [INFO] [stderr] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/v2024_07_0/management/components/schemas/group_profile.rs:1:1 [INFO] [stderr] | [INFO] [stderr] 1 | #[crate::apply(crate::structs!)] [INFO] [stderr] | -------------------------------- in this procedural macro expansion [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `merge` [INFO] [stderr] --> src/lib.rs:59:47 [INFO] [stderr] | [INFO] [stderr] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/v2024_07_0/management/components/schemas/href_hints.rs:1:1 [INFO] [stderr] | [INFO] [stderr] 1 | #[crate::apply(crate::structs!)] [INFO] [stderr] | -------------------------------- in this procedural macro expansion [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `merge` [INFO] [stderr] --> src/lib.rs:59:47 [INFO] [stderr] | [INFO] [stderr] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/v2024_07_0/management/components/schemas/href_object.rs:3:1 [INFO] [stderr] | [INFO] [stderr] 3 | #[crate::apply(crate::structs!)] [INFO] [stderr] | -------------------------------- in this procedural macro expansion [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `merge` [INFO] [stderr] --> src/lib.rs:59:47 [INFO] [stderr] | [INFO] [stderr] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/v2024_07_0/management/components/schemas/links_self.rs:1:1 [INFO] [stderr] | [INFO] [stderr] 1 | #[crate::apply(crate::structs!)] [INFO] [stderr] | -------------------------------- in this procedural macro expansion [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `merge` [INFO] [stderr] --> src/lib.rs:59:47 [INFO] [stderr] | [INFO] [stderr] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/v2024_07_0/management/components/schemas/password_credential.rs:1:1 [INFO] [stderr] | [INFO] [stderr] 1 | #[crate::apply(crate::structs!)] [INFO] [stderr] | -------------------------------- in this procedural macro expansion [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `merge` [INFO] [stderr] --> src/lib.rs:59:47 [INFO] [stderr] | [INFO] [stderr] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/v2024_07_0/management/components/schemas/password_credential_hash.rs:1:1 [INFO] [stderr] | [INFO] [stderr] 1 | #[crate::apply(crate::structs!)] [INFO] [stderr] | -------------------------------- in this procedural macro expansion [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `merge` [INFO] [stderr] --> src/lib.rs:59:47 [INFO] [stderr] | [INFO] [stderr] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/v2024_07_0/management/components/schemas/password_credential_hook.rs:1:1 [INFO] [stderr] | [INFO] [stderr] 1 | #[crate::apply(crate::structs!)] [INFO] [stderr] | -------------------------------- in this procedural macro expansion [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `merge` [INFO] [stderr] --> src/lib.rs:59:47 [INFO] [stderr] | [INFO] [stderr] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/v2024_07_0/management/components/schemas/recovery_question_credential.rs:1:1 [INFO] [stderr] | [INFO] [stderr] 1 | #[crate::apply(crate::structs!)] [INFO] [stderr] | -------------------------------- in this procedural macro expansion [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `merge` [INFO] [stderr] --> src/lib.rs:59:47 [INFO] [stderr] | [INFO] [stderr] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/v2024_07_0/management/components/schemas/user.rs:81:1 [INFO] [stderr] | [INFO] [stderr] 81 | #[crate::apply(crate::structs!)] [INFO] [stderr] | -------------------------------- in this procedural macro expansion [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `merge` [INFO] [stderr] --> src/lib.rs:59:47 [INFO] [stderr] | [INFO] [stderr] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/v2024_07_0/management/components/schemas/user.rs:4:1 [INFO] [stderr] | [INFO] [stderr] 4 | #[crate::apply(crate::structs!)] [INFO] [stderr] | -------------------------------- in this procedural macro expansion [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `merge` [INFO] [stderr] --> src/lib.rs:59:47 [INFO] [stderr] | [INFO] [stderr] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/v2024_07_0/management/components/schemas/user_credentials.rs:1:1 [INFO] [stderr] | [INFO] [stderr] 1 | #[crate::apply(crate::structs!)] [INFO] [stderr] | -------------------------------- in this procedural macro expansion [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `merge` [INFO] [stderr] --> src/lib.rs:59:47 [INFO] [stderr] | [INFO] [stderr] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/v2024_07_0/management/components/schemas/user_profile.rs:1:1 [INFO] [stderr] | [INFO] [stderr] 1 | #[crate::apply(crate::structs!)] [INFO] [stderr] | -------------------------------- in this procedural macro expansion [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: unexpected `cfg` condition value: `merge` [INFO] [stderr] --> src/lib.rs:59:47 [INFO] [stderr] | [INFO] [stderr] 59 | #[cfg_attr(feature = "patch", derive(::struct_patch::Patch))] [INFO] [stderr] | ^^^^^^^^^^^^^^^^^^^^^ [INFO] [stderr] | [INFO] [stderr] ::: src/v2024_07_0/management/components/schemas/user_type.rs:1:1 [INFO] [stderr] | [INFO] [stderr] 1 | #[crate::apply(crate::structs!)] [INFO] [stderr] | -------------------------------- in this procedural macro expansion [INFO] [stderr] | [INFO] [stderr] = note: expected values for `feature` are: `arbitrary`, `builder`, `clap`, `comparable`, `default`, `dummy`, `educe`, `patch`, `proptest`, `schemars`, `serde`, `strum`, and `validate` [INFO] [stderr] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stderr] = help: try referring to `::struct_patch::Patch` crate for guidance on how handle this unexpected cfg [INFO] [stderr] = help: the derive macro `::struct_patch::Patch` may come from an old version of the `struct_patch_derive` crate, try updating your dependency with `cargo update -p struct_patch_derive` [INFO] [stderr] = note: see for more information about checking conditional configuration [INFO] [stderr] = note: this warning originates in the derive macro `::struct_patch::Patch` which comes from the expansion of the attribute macro `crate::apply` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stderr] [INFO] [stderr] warning: `eio-okta-data` (lib) generated 22 warnings [INFO] [stderr] warning: `eio-okta-data` (lib test) generated 22 warnings (22 duplicates) [INFO] [stderr] Finished `test` profile [unoptimized + debuginfo] target(s) in 0.59s [INFO] [stderr] Running unittests src/lib.rs (/opt/rustwide/target/debug/deps/eio_okta_data-40d7b75915ab6a12) [INFO] [stdout] [INFO] [stdout] running 79 tests [INFO] [stdout] test v2024_07_0::management::components::parameters::path_group_id::tests::validate_dummy ... ok [INFO] [stdout] test v2024_07_0::management::components::parameters::query_after::tests::validate_dummy ... ok [INFO] [stdout] test v2024_07_0::management::components::parameters::path_user_id::tests::validate_dummy ... ok [INFO] [stdout] test v2024_07_0::management::components::parameters::query_filter::tests::validate_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::parameters::query_filter::tests::validate_dummy ... ok [INFO] [stdout] test v2024_07_0::management::components::parameters::query_limit::tests::clap_defaults_match ... ok [INFO] [stdout] test v2024_07_0::management::components::parameters::query_filter::tests::roundtrip_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::parameters::query_after::tests::validate_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::parameters::query_limit::tests::validate_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::parameters::query_limit::tests::validate_dummy ... ok [INFO] [stdout] test v2024_07_0::management::components::parameters::query_limit::tests::roundtrip_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::parameters::query_user_expand::tests::validate_dummy ... ok [INFO] [stdout] test v2024_07_0::management::components::parameters::query_user_expand::tests::roundtrip_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::parameters::query_user_expand::tests::validate_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::parameters::query_after::tests::roundtrip_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::authentication_provider::tests::validate_dummy ... ok [INFO] [stdout] test v2024_07_0::management::components::parameters::path_user_id::tests::validate_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::authentication_provider_type::tests::validate_dummy ... ok [INFO] [stdout] test v2024_07_0::management::components::parameters::path_user_id::tests::roundtrip_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::parameters::path_group_id::tests::validate_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::digest_algorithm::tests::validate_dummy ... ok [INFO] [stdout] test v2024_07_0::management::components::parameters::path_group_id::tests::roundtrip_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::digest_algorithm::tests::roundtrip_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::group::tests::validate_dummy ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::digest_algorithm::tests::validate_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::authentication_provider_type::tests::validate_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::group_profile::tests::validate_dummy ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::authentication_provider_type::tests::roundtrip_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::group_type::tests::roundtrip_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::group_type::tests::validate_dummy ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::group_type::tests::validate_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::authentication_provider::tests::validate_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::href_hints::tests::validate_dummy ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::authentication_provider::tests::roundtrip_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::group_profile::tests::roundtrip_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::href_object::tests::validate_dummy ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::http_method::tests::roundtrip_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::http_method::tests::validate_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::http_method::tests::validate_dummy ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::group_profile::tests::validate_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::href_object::tests::validate_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::links_self::tests::validate_dummy ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::href_object::tests::roundtrip_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::href_hints::tests::validate_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::password_credential::tests::validate_dummy ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::password_credential::tests::roundtrip_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::href_hints::tests::roundtrip_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::password_credential_hash::tests::validate_dummy ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::password_credential_hash_algorithm::tests::roundtrip_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::links_self::tests::validate_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::password_credential_hash_algorithm::tests::validate_dummy ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::password_credential_hash_algorithm::tests::validate_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::password_credential_hash::tests::roundtrip_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::password_credential_hook::tests::validate_dummy ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::links_self::tests::roundtrip_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::password_credential::tests::validate_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::recovery_question_credential::tests::validate_dummy ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::password_credential_hash::tests::validate_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::password_credential_hook::tests::roundtrip_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::user::tests::validate_dummy ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::password_credential_hook::tests::validate_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::recovery_question_credential::tests::validate_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::recovery_question_credential::tests::roundtrip_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::user_credentials::tests::validate_dummy ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::user_credentials::tests::validate_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::user_profile::tests::validate_dummy ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::user_status::tests::roundtrip_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::user_status::tests::validate_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::user_status::tests::validate_dummy ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::user_credentials::tests::roundtrip_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::user_type::tests::roundtrip_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::user_type::tests::validate_dummy ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::user_type::tests::validate_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::user_profile::tests::validate_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::user_profile::tests::roundtrip_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::user::tests::roundtrip_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::user::tests::validate_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::group::tests::roundtrip_arbitrary has been running for over 60 seconds [INFO] [stdout] test v2024_07_0::management::components::schemas::group::tests::validate_arbitrary has been running for over 60 seconds [INFO] [stdout] test v2024_07_0::management::components::schemas::group::tests::roundtrip_arbitrary ... ok [INFO] [stdout] test v2024_07_0::management::components::schemas::group::tests::validate_arbitrary ... ok [INFO] [stdout] [INFO] [stdout] test result: ok. 79 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 67.31s [INFO] [stdout] [INFO] [stderr] Doc-tests eio_okta_data [INFO] [stdout] [INFO] [stdout] running 0 tests [INFO] [stdout] [INFO] [stdout] test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s [INFO] [stdout] [INFO] running `Command { std: "docker" "inspect" "3cd31fc589be44acc299054a54e4cb207610d8f19563151550af63c6168cd3c2", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "3cd31fc589be44acc299054a54e4cb207610d8f19563151550af63c6168cd3c2", kill_on_drop: false }` [INFO] [stdout] 3cd31fc589be44acc299054a54e4cb207610d8f19563151550af63c6168cd3c2