feat: batch cold account loads in light client #2018
sergeytimoshinAnnotations
16 errors and 5 warnings
|
system-programs (token test, ["cargo-test-sbf -p sdk-token-test", "cargo-test-sbf -p token-client...
Process completed with exit code 1.
|
|
system-programs (token test, ["cargo-test-sbf -p sdk-token-test", "cargo-test-sbf -p token-client...:
prover/client/src/proof_types/batch_address_append/proof_inputs.rs#L264
cannot find value `batch_len` in this scope
|
|
system-programs (token test, ["cargo-test-sbf -p sdk-token-test", "cargo-test-sbf -p token-client...:
prover/client/src/proof_types/batch_address_append/proof_inputs.rs#L229
cannot find value `batch_len` in this scope
|
|
system-programs (token test, ["cargo-test-sbf -p sdk-token-test", "cargo-test-sbf -p token-client...:
prover/client/src/proof_types/batch_address_append/proof_inputs.rs#L228
cannot find value `batch_len` in this scope
|
|
system-programs (token test, ["cargo-test-sbf -p sdk-token-test", "cargo-test-sbf -p token-client...:
prover/client/src/proof_types/batch_address_append/proof_inputs.rs#L227
cannot find value `batch_len` in this scope
|
|
system-programs (token test, ["cargo-test-sbf -p sdk-token-test", "cargo-test-sbf -p token-client...:
prover/client/src/proof_types/batch_address_append/proof_inputs.rs#L226
cannot find value `batch_len` in this scope
|
|
system-programs (token test, ["cargo-test-sbf -p sdk-token-test", "cargo-test-sbf -p token-client...:
prover/client/src/proof_types/batch_address_append/proof_inputs.rs#L225
cannot find value `batch_len` in this scope
|
|
system-programs (token test, ["cargo-test-sbf -p sdk-token-test", "cargo-test-sbf -p token-client...:
prover/client/src/proof_types/batch_address_append/proof_inputs.rs#L224
cannot find value `batch_len` in this scope
|
|
system-programs (native, ["cargo-test-sbf -p sdk-native-test", "cargo-test-sbf -p sdk-v1-native-t...
The strategy configuration was canceled because "system-programs.token_test___cargo-test-s" failed
|
|
system-programs (native, ["cargo-test-sbf -p sdk-native-test", "cargo-test-sbf -p sdk-v1-native-t...
The operation was canceled.
|
|
system-programs (sdk-libs, just sdk-libs test)
The strategy configuration was canceled because "system-programs.token_test___cargo-test-s" failed
|
|
system-programs (sdk-libs, just sdk-libs test)
The operation was canceled.
|
|
system-programs (light-account, ["cargo-test-sbf -p csdk-anchor-derived-test", "cargo-test-sbf -p...
The strategy configuration was canceled because "system-programs.token_test___cargo-test-s" failed
|
|
system-programs (light-account, ["cargo-test-sbf -p csdk-anchor-derived-test", "cargo-test-sbf -p...
The operation was canceled.
|
|
system-programs (anchor & pinocchio, ["cargo-test-sbf -p sdk-anchor-test", "cargo-test-sbf -p sdk...
The strategy configuration was canceled because "system-programs.token_test___cargo-test-s" failed
|
|
system-programs (anchor & pinocchio, ["cargo-test-sbf -p sdk-anchor-test", "cargo-test-sbf -p sdk...
The operation was canceled.
|
|
system-programs (token test, ["cargo-test-sbf -p sdk-token-test", "cargo-test-sbf -p token-client...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-node@v4, extractions/setup-just@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
system-programs (native, ["cargo-test-sbf -p sdk-native-test", "cargo-test-sbf -p sdk-v1-native-t...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-node@v4, extractions/setup-just@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
system-programs (sdk-libs, just sdk-libs test)
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-node@v4, extractions/setup-just@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
system-programs (light-account, ["cargo-test-sbf -p csdk-anchor-derived-test", "cargo-test-sbf -p...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-node@v4, extractions/setup-just@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|
|
system-programs (anchor & pinocchio, ["cargo-test-sbf -p sdk-anchor-test", "cargo-test-sbf -p sdk...
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache@v4, actions/setup-node@v4, extractions/setup-just@v2. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
|