warning: Patch `solana-nostd-secp256k1-recover v0.1.1 (https://github.com/jupnet/solana-nostd-secp256k1-recover.git#4675e623)` was not used in the crate graph. Check that the patched package version and available features are compatible with the dependency requirements. If the patch has a different version from what is locked in the Cargo.lock file, run `cargo update` to use the new version. This may also occur with an optional dependency that is not enabled. Compiling jupnet-bank v0.1.0 (/home/newby/projects/raccoons.dev/jupnet/infra/build-server/os/contracts-v2/external-contracts/solana/programs/bank) warning: unexpected `cfg` condition value: `anchor-debug` --> /home/newby/projects/raccoons.dev/jupnet/infra/build-server/os/contracts-v2/external-contracts/solana/programs/bank/src/instructions/close_request_buffer.rs:18:10 | 18 | #[derive(Accounts)] | ^^^^^^^^ | = note: expected values for `feature` are: `cpi`, `default`, `devnet`, `dummy-for-ci-check`, `frozen-abi`, `idl-build`, `mainnet`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg = help: the derive macro `Accounts` may come from an old version of the `anchor_derive_accounts` crate, try updating your dependency with `cargo update -p anchor_derive_accounts` = note: see for more information about checking conditional configuration = note: `#[warn(unexpected_cfgs)]` on by default = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `anchor-debug` --> /home/newby/projects/raccoons.dev/jupnet/infra/build-server/os/contracts-v2/external-contracts/solana/programs/bank/src/instructions/create_or_append_request_buffer.rs:123:10 | 123 | #[derive(Accounts)] | ^^^^^^^^ | = note: expected values for `feature` are: `cpi`, `default`, `devnet`, `dummy-for-ci-check`, `frozen-abi`, `idl-build`, `mainnet`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg = help: the derive macro `Accounts` may come from an old version of the `anchor_derive_accounts` crate, try updating your dependency with `cargo update -p anchor_derive_accounts` = note: see for more information about checking conditional configuration = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `anchor-debug` --> /home/newby/projects/raccoons.dev/jupnet/infra/build-server/os/contracts-v2/external-contracts/solana/programs/bank/src/instructions/invalidate_request.rs:195:10 | 195 | #[derive(Accounts)] | ^^^^^^^^ | = note: expected values for `feature` are: `cpi`, `default`, `devnet`, `dummy-for-ci-check`, `frozen-abi`, `idl-build`, `mainnet`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg = help: the derive macro `Accounts` may come from an old version of the `anchor_derive_accounts` crate, try updating your dependency with `cargo update -p anchor_derive_accounts` = note: see for more information about checking conditional configuration = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `anchor-debug` --> /home/newby/projects/raccoons.dev/jupnet/infra/build-server/os/contracts-v2/external-contracts/solana/programs/bank/src/instructions/request.rs:277:10 | 277 | #[derive(Accounts)] | ^^^^^^^^ | = note: expected values for `feature` are: `cpi`, `default`, `devnet`, `dummy-for-ci-check`, `frozen-abi`, `idl-build`, `mainnet`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg = help: the derive macro `Accounts` may come from an old version of the `anchor_derive_accounts` crate, try updating your dependency with `cargo update -p anchor_derive_accounts` = note: see for more information about checking conditional configuration = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `anchor-debug` --> /home/newby/projects/raccoons.dev/jupnet/infra/build-server/os/contracts-v2/external-contracts/solana/programs/bank/src/instructions/sweep.rs:144:10 | 144 | #[derive(Accounts)] | ^^^^^^^^ | = note: expected values for `feature` are: `cpi`, `default`, `devnet`, `dummy-for-ci-check`, `frozen-abi`, `idl-build`, `mainnet`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg = help: the derive macro `Accounts` may come from an old version of the `anchor_derive_accounts` crate, try updating your dependency with `cargo update -p anchor_derive_accounts` = note: see for more information about checking conditional configuration = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `anchor-debug` --> /home/newby/projects/raccoons.dev/jupnet/infra/build-server/os/contracts-v2/external-contracts/solana/programs/bank/src/instructions/toggle_bank_state.rs:30:10 | 30 | #[derive(Accounts)] | ^^^^^^^^ | = note: expected values for `feature` are: `cpi`, `default`, `devnet`, `dummy-for-ci-check`, `frozen-abi`, `idl-build`, `mainnet`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg = help: the derive macro `Accounts` may come from an old version of the `anchor_derive_accounts` crate, try updating your dependency with `cargo update -p anchor_derive_accounts` = note: see for more information about checking conditional configuration = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `anchor-debug` --> /home/newby/projects/raccoons.dev/jupnet/infra/build-server/os/contracts-v2/external-contracts/solana/programs/bank/src/lib.rs:16:1 | 16 | #[program] | ^^^^^^^^^^ | = note: expected values for `feature` are: `cpi`, `default`, `devnet`, `dummy-for-ci-check`, `frozen-abi`, `idl-build`, `mainnet`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `program` crate for guidance on how handle this unexpected cfg = help: the attribute macro `program` may come from an old version of the `anchor_attribute_program` crate, try updating your dependency with `cargo update -p anchor_attribute_program` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `program` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `anchor-debug` --> /home/newby/projects/raccoons.dev/jupnet/infra/build-server/os/contracts-v2/external-contracts/solana/programs/bank/src/lib.rs:16:1 | 16 | #[program] | ^^^^^^^^^^ | = note: expected values for `feature` are: `cpi`, `default`, `devnet`, `dummy-for-ci-check`, `frozen-abi`, `idl-build`, `mainnet`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg = help: the derive macro `Accounts` may come from an old version of the `anchor_derive_accounts` crate, try updating your dependency with `cargo update -p anchor_derive_accounts` = note: see for more information about checking conditional configuration = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) warning: `jupnet-bank` (lib) generated 13 warnings (5 duplicates) Compiling common v0.1.0 (/home/newby/projects/raccoons.dev/jupnet/infra/build-server/os/services/common) Compiling jupnet-implementation-1 v0.1.0 (/home/newby/projects/raccoons.dev/jupnet/infra/build-server/os/contracts-v2/external-contracts/solana/programs/jupnet-implementation-1) warning: unexpected `cfg` condition value: `custom-heap` --> /home/newby/projects/raccoons.dev/jupnet/infra/build-server/os/contracts-v2/external-contracts/solana/programs/jupnet-implementation-1/src/lib.rs:16:1 | 16 | #[program] | ^^^^^^^^^^ | = note: expected values for `feature` are: `cpi`, `default`, `devnet`, `dummy-for-ci-check`, `frozen-abi`, `idl-build`, `mainnet`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `$crate::custom_heap_default` crate for guidance on how handle this unexpected cfg = help: the macro `$crate::custom_heap_default` may come from an old version of the `solana_program_entrypoint` crate, try updating your dependency with `cargo update -p solana_program_entrypoint` = note: see for more information about checking conditional configuration = note: `#[warn(unexpected_cfgs)]` on by default = 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) warning: unexpected `cfg` condition value: `solana` --> /home/newby/projects/raccoons.dev/jupnet/infra/build-server/os/contracts-v2/external-contracts/solana/programs/jupnet-implementation-1/src/lib.rs:16:1 | 16 | #[program] | ^^^^^^^^^^ | = note: expected values for `target_os` are: `aix`, `amdhsa`, `android`, `cuda`, `cygwin`, `dragonfly`, `emscripten`, `espidf`, `freebsd`, `fuchsia`, `haiku`, `hermit`, `horizon`, `hurd`, `illumos`, `ios`, `l4re`, `linux`, `lynxos178`, `macos`, `managarm`, `netbsd`, `none`, `nto`, `nuttx`, `openbsd`, `psp`, `psx`, `redox`, `rtems`, `solaris`, `solid_asp3`, `teeos`, `trusty`, and `tvos` and 11 more = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `$crate::custom_heap_default` crate for guidance on how handle this unexpected cfg = help: the macro `$crate::custom_heap_default` may come from an old version of the `solana_program_entrypoint` crate, try updating your dependency with `cargo update -p solana_program_entrypoint` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition value: `custom-panic` --> /home/newby/projects/raccoons.dev/jupnet/infra/build-server/os/contracts-v2/external-contracts/solana/programs/jupnet-implementation-1/src/lib.rs:16:1 | 16 | #[program] | ^^^^^^^^^^ | = note: expected values for `feature` are: `cpi`, `default`, `devnet`, `dummy-for-ci-check`, `frozen-abi`, `idl-build`, `mainnet`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `$crate::custom_panic_default` crate for guidance on how handle this unexpected cfg = help: the macro `$crate::custom_panic_default` may come from an old version of the `solana_program_entrypoint` crate, try updating your dependency with `cargo update -p solana_program_entrypoint` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition value: `solana` --> /home/newby/projects/raccoons.dev/jupnet/infra/build-server/os/contracts-v2/external-contracts/solana/programs/jupnet-implementation-1/src/lib.rs:16:1 | 16 | #[program] | ^^^^^^^^^^ | = note: expected values for `target_os` are: `aix`, `amdhsa`, `android`, `cuda`, `cygwin`, `dragonfly`, `emscripten`, `espidf`, `freebsd`, `fuchsia`, `haiku`, `hermit`, `horizon`, `hurd`, `illumos`, `ios`, `l4re`, `linux`, `lynxos178`, `macos`, `managarm`, `netbsd`, `none`, `nto`, `nuttx`, `openbsd`, `psp`, `psx`, `redox`, `rtems`, `solaris`, `solid_asp3`, `teeos`, `trusty`, and `tvos` and 11 more = note: using a cfg inside a macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `$crate::custom_panic_default` crate for guidance on how handle this unexpected cfg = help: the macro `$crate::custom_panic_default` may come from an old version of the `solana_program_entrypoint` crate, try updating your dependency with `cargo update -p solana_program_entrypoint` = note: see for more information about checking conditional configuration = 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) warning: unexpected `cfg` condition value: `anchor-debug` --> /home/newby/projects/raccoons.dev/jupnet/infra/build-server/os/contracts-v2/external-contracts/solana/programs/jupnet-implementation-1/src/instructions/complete_swap.rs:82:10 | 82 | #[derive(Accounts)] | ^^^^^^^^ | = note: expected values for `feature` are: `cpi`, `default`, `devnet`, `dummy-for-ci-check`, `frozen-abi`, `idl-build`, `mainnet`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg = help: the derive macro `Accounts` may come from an old version of the `anchor_derive_accounts` crate, try updating your dependency with `cargo update -p anchor_derive_accounts` = note: see for more information about checking conditional configuration = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `anchor-debug` --> /home/newby/projects/raccoons.dev/jupnet/infra/build-server/os/contracts-v2/external-contracts/solana/programs/jupnet-implementation-1/src/instructions/initiate_flash_fill.rs:234:10 | 234 | #[derive(Accounts)] | ^^^^^^^^ | = note: expected values for `feature` are: `cpi`, `default`, `devnet`, `dummy-for-ci-check`, `frozen-abi`, `idl-build`, `mainnet`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg = help: the derive macro `Accounts` may come from an old version of the `anchor_derive_accounts` crate, try updating your dependency with `cargo update -p anchor_derive_accounts` = note: see for more information about checking conditional configuration = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `anchor-debug` --> /home/newby/projects/raccoons.dev/jupnet/infra/build-server/os/contracts-v2/external-contracts/solana/programs/jupnet-implementation-1/src/instructions/withdraw.rs:189:10 | 189 | #[derive(Accounts)] | ^^^^^^^^ | = note: expected values for `feature` are: `cpi`, `default`, `devnet`, `dummy-for-ci-check`, `frozen-abi`, `idl-build`, `mainnet`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg = help: the derive macro `Accounts` may come from an old version of the `anchor_derive_accounts` crate, try updating your dependency with `cargo update -p anchor_derive_accounts` = note: see for more information about checking conditional configuration = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `anchor-debug` --> /home/newby/projects/raccoons.dev/jupnet/infra/build-server/os/contracts-v2/external-contracts/solana/programs/jupnet-implementation-1/src/lib.rs:16:1 | 16 | #[program] | ^^^^^^^^^^ | = note: expected values for `feature` are: `cpi`, `default`, `devnet`, `dummy-for-ci-check`, `frozen-abi`, `idl-build`, `mainnet`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` = note: using a cfg inside a attribute macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `program` crate for guidance on how handle this unexpected cfg = help: the attribute macro `program` may come from an old version of the `anchor_attribute_program` crate, try updating your dependency with `cargo update -p anchor_attribute_program` = note: see for more information about checking conditional configuration = note: this warning originates in the attribute macro `program` (in Nightly builds, run with -Z macro-backtrace for more info) warning: unexpected `cfg` condition value: `anchor-debug` --> /home/newby/projects/raccoons.dev/jupnet/infra/build-server/os/contracts-v2/external-contracts/solana/programs/jupnet-implementation-1/src/lib.rs:16:1 | 16 | #[program] | ^^^^^^^^^^ | = note: expected values for `feature` are: `cpi`, `default`, `devnet`, `dummy-for-ci-check`, `frozen-abi`, `idl-build`, `mainnet`, `no-entrypoint`, `no-idl`, and `no-log-ix-name` = note: using a cfg inside a derive macro will use the cfgs from the destination crate and not the ones from the defining crate = help: try referring to `Accounts` crate for guidance on how handle this unexpected cfg = help: the derive macro `Accounts` may come from an old version of the `anchor_derive_accounts` crate, try updating your dependency with `cargo update -p anchor_derive_accounts` = note: see for more information about checking conditional configuration = note: this warning originates in the derive macro `Accounts` (in Nightly builds, run with -Z macro-backtrace for more info) warning: `jupnet-implementation-1` (lib) generated 14 warnings (5 duplicates) Compiling jupnet-program-indexer v0.1.0 (/home/newby/projects/raccoons.dev/jupnet/infra/build-server/os/services/jupnet-program-indexer) Compiling data-api v0.1.0 (/home/newby/projects/raccoons.dev/jupnet/infra/build-server/os/services/data-api) Compiling runner-api-service v0.1.0 (/home/newby/projects/raccoons.dev/jupnet/infra/build-server/os/services/runner-api-service) Compiling signature-service v0.1.0 (/home/newby/projects/raccoons.dev/jupnet/infra/build-server/os/services/signature-service) Compiling mvm-poller v0.1.0 (/home/newby/projects/raccoons.dev/jupnet/infra/build-server/os/services/external-poller-services/mvm-poller) Compiling deposit-indexer v0.1.0 (/home/newby/projects/raccoons.dev/jupnet/infra/build-server/os/services/deposit-indexer) Compiling data-service v0.1.0 (/home/newby/projects/raccoons.dev/jupnet/infra/build-server/os/services/data-service) Compiling svm-strategy v0.1.0 (/home/newby/projects/raccoons.dev/jupnet/infra/build-server/os/services/external-strategy-services/svm-strategy) Compiling evm-poller v0.1.0 (/home/newby/projects/raccoons.dev/jupnet/infra/build-server/os/services/external-poller-services/evm-poller) Compiling deposit-sweeper-publisher v0.1.0 (/home/newby/projects/raccoons.dev/jupnet/infra/build-server/os/services/deposit-sweeper-publisher) Compiling relayer v0.1.0 (/home/newby/projects/raccoons.dev/jupnet/infra/build-server/os/services/relayer) Compiling sse-notification-server v0.1.0 (/home/newby/projects/raccoons.dev/jupnet/infra/build-server/os/services/sse-notification-server) Compiling diagnostic-service v0.1.0 (/home/newby/projects/raccoons.dev/jupnet/infra/build-server/os/services/diagnostic-service) Compiling multichain-receiver-listener v0.1.0 (/home/newby/projects/raccoons.dev/jupnet/infra/build-server/os/services/multichain-receiver-listener) Compiling svm-poller v0.1.0 (/home/newby/projects/raccoons.dev/jupnet/infra/build-server/os/services/external-poller-services/svm-poller) warning: unused import: `constants::DEPOSIT_ADDRESSES_SEED` --> jupnet-program-indexer/src/deposit_address_cache.rs:10:5 | 10 | constants::DEPOSIT_ADDRESSES_SEED, state::pda::deposit_addresses::DepositAddresses, | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | = note: `#[warn(unused_imports)]` (part of `#[warn(unused)]`) on by default warning: associated function `get_individual_signature` is never used --> signature-service/src/jupnet/client.rs:43:18 | 14 | impl JupnetRpcClient { | -------------------- associated function in this implementation ... 43 | pub async fn get_individual_signature( | ^^^^^^^^^^^^^^^^^^^^^^^^ | = note: `#[warn(dead_code)]` (part of `#[warn(unused)]`) on by default warning: method `fetch_individual_signatures_with_retry` is never used --> signature-service/src/jupnet/repository.rs:138:14 | 31 | impl BlsSignatureRepository { | --------------------------- method in this implementation ... 138 | async fn fetch_individual_signatures_with_retry( | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ warning: struct `ApiDoc` is never constructed --> data-api/src/server.rs:28:8 | 28 | struct ApiDoc; | ^^^^^^ | = note: `#[warn(dead_code)]` (part of `#[warn(unused)]`) on by default warning: methods `get_all_failed_claims` and `get_all_failed_sweeps` are never used --> relayer/src/db/repository.rs:1203:18 | 18 | impl PostgressRepository { | ------------------------ methods in this implementation ... 1203 | pub async fn get_all_failed_claims(&self) -> anyhow::Result> { | ^^^^^^^^^^^^^^^^^^^^^ ... 1497 | pub async fn get_all_failed_sweeps(&self) -> anyhow::Result> { | ^^^^^^^^^^^^^^^^^^^^^ | = note: `#[warn(dead_code)]` (part of `#[warn(unused)]`) on by default warning: method `create_deposit_event` is never used --> relayer/src/services/event_service.rs:112:12 | 17 | impl EventService { | ----------------- method in this implementation ... 112 | pub fn create_deposit_event( | ^^^^^^^^^^^^^^^^^^^^ warning: `signature-service` (bin "signature-service") generated 2 warnings warning: `data-api` (bin "data-api") generated 1 warning warning: `jupnet-program-indexer` (bin "jupnet-program-indexer") generated 1 warning (run `cargo fix --bin "jupnet-program-indexer"` to apply 1 suggestion) warning: `relayer` (bin "relayer") generated 2 warnings Finished `release` profile [optimized] target(s) in 56.67s