[INFO] cloning repository https://github.com/binfengke/Solana-Defi-Vault [INFO] running `Command { std: "git" "-c" "credential.helper=" "-c" "credential.helper=/workspace/cargo-home/bin/git-credential-null" "clone" "--bare" "https://github.com/binfengke/Solana-Defi-Vault" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fbinfengke%2FSolana-Defi-Vault", kill_on_drop: false }` [INFO] [stderr] Cloning into bare repository '/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fbinfengke%2FSolana-Defi-Vault'... [INFO] running `Command { std: "git" "rev-parse" "HEAD", kill_on_drop: false }` [INFO] [stdout] 60cc3a8784627e95df307ef9cd8f612fa9a3aeda [INFO] checking binfengke/Solana-Defi-Vault against 344f7902949345394fa40a5d7dda31f012ccbc0d for pr-161946 [INFO] running `Command { std: "git" "clone" "/workspace/cache/git-repos/https%3A%2F%2Fgithub.com%2Fbinfengke%2FSolana-Defi-Vault" "/workspace/builds/worker-1-tc1/source", kill_on_drop: false }` [INFO] [stderr] Cloning into '/workspace/builds/worker-1-tc1/source'... [INFO] [stderr] done. [INFO] removed /workspace/builds/worker-1-tc1/source/.cargo/config.toml [INFO] started tweaking git repo https://github.com/binfengke/Solana-Defi-Vault [INFO] finished tweaking git repo https://github.com/binfengke/Solana-Defi-Vault [INFO] tweaked toml for git repo https://github.com/binfengke/Solana-Defi-Vault written to /workspace/builds/worker-1-tc1/source/Cargo.toml [INFO] validating manifest of git repo https://github.com/binfengke/Solana-Defi-Vault on toolchain 344f7902949345394fa40a5d7dda31f012ccbc0d [INFO] running `Command { std: CARGO_HOME="/workspace/cargo-home" RUSTUP_HOME="/workspace/rustup-home" "/workspace/cargo-home/bin/cargo" "+344f7902949345394fa40a5d7dda31f012ccbc0d" "metadata" "--manifest-path" "Cargo.toml" "--no-deps", kill_on_drop: false }` [INFO] crate git repo https://github.com/binfengke/Solana-Defi-Vault 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" "+344f7902949345394fa40a5d7dda31f012ccbc0d" "fetch" "--manifest-path" "Cargo.toml", kill_on_drop: false }` [INFO] [stderr] Updating git repository `https://github.com/BLAKE3-team/BLAKE3` [INFO] [stderr] Updating git repository `https://github.com/rust-lang/jobserver-rs` [INFO] [stderr] Updating git repository `https://github.com/toml-rs/toml` [INFO] [stderr] warning: patch `toml_edit v0.21.1 (https://github.com/toml-rs/toml?rev=v0.21.1#f5c6f4b4)` was not used in the crate graph [INFO] [stderr] help: Check that the patched package version and available features are compatible [INFO] [stderr] with the dependency requirements. If the patch has a different version from [INFO] [stderr] what is locked in the Cargo.lock file, run `cargo update` to use the new [INFO] [stderr] version. This may also occur with an optional dependency that is not enabled. [INFO] [stderr] Downloading crates ... [INFO] [stderr] Downloaded zmij v1.0.19 [INFO] [stderr] Downloaded regex-syntax v0.8.9 [INFO] running `Command { std: "docker" "create" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-tc1/source:/opt/rustwide/workdir:ro,Z" "-v" "/var/lib/crater-agent-workspace/builds/worker-1-tc1/target:/opt/rustwide/target:rw,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" "-m" "1610612736" "--network" "none" "ghcr.io/rust-lang/crates-build-env/linux@sha256:8683fc1fc2eb5c9ac98e0d076ab094b2ffac7f99da555d2b6a2e27f346de2ec7" "sleep" "infinity", kill_on_drop: false }` [INFO] [stdout] a7763daa8b56b98270978ad17c38439c6505ae2b1c866c4861f19195dac03a70 [INFO] running `Command { std: "docker" "start" "a7763daa8b56b98270978ad17c38439c6505ae2b1c866c4861f19195dac03a70", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "a7763daa8b56b98270978ad17c38439c6505ae2b1c866c4861f19195dac03a70", kill_on_drop: false }` [INFO] running `Command { std: "docker" "exec" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-e" "CARGO_TARGET_DIR=/opt/rustwide/target" "-w" "/opt/rustwide/workdir" "--user" "0:0" "a7763daa8b56b98270978ad17c38439c6505ae2b1c866c4861f19195dac03a70" "/opt/rustwide/cargo-home/bin/cargo" "+344f7902949345394fa40a5d7dda31f012ccbc0d" "metadata" "--no-deps" "--format-version=1", kill_on_drop: false }` [INFO] running `Command { std: "docker" "inspect" "a7763daa8b56b98270978ad17c38439c6505ae2b1c866c4861f19195dac03a70", kill_on_drop: false }` [INFO] running `Command { std: "docker" "exec" "-e" "SOURCE_DIR=/opt/rustwide/workdir" "-e" "CARGO_HOME=/opt/rustwide/cargo-home" "-e" "RUSTUP_HOME=/opt/rustwide/rustup-home" "-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" "-w" "/opt/rustwide/workdir" "--user" "0:0" "a7763daa8b56b98270978ad17c38439c6505ae2b1c866c4861f19195dac03a70" "/opt/rustwide/cargo-home/bin/cargo" "+344f7902949345394fa40a5d7dda31f012ccbc0d" "check" "--frozen" "--all" "--all-targets" "--message-format=json", kill_on_drop: false }` [INFO] [stderr] warning: patch `toml_edit v0.21.1 (https://github.com/toml-rs/toml?rev=v0.21.1#f5c6f4b4)` was not used in the crate graph [INFO] [stderr] help: Check that the patched package version and available features are compatible [INFO] [stderr] with the dependency requirements. If the patch has a different version from [INFO] [stderr] what is locked in the Cargo.lock file, run `cargo update` to use the new [INFO] [stderr] version. This may also occur with an optional dependency that is not enabled. [INFO] [stderr] Compiling zerocopy v0.8.39 [INFO] [stderr] Compiling anyhow v1.0.101 [INFO] [stderr] Compiling zmij v1.0.19 [INFO] [stderr] Compiling indexmap v2.11.4 [INFO] [stderr] Compiling jobserver v0.1.32 (https://github.com/rust-lang/jobserver-rs?tag=0.1.32#f494d826) [INFO] [stderr] Checking memchr v2.8.0 [INFO] [stderr] Checking bytemuck v1.25.0 [INFO] [stderr] Checking regex-syntax v0.8.9 [INFO] [stderr] Compiling cc v1.2.55 [INFO] [stderr] Checking aho-corasick v1.1.4 [INFO] [stderr] Checking serde_json v1.0.149 [INFO] [stderr] Compiling toml_edit v0.23.10+spec-1.0.0 [INFO] [stderr] Compiling anchor-lang-idl-spec v0.1.0 [INFO] [stderr] Checking regex-automata v0.4.14 [INFO] [stderr] Compiling proc-macro-crate v3.4.0 [INFO] [stderr] Compiling borsh-derive v1.6.0 [INFO] [stderr] Compiling num_enum_derive v0.7.5 [INFO] [stderr] Compiling blake3 v1.5.1 (https://github.com/BLAKE3-team/BLAKE3?tag=1.5.1#54930c95) [INFO] [stderr] Compiling solana-program v1.18.26 [INFO] [stderr] Compiling anchor-syn v0.30.1 (/opt/rustwide/workdir/vendor/anchor-syn) [INFO] [stderr] Compiling anchor-lang-idl v0.1.2 [INFO] [stderr] Checking num_enum v0.7.5 [INFO] [stderr] Checking borsh v1.6.0 [INFO] [stderr] Checking regex v1.12.3 [INFO] [stderr] Checking env_logger v0.9.3 [INFO] [stderr] Checking solana-logger v1.18.26 [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> vendor/anchor-syn/src/parser/context.rs:41:20 [INFO] [stdout] | [INFO] [stdout] 41 | pub fn modules(&self) -> impl Iterator { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] = note: `#[warn(mismatched_lifetime_syntaxes)]` on by default [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 41 | pub fn modules(&self) -> impl Iterator> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: hiding a lifetime that's elided elsewhere is confusing [INFO] [stdout] --> vendor/anchor-syn/src/parser/context.rs:45:24 [INFO] [stdout] | [INFO] [stdout] 45 | pub fn root_module(&self) -> ModuleContext { [INFO] [stdout] | ^^^^^ ^^^^^^^^^^^^^ the same lifetime is hidden here [INFO] [stdout] | | [INFO] [stdout] | the lifetime is elided here [INFO] [stdout] | [INFO] [stdout] = help: the same lifetime is referred to in inconsistent ways, making the signature confusing [INFO] [stdout] help: use `'_` for type paths [INFO] [stdout] | [INFO] [stdout] 45 | pub fn root_module(&self) -> ModuleContext<'_> { [INFO] [stdout] | ++++ [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Compiling anchor-derive-accounts v0.30.1 [INFO] [stderr] Compiling anchor-derive-serde v0.30.1 [INFO] [stderr] Compiling anchor-attribute-program v0.30.1 [INFO] [stderr] Compiling anchor-attribute-constant v0.30.1 [INFO] [stderr] Compiling anchor-attribute-access-control v0.30.1 [INFO] [stderr] Compiling anchor-attribute-account v0.30.1 [INFO] [stderr] Compiling anchor-attribute-event v0.30.1 [INFO] [stderr] Compiling anchor-attribute-error v0.30.1 [INFO] [stderr] Checking ppv-lite86 v0.2.21 [INFO] [stderr] Checking ahash v0.8.12 [INFO] [stderr] Checking rand_chacha v0.3.1 [INFO] [stderr] Checking rand_chacha v0.2.2 [INFO] [stderr] Checking rand v0.8.5 [INFO] [stderr] Checking hashbrown v0.13.2 [INFO] [stderr] Checking rand v0.7.3 [INFO] [stderr] Checking borsh v0.10.4 [INFO] [stderr] Checking ark-std v0.4.0 [INFO] [stderr] Checking libsecp256k1 v0.6.0 [INFO] [stderr] Checking tiny-bip39 v0.8.2 [INFO] [stderr] Checking ed25519-dalek v1.0.1 [INFO] [stderr] Checking ark-serialize v0.4.2 [INFO] [stderr] Checking ed25519-dalek-bip32 v0.2.0 [INFO] [stderr] Checking ark-ff v0.4.2 [INFO] [stderr] Checking ark-poly v0.4.2 [INFO] [stderr] Checking ark-ec v0.4.2 [INFO] [stderr] Checking ark-bn254 v0.4.0 [INFO] [stderr] Checking light-poseidon v0.2.0 [INFO] [stderr] Checking solana-sdk v1.18.26 [INFO] [stderr] Checking spl-program-error v0.4.4 [INFO] [stderr] Checking spl-discriminator v0.2.5 [INFO] [stderr] Checking spl-memo v4.0.4 [INFO] [stderr] Checking spl-token v4.0.3 [INFO] [stderr] Checking anchor-lang v0.30.1 [INFO] [stderr] Checking solana-zk-token-sdk v1.18.26 [INFO] [stderr] Checking spl-pod v0.2.5 [INFO] [stderr] Checking spl-type-length-value v0.4.6 [INFO] [stderr] Checking spl-token-group-interface v0.2.5 [INFO] [stderr] Checking spl-tlv-account-resolution v0.6.5 [INFO] [stderr] Checking spl-token-metadata-interface v0.3.5 [INFO] [stderr] Checking spl-transfer-hook-interface v0.6.5 [INFO] [stderr] Checking spl-token-2022 v3.0.5 [INFO] [stderr] Checking spl-associated-token-account v3.0.4 [INFO] [stderr] Checking anchor-spl v0.30.1 [INFO] [stderr] Checking vault v0.1.0 (/opt/rustwide/workdir/programs/vault) [INFO] [stdout] warning: unexpected `cfg` condition value: `custom-heap` [INFO] [stdout] --> programs/vault/src/lib.rs:13:1 [INFO] [stdout] | [INFO] [stdout] 13 | #[program] [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::custom_heap_default` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `$crate::custom_heap_default` which comes from the expansion of the attribute macro `program` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `solana` [INFO] [stdout] --> programs/vault/src/lib.rs:13:1 [INFO] [stdout] | [INFO] [stdout] 13 | #[program] [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `target_os` are: `aix`, `amdhsa`, `android`, `cuda`, `cygwin`, `dragonfly`, `emscripten`, `espidf`, `freebsd`, `fuchsia`, `haiku`, `helenos`, `hermit`, `horizon`, `hurd`, `illumos`, `ios`, `l4re`, `linux`, `lynxos178`, `macos`, `managarm`, `motor`, `netbsd`, `none`, `nto`, `nuttx`, `openbsd`, `psp`, `psx`, `qnx`, `qurt`, `redox`, `rtems`, and `solaris` and 15 more [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::custom_heap_default` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::custom_heap_default` which comes from the expansion of the attribute macro `program` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `custom-panic` [INFO] [stdout] --> programs/vault/src/lib.rs:13:1 [INFO] [stdout] | [INFO] [stdout] 13 | #[program] [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::custom_panic_default` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::custom_panic_default` which comes from the expansion of the attribute macro `program` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `solana` [INFO] [stdout] --> programs/vault/src/lib.rs:13:1 [INFO] [stdout] | [INFO] [stdout] 13 | #[program] [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `target_os` are: `aix`, `amdhsa`, `android`, `cuda`, `cygwin`, `dragonfly`, `emscripten`, `espidf`, `freebsd`, `fuchsia`, `haiku`, `helenos`, `hermit`, `horizon`, `hurd`, `illumos`, `ios`, `l4re`, `linux`, `lynxos178`, `macos`, `managarm`, `motor`, `netbsd`, `none`, `nto`, `nuttx`, `openbsd`, `psp`, `psx`, `qnx`, `qurt`, `redox`, `rtems`, and `solaris` and 15 more [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::custom_panic_default` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::custom_panic_default` which comes from the expansion of the attribute macro `program` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/instructions/admin/initialize.rs:8:10 [INFO] [stdout] | [INFO] [stdout] 8 | #[derive(Accounts)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/instructions/admin/create_pool.rs:9:10 [INFO] [stdout] | [INFO] [stdout] 9 | #[derive(Accounts)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/instructions/admin/emergency.rs:11:10 [INFO] [stdout] | [INFO] [stdout] 11 | #[derive(Accounts)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/instructions/admin/emergency.rs:50:10 [INFO] [stdout] | [INFO] [stdout] 50 | #[derive(Accounts)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/instructions/admin/emergency.rs:90:10 [INFO] [stdout] | [INFO] [stdout] 90 | #[derive(Accounts)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/instructions/admin/emergency.rs:184:10 [INFO] [stdout] | [INFO] [stdout] 184 | #[derive(Accounts)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/instructions/admin/emergency.rs:219:10 [INFO] [stdout] | [INFO] [stdout] 219 | #[derive(Accounts)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/instructions/admin/update_config.rs:7:10 [INFO] [stdout] | [INFO] [stdout] 7 | #[derive(Accounts)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/instructions/admin/close.rs:7:10 [INFO] [stdout] | [INFO] [stdout] 7 | #[derive(Accounts)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/instructions/admin/close.rs:43:10 [INFO] [stdout] | [INFO] [stdout] 43 | #[derive(Accounts)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/instructions/operator/inject_yield.rs:9:10 [INFO] [stdout] | [INFO] [stdout] 9 | #[derive(Accounts)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/instructions/operator/inject_yield.rs:119:10 [INFO] [stdout] | [INFO] [stdout] 119 | #[derive(Accounts)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/instructions/operator/inject_yield.rs:205:10 [INFO] [stdout] | [INFO] [stdout] 205 | #[derive(Accounts)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/instructions/operator/process_queue.rs:9:10 [INFO] [stdout] | [INFO] [stdout] 9 | #[derive(Accounts)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/instructions/user/deposit.rs:9:10 [INFO] [stdout] | [INFO] [stdout] 9 | #[derive(Accounts)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/instructions/user/withdraw.rs:9:10 [INFO] [stdout] | [INFO] [stdout] 9 | #[derive(Accounts)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/instructions/user/withdraw.rs:197:10 [INFO] [stdout] | [INFO] [stdout] 197 | #[derive(Accounts)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/instructions/user/withdraw.rs:266:10 [INFO] [stdout] | [INFO] [stdout] 266 | #[derive(Accounts)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/instructions/views.rs:6:10 [INFO] [stdout] | [INFO] [stdout] 6 | #[derive(Accounts)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/instructions/views.rs:16:10 [INFO] [stdout] | [INFO] [stdout] 16 | #[derive(Accounts)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/lib.rs:13:1 [INFO] [stdout] | [INFO] [stdout] 13 | #[program] [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `program` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `program` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/lib.rs:13:1 [INFO] [stdout] | [INFO] [stdout] 13 | #[program] [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/lib.rs:13:1 [INFO] [stdout] | [INFO] [stdout] 13 | #[program] [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/lib.rs:13:1 [INFO] [stdout] | [INFO] [stdout] 13 | #[program] [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/lib.rs:13:1 [INFO] [stdout] | [INFO] [stdout] 13 | #[program] [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/lib.rs:13:1 [INFO] [stdout] | [INFO] [stdout] 13 | #[program] [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/lib.rs:13:1 [INFO] [stdout] | [INFO] [stdout] 13 | #[program] [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `custom-heap` [INFO] [stdout] --> programs/vault/src/lib.rs:13:1 [INFO] [stdout] | [INFO] [stdout] 13 | #[program] [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::custom_heap_default` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: `#[warn(unexpected_cfgs)]` on by default [INFO] [stdout] = note: this warning originates in the macro `$crate::custom_heap_default` which comes from the expansion of the attribute macro `program` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `solana` [INFO] [stdout] --> programs/vault/src/lib.rs:13:1 [INFO] [stdout] | [INFO] [stdout] 13 | #[program] [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `target_os` are: `aix`, `amdhsa`, `android`, `cuda`, `cygwin`, `dragonfly`, `emscripten`, `espidf`, `freebsd`, `fuchsia`, `haiku`, `helenos`, `hermit`, `horizon`, `hurd`, `illumos`, `ios`, `l4re`, `linux`, `lynxos178`, `macos`, `managarm`, `motor`, `netbsd`, `none`, `nto`, `nuttx`, `openbsd`, `psp`, `psx`, `qnx`, `qurt`, `redox`, `rtems`, and `solaris` and 15 more [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::custom_heap_default` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::custom_heap_default` which comes from the expansion of the attribute macro `program` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `custom-panic` [INFO] [stdout] --> programs/vault/src/lib.rs:13:1 [INFO] [stdout] | [INFO] [stdout] 13 | #[program] [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::custom_panic_default` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::custom_panic_default` which comes from the expansion of the attribute macro `program` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `solana` [INFO] [stdout] --> programs/vault/src/lib.rs:13:1 [INFO] [stdout] | [INFO] [stdout] 13 | #[program] [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `target_os` are: `aix`, `amdhsa`, `android`, `cuda`, `cygwin`, `dragonfly`, `emscripten`, `espidf`, `freebsd`, `fuchsia`, `haiku`, `helenos`, `hermit`, `horizon`, `hurd`, `illumos`, `ios`, `l4re`, `linux`, `lynxos178`, `macos`, `managarm`, `motor`, `netbsd`, `none`, `nto`, `nuttx`, `openbsd`, `psp`, `psx`, `qnx`, `qurt`, `redox`, `rtems`, and `solaris` and 15 more [INFO] [stdout] = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `$crate::custom_panic_default` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the macro `$crate::custom_panic_default` which comes from the expansion of the attribute macro `program` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/instructions/admin/initialize.rs:8:10 [INFO] [stdout] | [INFO] [stdout] 8 | #[derive(Accounts)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/instructions/admin/create_pool.rs:9:10 [INFO] [stdout] | [INFO] [stdout] 9 | #[derive(Accounts)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/instructions/admin/emergency.rs:11:10 [INFO] [stdout] | [INFO] [stdout] 11 | #[derive(Accounts)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/instructions/admin/emergency.rs:50:10 [INFO] [stdout] | [INFO] [stdout] 50 | #[derive(Accounts)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/instructions/admin/emergency.rs:90:10 [INFO] [stdout] | [INFO] [stdout] 90 | #[derive(Accounts)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/instructions/admin/emergency.rs:184:10 [INFO] [stdout] | [INFO] [stdout] 184 | #[derive(Accounts)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/instructions/admin/emergency.rs:219:10 [INFO] [stdout] | [INFO] [stdout] 219 | #[derive(Accounts)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/instructions/admin/update_config.rs:7:10 [INFO] [stdout] | [INFO] [stdout] 7 | #[derive(Accounts)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/instructions/admin/close.rs:7:10 [INFO] [stdout] | [INFO] [stdout] 7 | #[derive(Accounts)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/instructions/admin/close.rs:43:10 [INFO] [stdout] | [INFO] [stdout] 43 | #[derive(Accounts)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/instructions/operator/inject_yield.rs:9:10 [INFO] [stdout] | [INFO] [stdout] 9 | #[derive(Accounts)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/instructions/operator/inject_yield.rs:119:10 [INFO] [stdout] | [INFO] [stdout] 119 | #[derive(Accounts)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/instructions/operator/inject_yield.rs:205:10 [INFO] [stdout] | [INFO] [stdout] 205 | #[derive(Accounts)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/instructions/operator/process_queue.rs:9:10 [INFO] [stdout] | [INFO] [stdout] 9 | #[derive(Accounts)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/instructions/user/deposit.rs:9:10 [INFO] [stdout] | [INFO] [stdout] 9 | #[derive(Accounts)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/instructions/user/withdraw.rs:9:10 [INFO] [stdout] | [INFO] [stdout] 9 | #[derive(Accounts)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/instructions/user/withdraw.rs:197:10 [INFO] [stdout] | [INFO] [stdout] 197 | #[derive(Accounts)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/instructions/user/withdraw.rs:266:10 [INFO] [stdout] | [INFO] [stdout] 266 | #[derive(Accounts)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/instructions/views.rs:6:10 [INFO] [stdout] | [INFO] [stdout] 6 | #[derive(Accounts)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/instructions/views.rs:16:10 [INFO] [stdout] | [INFO] [stdout] 16 | #[derive(Accounts)] [INFO] [stdout] | ^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/lib.rs:13:1 [INFO] [stdout] | [INFO] [stdout] 13 | #[program] [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `program` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the attribute macro `program` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/lib.rs:13:1 [INFO] [stdout] | [INFO] [stdout] 13 | #[program] [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/lib.rs:13:1 [INFO] [stdout] | [INFO] [stdout] 13 | #[program] [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/lib.rs:13:1 [INFO] [stdout] | [INFO] [stdout] 13 | #[program] [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/lib.rs:13:1 [INFO] [stdout] | [INFO] [stdout] 13 | #[program] [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/lib.rs:13:1 [INFO] [stdout] | [INFO] [stdout] 13 | #[program] [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stdout] warning: unexpected `cfg` condition value: `anchor-debug` [INFO] [stdout] --> programs/vault/src/lib.rs:13:1 [INFO] [stdout] | [INFO] [stdout] 13 | #[program] [INFO] [stdout] | ^^^^^^^^^^ [INFO] [stdout] | [INFO] [stdout] = note: expected values for `feature` are: `cpi`, `default`, `idl-build`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` [INFO] [stdout] = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate [INFO] [stdout] = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg [INFO] [stdout] = note: see for more information about checking conditional configuration [INFO] [stdout] = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) [INFO] [stdout] [INFO] [stdout] [INFO] [stderr] Finished `dev` profile [unoptimized + debuginfo] target(s) in 1m 00s [INFO] [stderr] warning: the following packages contain code that will be rejected by a future version of Rust: borsh v1.6.0 [INFO] [stderr] note: to see what the problems were, use the option `--future-incompat-report`, or run `cargo report future-incompatibilities --id 4` [INFO] running `Command { std: "docker" "inspect" "a7763daa8b56b98270978ad17c38439c6505ae2b1c866c4861f19195dac03a70", kill_on_drop: false }` [INFO] running `Command { std: "docker" "rm" "-f" "a7763daa8b56b98270978ad17c38439c6505ae2b1c866c4861f19195dac03a70", kill_on_drop: false }` [INFO] [stdout] a7763daa8b56b98270978ad17c38439c6505ae2b1c866c4861f19195dac03a70