[INFO] cloning repository https://github.com/rancher-eio/okta-sync
[INFO] running `Command { std: "git" "-c" "credential.helper=" "-c" "credential.helper=/workspace/cargo-home/bin/git-credential-null" "clone" "--bare" "https://github.com/rancher-eio/okta-sync" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Francher-eio%2Fokta-sync", kill_on_drop: false }`
[INFO] [stderr] Cloning into bare repository '/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Francher-eio%2Fokta-sync'...
[INFO] running `Command { std: "git" "rev-parse" "HEAD", kill_on_drop: false }`
[INFO] [stdout] f804cb44bdb60cf2ae2f47c69d42f6d5e5438e6d
[INFO] checking rancher-eio/okta-sync against try#334963c956d25708feab489a3816ae63f639355d for pr-135216-1
[INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Francher-eio%2Fokta-sync" "/workspace/builds/worker-7-tc2/source", kill_on_drop: false }`
[INFO] [stderr] Cloning into '/workspace/builds/worker-7-tc2/source'...
[INFO] [stderr] done.
[INFO] validating manifest of git repo https://github.com/rancher-eio/okta-sync on toolchain 334963c956d25708feab489a3816ae63f639355d
[INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+334963c956d25708feab489a3816ae63f639355d" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }`
[INFO] started tweaking git repo https://github.com/rancher-eio/okta-sync
[INFO] finished tweaking git repo https://github.com/rancher-eio/okta-sync
[INFO] tweaked toml for git repo https://github.com/rancher-eio/okta-sync written to /workspace/builds/worker-7-tc2/source/Cargo.toml
[INFO] crate git repo https://github.com/rancher-eio/okta-sync 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" "+334963c956d25708feab489a3816ae63f639355d" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-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:f3a9d4ad9d972b27faf3965f35b62e55ba32bbce8f20bc8fe909558a86702fde" "/opt/rustwide/cargo-home/bin/cargo" "+334963c956d25708feab489a3816ae63f639355d" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }`
[INFO] [stdout] 02ccbe2228d9588767f9cd800c9dcb5a23f1a56c4e7d52128513f93346d5457b
[INFO] running `Command { std: "docker" "start" "-a" "02ccbe2228d9588767f9cd800c9dcb5a23f1a56c4e7d52128513f93346d5457b", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "inspect" "02ccbe2228d9588767f9cd800c9dcb5a23f1a56c4e7d52128513f93346d5457b", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "02ccbe2228d9588767f9cd800c9dcb5a23f1a56c4e7d52128513f93346d5457b", kill_on_drop: false }`
[INFO] [stdout] 02ccbe2228d9588767f9cd800c9dcb5a23f1a56c4e7d52128513f93346d5457b
[INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc2/target:/opt/rustwide/target:rw,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-7-tc2/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/cargo-home:/opt/rustwide/cargo-home:ro,Z" "-v" "/var/lib/crater-agent-workspace/rustup-home:/opt/rustwide/rustup-home:ro,Z" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-e" "CARGO_INCREMENTAL=0" "-e" "RUST_BACKTRACE=full" "-e" "RUSTFLAGS=--cap-lints=forbid" "-e" "RUSTDOCFLAGS=--cap-lints=forbid" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-w" "/opt/rustwide/workdir" "-m" "1610612736" "--user" "0:0" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:f3a9d4ad9d972b27faf3965f35b62e55ba32bbce8f20bc8fe909558a86702fde" "/opt/rustwide/cargo-home/bin/cargo" "+334963c956d25708feab489a3816ae63f639355d" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }`
[INFO] [stdout] fb53d88d73c461d5aabf52c52f6e6ab7c23022d6fdca4b4c61085605ada9bd95
[INFO] running `Command { std: "docker" "start" "-a" "fb53d88d73c461d5aabf52c52f6e6ab7c23022d6fdca4b4c61085605ada9bd95", kill_on_drop: false }`
[INFO] [stderr]    Compiling proc-macro2 v1.0.92
[INFO] [stderr]    Compiling unicode-ident v1.0.14
[INFO] [stderr]    Compiling libc v0.2.169
[INFO] [stderr]     Checking cfg-if v1.0.0
[INFO] [stderr]    Compiling serde v1.0.217
[INFO] [stderr]    Compiling autocfg v1.4.0
[INFO] [stderr]     Checking memchr v2.7.4
[INFO] [stderr]     Checking itoa v1.0.14
[INFO] [stderr]     Checking smallvec v1.13.2
[INFO] [stderr]    Compiling version_check v0.9.5
[INFO] [stderr]     Checking once_cell v1.20.2
[INFO] [stderr]     Checking stable_deref_trait v1.2.0
[INFO] [stderr]    Compiling strsim v0.11.1
[INFO] [stderr]     Checking litemap v0.7.4
[INFO] [stderr]     Checking writeable v0.5.5
[INFO] [stderr]    Compiling ident_case v1.0.1
[INFO] [stderr]    Compiling fnv v1.0.7
[INFO] [stderr]     Checking equivalent v1.0.1
[INFO] [stderr]     Checking hashbrown v0.15.2
[INFO] [stderr]     Checking ryu v1.0.18
[INFO] [stderr]    Compiling serde_json v1.0.134
[INFO] [stderr]     Checking icu_locid_transform_data v1.5.0
[INFO] [stderr]     Checking bytes v1.9.0
[INFO] [stderr]     Checking icu_properties_data v1.5.0
[INFO] [stderr]     Checking bitflags v2.6.0
[INFO] [stderr]     Checking utf16_iter v1.0.5
[INFO] [stderr]     Checking write16 v1.0.0
[INFO] [stderr]     Checking utf8_iter v1.0.4
[INFO] [stderr]     Checking icu_normalizer_data v1.5.0
[INFO] [stderr]    Compiling syn v1.0.109
[INFO] [stderr]     Checking percent-encoding v2.3.1
[INFO] [stderr]     Checking byteorder v1.5.0
[INFO] [stderr]    Compiling heck v0.5.0
[INFO] [stderr]    Compiling rustix v0.38.42
[INFO] [stderr]    Compiling unicode-segmentation v1.12.0
[INFO] [stderr]     Checking log v0.4.22
[INFO] [stderr]     Checking linux-raw-sys v0.4.14
[INFO] [stderr]     Checking form_urlencoded v1.2.1
[INFO] [stderr]     Checking utf8parse v0.2.2
[INFO] [stderr]     Checking regex-syntax v0.8.5
[INFO] [stderr]    Compiling paste v1.0.15
[INFO] [stderr]    Compiling num-traits v0.2.19
[INFO] [stderr]     Checking anstyle-parse v0.2.6
[INFO] [stderr]    Compiling shlex v1.3.0
[INFO] [stderr]    Compiling anyhow v1.0.95
[INFO] [stderr]     Checking anstyle v1.0.10
[INFO] [stderr]    Compiling rustversion v1.0.19
[INFO] [stderr]     Checking is_terminal_polyfill v1.70.1
[INFO] [stderr]     Checking iana-time-zone v0.1.61
[INFO] [stderr]     Checking colorchoice v1.0.3
[INFO] [stderr]     Checking unicode-width v0.2.0
[INFO] [stderr]     Checking anstyle-query v1.1.2
[INFO] [stderr]    Compiling cc v1.2.7
[INFO] [stderr]     Checking http v1.2.0
[INFO] [stderr]     Checking anstream v0.6.18
[INFO] [stderr]     Checking clap_lex v0.7.4
[INFO] [stderr]     Checking unicase v2.8.1
[INFO] [stderr]     Checking aho-corasick v1.1.3
[INFO] [stderr]    Compiling convert_case v0.6.0
[INFO] [stderr]    Compiling serde_yml v0.0.12
[INFO] [stderr]     Checking dyn-clone v1.0.17
[INFO] [stderr]    Compiling quote v1.0.38
[INFO] [stderr]     Checking lazy_static v1.5.0
[INFO] [stderr]    Compiling schemars v0.8.21
[INFO] [stderr]     Checking yansi v1.0.1
[INFO] [stderr]     Checking diff v0.1.13
[INFO] [stderr]    Compiling lock_api v0.4.12
[INFO] [stderr]     Checking libyml v0.0.5
[INFO] [stderr]    Compiling typenum v1.17.0
[INFO] [stderr]    Compiling syn v2.0.95
[INFO] [stderr]     Checking deunicode v1.6.0
[INFO] [stderr]    Compiling parking_lot_core v0.9.10
[INFO] [stderr]    Compiling macro_rules_attribute-proc_macro v0.2.0
[INFO] [stderr]     Checking pretty_assertions v1.4.1
[INFO] [stderr]    Compiling proc-macro-error-attr2 v2.0.0
[INFO] [stderr]     Checking unarray v0.1.4
[INFO] [stderr]     Checking pin-project-lite v0.2.16
[INFO] [stderr]    Compiling generic-array v0.14.7
[INFO] [stderr]     Checking getrandom v0.2.15
[INFO] [stderr]     Checking terminal_size v0.4.1
[INFO] [stderr]     Checking macro_rules_attribute v0.2.0
[INFO] [stderr]     Checking signal-hook-registry v1.4.2
[INFO] [stderr]     Checking scopeguard v1.2.0
[INFO] [stderr]     Checking untrusted v0.9.0
[INFO] [stderr]     Checking clap_builder v4.5.23
[INFO] [stderr]     Checking rustls-pki-types v1.10.1
[INFO] [stderr]     Checking constcat v0.5.1
[INFO] [stderr]    Compiling thiserror v1.0.69
[INFO] [stderr]     Checking spin v0.9.8
[INFO] [stderr]    Compiling proc-macro-error-attr v1.0.4
[INFO] [stderr]    Compiling slab v0.4.9
[INFO] [stderr]     Checking futures-sink v0.3.31
[INFO] [stderr]    Compiling num-conv v0.1.0
[INFO] [stderr]     Checking powerfmt v0.2.0
[INFO] [stderr]    Compiling time-core v0.1.2
[INFO] [stderr]     Checking futures-core v0.3.31
[INFO] [stderr]    Compiling proc-macro-error v1.0.4
[INFO] [stderr]     Checking parking_lot v0.12.3
[INFO] [stderr]     Checking zeroize v1.8.1
[INFO] [stderr]    Compiling time-macros v0.2.18
[INFO] [stderr]     Checking num_threads v0.1.7
[INFO] [stderr]     Checking base64 v0.21.7
[INFO] [stderr]    Compiling rustls v0.23.20
[INFO] [stderr]     Checking adler2 v2.0.0
[INFO] [stderr]     Checking miniz_oxide v0.8.2
[INFO] [stderr]     Checking futures-channel v0.3.31
[INFO] [stderr]     Checking subtle v2.6.1
[INFO] [stderr]     Checking pin-utils v0.1.0
[INFO] [stderr]     Checking futures-io v0.3.31
[INFO] [stderr]     Checking futures-task v0.3.31
[INFO] [stderr]     Checking mio v1.0.3
[INFO] [stderr]     Checking socket2 v0.5.8
[INFO] [stderr]    Compiling peg-runtime v0.8.3
[INFO] [stderr]     Checking regex-automata v0.4.9
[INFO] [stderr]     Checking base64 v0.22.1
[INFO] [stderr]    Compiling object v0.36.7
[INFO] [stderr]     Checking gimli v0.31.1
[INFO] [stderr]    Compiling ring v0.17.8
[INFO] [stderr]    Compiling peg-macros v0.8.4
[INFO] [stderr]     Checking cpufeatures v0.2.16
[INFO] [stderr]     Checking headers-core v0.3.0
[INFO] [stderr]     Checking crc32fast v1.4.2
[INFO] [stderr]     Checking rustc-demangle v0.1.24
[INFO] [stderr]    Compiling owo-colors v4.1.0
[INFO] [stderr]     Checking httpdate v1.0.3
[INFO] [stderr]     Checking mime v0.3.17
[INFO] [stderr]     Checking unicode-width v0.1.14
[INFO] [stderr]     Checking flate2 v1.0.35
[INFO] [stderr]     Checking webpki-roots v0.26.7
[INFO] [stderr]     Checking http-body v1.0.1
[INFO] [stderr]     Checking tracing-core v0.1.33
[INFO] [stderr]    Compiling httparse v1.9.5
[INFO] [stderr]     Checking unicode-linebreak v0.1.5
[INFO] [stderr]     Checking is_ci v1.2.0
[INFO] [stderr]     Checking supports-color v3.0.2
[INFO] [stderr]     Checking textwrap v0.16.1
[INFO] [stderr]     Checking supports-hyperlinks v3.1.0
[INFO] [stderr]     Checking humantime v2.1.0
[INFO] [stderr]     Checking try-lock v0.2.5
[INFO] [stderr]     Checking tower-service v0.3.3
[INFO] [stderr]     Checking supports-unicode v3.0.0
[INFO] [stderr]     Checking want v0.3.1
[INFO] [stderr]     Checking crypto-common v0.1.6
[INFO] [stderr]     Checking block-buffer v0.10.4
[INFO] [stderr]    Compiling signal-hook v0.3.17
[INFO] [stderr]     Checking num-integer v0.1.46
[INFO] [stderr]     Checking digest v0.10.7
[INFO] [stderr]     Checking mio v0.8.11
[INFO] [stderr]    Compiling semver v1.0.24
[INFO] [stderr]     Checking tower-layer v0.3.3
[INFO] [stderr]     Checking sync_wrapper v1.0.2
[INFO] [stderr]     Checking openssl-probe v0.1.5
[INFO] [stderr]     Checking sha1 v0.10.6
[INFO] [stderr]     Checking num-bigint v0.4.6
[INFO] [stderr]     Checking signal-hook-mio v0.2.4
[INFO] [stderr]     Checking rustls-native-certs v0.8.1
[INFO] [stderr]     Checking pem v3.0.4
[INFO] [stderr]    Compiling fs-err v3.0.0
[INFO] [stderr]     Checking headers v0.4.0
[INFO] [stderr]     Checking thread_local v1.1.8
[INFO] [stderr]    Compiling camino v1.1.9
[INFO] [stderr]     Checking home v0.5.11
[INFO] [stderr]     Checking either v1.13.0
[INFO] [stderr]     Checking bitflags v1.3.2
[INFO] [stderr]     Checking fuzzy-matcher v0.3.7
[INFO] [stderr]     Checking crossterm v0.25.0
[INFO] [stderr]     Checking etcetera v0.8.0
[INFO] [stderr]     Checking peg v0.8.4
[INFO] [stderr]     Checking secrecy v0.10.3
[INFO] [stderr]     Checking filetime v0.2.25
[INFO] [stderr]     Checking fxhash v0.2.1
[INFO] [stderr]     Checking arc-swap v1.7.1
[INFO] [stderr]     Checking addr2line v0.24.2
[INFO] [stderr]     Checking web-time v1.1.0
[INFO] [stderr]     Checking itertools v0.13.0
[INFO] [stderr]     Checking newline-converter v0.3.0
[INFO] [stderr]     Checking tar v0.4.43
[INFO] [stderr]     Checking console v0.15.10
[INFO] [stderr]     Checking condtype v1.3.0
[INFO] [stderr]     Checking regex-lite v0.1.6
[INFO] [stderr]    Compiling uuid v1.11.0
[INFO] [stderr]     Checking inquire v0.7.5
[INFO] [stderr]    Compiling comparable_helper v0.5.5 (https://github.com/jwiegley/comparable.git?rev=refs%2Fpull%2F5%2Fhead#b6e1b62f)
[INFO] [stderr]    Compiling comparable_derive v0.5.5 (https://github.com/jwiegley/comparable.git?rev=refs%2Fpull%2F5%2Fhead#b6e1b62f)
[INFO] [stderr]     Checking regex v1.11.1
[INFO] [stderr]     Checking backtrace v0.3.74
[INFO] [stderr]     Checking parse_link_header v0.4.0
[INFO] [stderr]     Checking backtrace-ext v0.2.1
[INFO] [stderr]     Checking rustls-webpki v0.102.8
[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 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 clap_derive v4.5.18
[INFO] [stderr]    Compiling enum-ordinalize-derive v4.3.1
[INFO] [stderr]    Compiling structmeta-derive v0.3.0
[INFO] [stderr]    Compiling struct-patch-derive v0.8.6
[INFO] [stderr]    Compiling strum_macros v0.26.4
[INFO] [stderr]    Compiling proptest-macro v0.1.0
[INFO] [stderr]    Compiling zerofrom-derive v0.1.5
[INFO] [stderr]    Compiling yoke-derive v0.7.5
[INFO] [stderr]    Compiling proptest-derive v0.5.0 (https://github.com/proptest-rs/proptest.git?rev=refs%2Fpull%2F530%2Fhead#4e6d6cd8)
[INFO] [stderr]     Checking struct-patch v0.8.6
[INFO] [stderr]    Compiling remain v0.2.14
[INFO] [stderr]    Compiling schemars_derive v0.8.21
[INFO] [stderr]    Compiling thiserror-impl v1.0.69
[INFO] [stderr]     Checking arbitrary v1.4.1
[INFO] [stderr]     Checking zerocopy v0.7.35
[INFO] [stderr]    Compiling enum-ordinalize v4.3.0
[INFO] [stderr]    Compiling educe v0.6.0
[INFO] [stderr]    Compiling structmeta v0.3.0
[INFO] [stderr]    Compiling futures-macro v0.3.31
[INFO] [stderr]    Compiling test-strategy v0.4.0
[INFO] [stderr]    Compiling tokio-macros v2.4.0
[INFO] [stderr]    Compiling tracing-attributes v0.1.28
[INFO] [stderr]     Checking ppv-lite86 v0.2.20
[INFO] [stderr]     Checking zerofrom v0.1.5
[INFO] [stderr]    Compiling miette-derive v7.4.0
[INFO] [stderr]    Compiling snafu-derive v0.8.5
[INFO] [stderr]    Compiling pin-project-internal v1.1.8
[INFO] [stderr]     Checking tokio v1.42.0
[INFO] [stderr]     Checking yoke v0.7.5
[INFO] [stderr]     Checking clap v4.5.23
[INFO] [stderr]    Compiling async-trait v0.1.85
[INFO] [stderr]    Compiling divan-macros v0.1.17
[INFO] [stderr]     Checking strum v0.26.3
[INFO] [stderr]     Checking zerovec v0.10.4
[INFO] [stderr]     Checking futures-util v0.3.31
[INFO] [stderr]    Compiling darling_macro v0.20.10
[INFO] [stderr]    Compiling darling v0.20.10
[INFO] [stderr]    Compiling derive_builder_core v0.20.2
[INFO] [stderr]    Compiling dummy v0.9.1
[INFO] [stderr]    Compiling validator_derive v0.19.0
[INFO] [stderr]    Compiling serde_with_macros v3.12.0
[INFO] [stderr]     Checking tracing v0.1.41
[INFO] [stderr]     Checking pin-project v1.1.8
[INFO] [stderr]     Checking tinystr v0.7.6
[INFO] [stderr]     Checking icu_collections v1.5.0
[INFO] [stderr]     Checking icu_locid v1.5.0
[INFO] [stderr]     Checking divan v0.1.17
[INFO] [stderr]     Checking icu_provider v1.5.0
[INFO] [stderr]     Checking icu_locid_transform v1.5.0
[INFO] [stderr]    Compiling derive_builder_macro v0.20.2
[INFO] [stderr]     Checking snafu v0.8.5
[INFO] [stderr]     Checking derive_builder v0.20.2
[INFO] [stderr]     Checking icu_properties v1.5.1
[INFO] [stderr]     Checking futures-executor v0.3.31
[INFO] [stderr]     Checking http-body-util v0.1.2
[INFO] [stderr]     Checking futures v0.3.31
[INFO] [stderr]     Checking hyper v1.5.2
[INFO] [stderr]     Checking tokio-util v0.7.13
[INFO] [stderr]     Checking tokio-rustls v0.26.1
[INFO] [stderr]     Checking icu_normalizer v1.5.0
[INFO] [stderr]     Checking tower v0.5.2
[INFO] [stderr]     Checking indexmap v2.7.0
[INFO] [stderr]     Checking rand_core v0.6.4
[INFO] [stderr]     Checking chrono v0.4.39
[INFO] [stderr]     Checking email_address v0.2.9
[INFO] [stderr]     Checking mediatype v0.19.18
[INFO] [stderr]     Checking comparable v0.5.5 (https://github.com/jwiegley/comparable.git?rev=refs%2Fpull%2F5%2Fhead#b6e1b62f)
[INFO] [stderr]     Checking deranged v0.3.11
[INFO] [stderr]     Checking iri-string v0.7.7
[INFO] [stderr]     Checking base64urlsafedata v0.5.1
[INFO] [stderr]     Checking serde_urlencoded v0.7.1
[INFO] [stderr]     Checking serde_with v3.12.0
[INFO] [stderr]     Checking serde_qs v0.13.0
[INFO] [stderr]     Checking idna_adapter v1.2.0
[INFO] [stderr]     Checking humantime-serde v1.1.1
[INFO] [stderr]     Checking rand_chacha v0.3.1
[INFO] [stderr]     Checking idna v1.0.3
[INFO] [stderr]     Checking rand_xorshift v0.3.0
[INFO] [stderr]     Checking miette v7.4.0
[INFO] [stderr]     Checking serde_path_to_error v0.1.16
[INFO] [stderr]     Checking rand v0.8.5
[INFO] [stderr]     Checking hyper-util v0.1.10
[INFO] [stderr]     Checking url v2.5.4
[INFO] [stderr]     Checking proptest v1.5.0 (https://github.com/proptest-rs/proptest.git?rev=refs%2Fpull%2F530%2Fhead#4e6d6cd8)
[INFO] [stderr]     Checking time v0.3.36
[INFO] [stderr]     Checking fake v3.1.0
[INFO] [stderr]     Checking validator v0.19.0
[INFO] [stderr]     Checking ureq v2.12.1
[INFO] [stderr]     Checking tower-http v0.6.2
[INFO] [stderr]     Checking hyper-rustls v0.27.5
[INFO] [stderr]     Checking hyper-timeout v0.5.2
[INFO] [stderr]     Checking update-informer v1.2.0
[INFO] [stderr]     Checking simple_asn1 v0.6.2
[INFO] [stderr]     Checking jsonwebtoken v9.3.0
[INFO] [stderr]    Compiling utoipa-gen v4.3.1
[INFO] [stderr]     Checking eio-okta-data v0.2.1 (/opt/rustwide/workdir/eio-okta-data)
[INFO] [stderr]     Checking octocrab v0.42.1
[INFO] [stdout] warning: unexpected `cfg` condition value: `merge`
[INFO] [stdout]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: `#[warn(unexpected_cfgs)]` on by default
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]   --> eio-okta-data/src/lib.rs:59:47
[INFO] [stdout]    |
[INFO] [stdout] 59 |     #[cfg_attr(feature = "patch",      derive(::struct_patch::Patch))]
[INFO] [stdout]    |                                               ^^^^^^^^^^^^^^^^^^^^^
[INFO] [stdout]    |
[INFO] [stdout]   ::: eio-okta-data/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 <https://doc.rust-lang.org/nightly/rustc/check-cfg/cargo-specifics.html> for more information about checking conditional configuration
[INFO] [stdout]    = note: this warning originates in the derive macro `::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]     Checking utoipa v4.2.3
[INFO] [stderr]     Checking scim_proto v1.4.5
[INFO] [stderr]     Checking eio-okta-api v0.2.1 (/opt/rustwide/workdir/eio-okta-api)
[INFO] [stderr]     Checking eio-okta-client v0.2.1 (/opt/rustwide/workdir/eio-okta-client)
[INFO] [stderr]     Checking eio-okta-sync v0.4.1 (/opt/rustwide/workdir/eio-okta-sync)
[INFO] [stderr]     Finished `dev` profile [unoptimized + debuginfo] target(s) in 1m 01s
[INFO] running `Command { std: "docker" "inspect" "fb53d88d73c461d5aabf52c52f6e6ab7c23022d6fdca4b4c61085605ada9bd95", kill_on_drop: false }`
[INFO] running `Command { std: "docker" "rm" "-f" "fb53d88d73c461d5aabf52c52f6e6ab7c23022d6fdca4b4c61085605ada9bd95", kill_on_drop: false }`
[INFO] [stdout] fb53d88d73c461d5aabf52c52f6e6ab7c23022d6fdca4b4c61085605ada9bd95
