Size limit has been exceeded.

Process completed with exit code 1.

Canceling since a higher priority waiting request for Pull request-feat/verify-hash-access-key exists

The operation was canceled.

TransactionExecutionError: Execution reverted for an unknown reason. Request Arguments: from: 0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266 Details: execution reverted Version: viem@2.47.7 ❯ getTransactionError src/utils/errors/getTransactionError.ts:44:10 ❯ sendTransactionSync src/actions/wallet/sendTransactionSync.ts:407:11 ❯ revokeRoles.inner src/tempo/actions/token.ts:2513:13 ❯ Module.revokeRolesSync src/tempo/actions/token.ts:2622:19 ❯ src/tempo/actions/token.test.ts:1531:5 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { details: 'execution reverted', docsPath: undefined, metaMessages: [ 'Request Arguments:', ' from: 0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266' ], shortMessage: 'Execution reverted for an unknown reason.', version: '2.47.7', walk: 'Function<walk>' } Caused by: ExecutionRevertedError: Execution reverted for an unknown reason. Details: execution reverted Version: viem@2.47.7 ❯ getNodeError src/utils/errors/getNodeError.ts:77:12 ❯ src/utils/errors/getTransactionError.ts:37:19 ❯ getTransactionError src/utils/errors/getTransactionError.ts:43:3 ❯ sendTransactionSync src/actions/wallet/sendTransactionSync.ts:407:11 ❯ revokeRoles.inner src/tempo/actions/token.ts:2513:13 ❯ Module.revokeRolesSync src/tempo/actions/token.ts:2622:19 ❯ src/tempo/actions/token.test.ts:1531:5 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { details: 'execution reverted', docsPath: undefined, metaMessages: undefined, shortMessage: 'Execution reverted for an unknown reason.', version: '2.47.7', walk: 'Function<walk>' } Caused by: TransactionExecutionError: Execution reverted for an unknown reason. Request Arguments: chain: Tempo (id: 1337) from: 0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266 Details: execution reverted Version: viem@2.47.7 ❯ getTransactionError src/utils/errors/getTransactionError.ts:44:10 ❯ fillTransaction src/actions/public/fillTransaction.ts:243:11 ❯ prepareTransactionRequest src/actions/wallet/prepareTransactionRequest.ts:373:7 ❯ sendTransactionSync src/actions/wallet/sendTransactionSync.ts:352:23 ❯ revokeRoles.inner src/tempo/actions/token.ts:2513:13 ❯ Module.revokeRolesSync src/tempo/actions/token.ts:2622:19 ❯ src/tempo/actions/token.test.ts:1531:5 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { details: 'execution reverted', docsPath: undefined, metaMessages: [ 'Request Arguments:', ' chain: Tempo (id: 1337)\n from: 0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266' ], shortMessage: 'Execution reverted for an unknown reason.', version: '2.47.7', walk: 'Function<walk>' } Caused by: ExecutionRevertedError: Execution reverted for an unknown reason. Details: execution reverted Version: viem@2.47.7 ❯ getNodeError src/utils/errors/getNodeError.ts:77:12 ❯ src/utils/errors/getTransactionError.ts:37:19 ❯ getTransactionError src/utils/errors/getTransactionError.ts:43:3 ❯ fillTransaction src/actions/public/fillTransaction.ts:243:11 ❯ prepareTransactionRequest src/actions/wallet/prepareTransactionRequest.ts:373:7 ❯ sendTransactionSync src/actions/wallet/sendTransactionSync.ts:352:23 ❯ revokeRoles.inner src/tempo/actions/token.ts:2513:13 ❯ Module.revokeRolesSync src/tempo/actions/token.ts:2622:19 ❯ src/tempo/actions/token.test.ts:1531:5 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { details: 'execution reverted', docsPath: undefined, metaMessages: undefined, shortMessage: 'Execution reverted for an unknown reason.', version: '2.47.7', walk: 'Function<walk>' } Caused by: RpcRequestError: RPC Request failed. URL: http://localhost:9545/1016 Request body: {"method":"eth_fillTransaction","params":[{"from":"0x8C8d35429F74ec245F8Ef2f4Fd1e551cFF97d650","type":"0x76","calls":[{"to":"0x20c000000000000000000000A03926B09f426950","value":"0x","data":"0xd547741f114e74f6ea3bd819998f78687bfcb11b1

TransactionExecutionError: Execution reverted for an unknown reason. Request Arguments: from: 0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266 Details: execution reverted Version: viem@2.47.7 ❯ getTransactionError src/utils/errors/getTransactionError.ts:44:10 ❯ sendTransactionSync src/actions/wallet/sendTransactionSync.ts:407:11 ❯ revokeRoles.inner src/tempo/actions/token.ts:2513:13 ❯ Module.revokeRolesSync src/tempo/actions/token.ts:2622:19 ❯ src/tempo/actions/token.test.ts:1531:5 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { details: 'execution reverted', docsPath: undefined, metaMessages: [ 'Request Arguments:', ' from: 0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266' ], shortMessage: 'Execution reverted for an unknown reason.', version: '2.47.7', walk: 'Function<walk>' } Caused by: ExecutionRevertedError: Execution reverted for an unknown reason. Details: execution reverted Version: viem@2.47.7 ❯ getNodeError src/utils/errors/getNodeError.ts:77:12 ❯ src/utils/errors/getTransactionError.ts:37:19 ❯ getTransactionError src/utils/errors/getTransactionError.ts:43:3 ❯ sendTransactionSync src/actions/wallet/sendTransactionSync.ts:407:11 ❯ revokeRoles.inner src/tempo/actions/token.ts:2513:13 ❯ Module.revokeRolesSync src/tempo/actions/token.ts:2622:19 ❯ src/tempo/actions/token.test.ts:1531:5 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { details: 'execution reverted', docsPath: undefined, metaMessages: undefined, shortMessage: 'Execution reverted for an unknown reason.', version: '2.47.7', walk: 'Function<walk>' } Caused by: TransactionExecutionError: Execution reverted for an unknown reason. Request Arguments: chain: Tempo (id: 1337) from: 0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266 Details: execution reverted Version: viem@2.47.7 ❯ getTransactionError src/utils/errors/getTransactionError.ts:44:10 ❯ fillTransaction src/actions/public/fillTransaction.ts:243:11 ❯ prepareTransactionRequest src/actions/wallet/prepareTransactionRequest.ts:373:7 ❯ sendTransactionSync src/actions/wallet/sendTransactionSync.ts:352:23 ❯ revokeRoles.inner src/tempo/actions/token.ts:2513:13 ❯ Module.revokeRolesSync src/tempo/actions/token.ts:2622:19 ❯ src/tempo/actions/token.test.ts:1531:5 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { details: 'execution reverted', docsPath: undefined, metaMessages: [ 'Request Arguments:', ' chain: Tempo (id: 1337)\n from: 0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266' ], shortMessage: 'Execution reverted for an unknown reason.', version: '2.47.7', walk: 'Function<walk>' } Caused by: ExecutionRevertedError: Execution reverted for an unknown reason. Details: execution reverted Version: viem@2.47.7 ❯ getNodeError src/utils/errors/getNodeError.ts:77:12 ❯ src/utils/errors/getTransactionError.ts:37:19 ❯ getTransactionError src/utils/errors/getTransactionError.ts:43:3 ❯ fillTransaction src/actions/public/fillTransaction.ts:243:11 ❯ prepareTransactionRequest src/actions/wallet/prepareTransactionRequest.ts:373:7 ❯ sendTransactionSync src/actions/wallet/sendTransactionSync.ts:352:23 ❯ revokeRoles.inner src/tempo/actions/token.ts:2513:13 ❯ Module.revokeRolesSync src/tempo/actions/token.ts:2622:19 ❯ src/tempo/actions/token.test.ts:1531:5 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { details: 'execution reverted', docsPath: undefined, metaMessages: undefined, shortMessage: 'Execution reverted for an unknown reason.', version: '2.47.7', walk: 'Function<walk>' } Caused by: RpcRequestError: RPC Request failed. URL: http://localhost:9545/1016 Request body: {"method":"eth_fillTransaction","params":[{"from":"0x8C8d35429F74ec245F8Ef2f4Fd1e551cFF97d650","type":"0x76","calls":[{"to":"0x20c00000000000000000000056854c8609fCf255","value":"0x","data":"0xd547741f114e74f6ea3bd819998f78687bfcb11b1

TransactionExecutionError: Execution reverted for an unknown reason. Request Arguments: from: 0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266 Details: execution reverted Version: viem@2.47.7 ❯ getTransactionError src/utils/errors/getTransactionError.ts:44:10 ❯ sendTransactionSync src/actions/wallet/sendTransactionSync.ts:407:11 ❯ revokeRoles.inner src/tempo/actions/token.ts:2513:13 ❯ Module.revokeRolesSync src/tempo/actions/token.ts:2622:19 ❯ src/tempo/actions/token.test.ts:1531:5 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { details: 'execution reverted', docsPath: undefined, metaMessages: [ 'Request Arguments:', ' from: 0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266' ], shortMessage: 'Execution reverted for an unknown reason.', version: '2.47.7', walk: 'Function<walk>' } Caused by: ExecutionRevertedError: Execution reverted for an unknown reason. Details: execution reverted Version: viem@2.47.7 ❯ getNodeError src/utils/errors/getNodeError.ts:77:12 ❯ src/utils/errors/getTransactionError.ts:37:19 ❯ getTransactionError src/utils/errors/getTransactionError.ts:43:3 ❯ sendTransactionSync src/actions/wallet/sendTransactionSync.ts:407:11 ❯ revokeRoles.inner src/tempo/actions/token.ts:2513:13 ❯ Module.revokeRolesSync src/tempo/actions/token.ts:2622:19 ❯ src/tempo/actions/token.test.ts:1531:5 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { details: 'execution reverted', docsPath: undefined, metaMessages: undefined, shortMessage: 'Execution reverted for an unknown reason.', version: '2.47.7', walk: 'Function<walk>' } Caused by: TransactionExecutionError: Execution reverted for an unknown reason. Request Arguments: chain: Tempo (id: 1337) from: 0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266 Details: execution reverted Version: viem@2.47.7 ❯ getTransactionError src/utils/errors/getTransactionError.ts:44:10 ❯ fillTransaction src/actions/public/fillTransaction.ts:243:11 ❯ prepareTransactionRequest src/actions/wallet/prepareTransactionRequest.ts:373:7 ❯ sendTransactionSync src/actions/wallet/sendTransactionSync.ts:352:23 ❯ revokeRoles.inner src/tempo/actions/token.ts:2513:13 ❯ Module.revokeRolesSync src/tempo/actions/token.ts:2622:19 ❯ src/tempo/actions/token.test.ts:1531:5 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { details: 'execution reverted', docsPath: undefined, metaMessages: [ 'Request Arguments:', ' chain: Tempo (id: 1337)\n from: 0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266' ], shortMessage: 'Execution reverted for an unknown reason.', version: '2.47.7', walk: 'Function<walk>' } Caused by: ExecutionRevertedError: Execution reverted for an unknown reason. Details: execution reverted Version: viem@2.47.7 ❯ getNodeError src/utils/errors/getNodeError.ts:77:12 ❯ src/utils/errors/getTransactionError.ts:37:19 ❯ getTransactionError src/utils/errors/getTransactionError.ts:43:3 ❯ fillTransaction src/actions/public/fillTransaction.ts:243:11 ❯ prepareTransactionRequest src/actions/wallet/prepareTransactionRequest.ts:373:7 ❯ sendTransactionSync src/actions/wallet/sendTransactionSync.ts:352:23 ❯ revokeRoles.inner src/tempo/actions/token.ts:2513:13 ❯ Module.revokeRolesSync src/tempo/actions/token.ts:2622:19 ❯ src/tempo/actions/token.test.ts:1531:5 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { details: 'execution reverted', docsPath: undefined, metaMessages: undefined, shortMessage: 'Execution reverted for an unknown reason.', version: '2.47.7', walk: 'Function<walk>' } Caused by: RpcRequestError: RPC Request failed. URL: http://localhost:9545/1016 Request body: {"method":"eth_fillTransaction","params":[{"from":"0x8C8d35429F74ec245F8Ef2f4Fd1e551cFF97d650","type":"0x76","calls":[{"to":"0x20c00000000000000000000006e1aE2f9cEBAaC1","value":"0x","data":"0xd547741f114e74f6ea3bd819998f78687bfcb11b1

TransactionExecutionError: Execution reverted for an unknown reason. Request Arguments: from: 0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266 Details: execution reverted Version: viem@2.47.7 ❯ getTransactionError src/utils/errors/getTransactionError.ts:44:10 ❯ sendTransactionSync src/actions/wallet/sendTransactionSync.ts:407:11 ❯ revokeRoles.inner src/tempo/actions/token.ts:2513:13 ❯ Module.revokeRolesSync src/tempo/actions/token.ts:2622:19 ❯ src/tempo/actions/token.test.ts:1531:5 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { details: 'execution reverted', docsPath: undefined, metaMessages: [ 'Request Arguments:', ' from: 0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266' ], shortMessage: 'Execution reverted for an unknown reason.', version: '2.47.7', walk: 'Function<walk>' } Caused by: Caused by: ExecutionRevertedError: Execution reverted for an unknown reason. Details: execution reverted Version: viem@2.47.7 ❯ getNodeError src/utils/errors/getNodeError.ts:77:12 ❯ src/utils/errors/getTransactionError.ts:37:19 ❯ getTransactionError src/utils/errors/getTransactionError.ts:43:3 ❯ sendTransactionSync src/actions/wallet/sendTransactionSync.ts:407:11 ❯ revokeRoles.inner src/tempo/actions/token.ts:2513:13 ❯ Module.revokeRolesSync src/tempo/actions/token.ts:2622:19 ❯ src/tempo/actions/token.test.ts:1531:5 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { details: 'execution reverted', docsPath: undefined, metaMessages: undefined, shortMessage: 'Execution reverted for an unknown reason.', version: '2.47.7', walk: 'Function<walk>' } Caused by: Caused by: TransactionExecutionError: Execution reverted for an unknown reason. Request Arguments: chain: Tempo (id: 1337) from: 0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266 Details: execution reverted Version: viem@2.47.7 ❯ getTransactionError src/utils/errors/getTransactionError.ts:44:10 ❯ fillTransaction src/actions/public/fillTransaction.ts:243:11 ❯ prepareTransactionRequest src/actions/wallet/prepareTransactionRequest.ts:373:7 ❯ sendTransactionSync src/actions/wallet/sendTransactionSync.ts:352:23 ❯ revokeRoles.inner src/tempo/actions/token.ts:2513:13 ❯ Module.revokeRolesSync src/tempo/actions/token.ts:2622:19 ❯ src/tempo/actions/token.test.ts:1531:5 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { details: 'execution reverted', docsPath: undefined, metaMessages: [ 'Request Arguments:', ' chain: Tempo (id: 1337)\n from: 0xf39Fd6e51aad88F6F4ce6aB8827279cffFb92266' ], shortMessage: 'Execution reverted for an unknown reason.', version: '2.47.7', walk: 'Function<walk>' } Caused by: Caused by: ExecutionRevertedError: Execution reverted for an unknown reason. Details: execution reverted Version: viem@2.47.7 ❯ getNodeError src/utils/errors/getNodeError.ts:77:12 ❯ src/utils/errors/getTransactionError.ts:37:19 ❯ getTransactionError src/utils/errors/getTransactionError.ts:43:3 ❯ fillTransaction src/actions/public/fillTransaction.ts:243:11 ❯ prepareTransactionRequest src/actions/wallet/prepareTransactionRequest.ts:373:7 ❯ sendTransactionSync src/actions/wallet/sendTransactionSync.ts:352:23 ❯ revokeRoles.inner src/tempo/actions/token.ts:2513:13 ❯ Module.revokeRolesSync src/tempo/actions/token.ts:2622:19 ❯ src/tempo/actions/token.test.ts:1531:5 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { details: 'execution reverted', docsPath: undefined, metaMessages: undefined, shortMessage: 'Execution reverted for an unknown reason.', version: '2.47.7', walk: 'Function<walk>' } Caused by: Caused by: RpcRequestError: RPC Request failed. URL: http://localhost:9545/1016 Request body: {"method":"eth_fillTransaction","params":[{"from":"0x8C8d35429F74ec245F8Ef2f4Fd1e551cFF97d650","type":"0x76","calls":[{"to":"0x20c000000000000000000000F32DF0D475211e02","value":"0x","data":

Canceling since a higher priority waiting request for Pull request-feat/verify-hash-access-key exists

The operation was canceled.

TimeoutError: The request took too long to respond. URL: http://localhost Request body: {"method":"anvil_mine","params":["0x64","0x0"]} Details: The request timed out. Version: viem@x.y.z ❯ Object.request src/utils/rpc/http.ts:134:28 ❯ fn src/clients/transports/http.ts:148:35 ❯ request src/clients/transports/http.ts:153:45 ❯ delay.count.count src/utils/buildRequest.ts:153:28 ❯ attemptRetry src/utils/promise/withRetry.ts:44:28 ❯ retry src/utils/promise/withRetry.ts:40:9 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { details: 'The request timed out.', docsPath: undefined, metaMessages: [ 'URL: http://localhost', 'Request body: {"method":"anvil_mine","params":["0x64","0x0"]}' ], shortMessage: 'The request took too long to respond.', version: '2.47.7', url: 'http://127.0.0.1:8545/884', walk: 'Function<walk>' }

TimeoutError: The request took too long to respond. URL: http://localhost Request body: {"method":"anvil_mine","params":["0x64","0x0"]} Details: The request timed out. Version: viem@x.y.z ❯ Object.request src/utils/rpc/http.ts:134:28 ❯ fn src/clients/transports/http.ts:148:35 ❯ request src/clients/transports/http.ts:153:45 ❯ delay.count.count src/utils/buildRequest.ts:153:28 ❯ attemptRetry src/utils/promise/withRetry.ts:44:28 ❯ retry src/utils/promise/withRetry.ts:40:9 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { details: 'The request timed out.', docsPath: undefined, metaMessages: [ 'URL: http://localhost', 'Request body: {"method":"anvil_mine","params":["0x64","0x0"]}' ], shortMessage: 'The request took too long to respond.', version: '2.47.7', url: 'http://127.0.0.1:8545/884', walk: 'Function<walk>' }

TimeoutError: The request took too long to respond. URL: http://localhost Request body: {"method":"anvil_mine","params":["0x64","0x0"]} Details: The request timed out. Version: viem@x.y.z ❯ Object.request src/utils/rpc/http.ts:134:28 ❯ fn src/clients/transports/http.ts:148:35 ❯ request src/clients/transports/http.ts:153:45 ❯ delay.count.count src/utils/buildRequest.ts:153:28 ❯ attemptRetry src/utils/promise/withRetry.ts:44:28 ❯ retry src/utils/promise/withRetry.ts:40:9 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { details: 'The request timed out.', docsPath: undefined, metaMessages: [ 'URL: http://localhost', 'Request body: {"method":"anvil_mine","params":["0x64","0x0"]}' ], shortMessage: 'The request took too long to respond.', version: '2.47.7', url: 'http://127.0.0.1:8545/884', walk: 'Function<walk>' }

TimeoutError: The request took too long to respond. URL: http://localhost Request body: {"method":"anvil_mine","params":["0x64","0x0"]} Details: The request timed out. Version: viem@x.y.z ❯ Object.request src/utils/rpc/http.ts:134:28 ❯ fn src/clients/transports/http.ts:148:35 ❯ request src/clients/transports/http.ts:153:45 ❯ delay.count.count src/utils/buildRequest.ts:153:28 ❯ attemptRetry src/utils/promise/withRetry.ts:44:28 ❯ retry src/utils/promise/withRetry.ts:40:9 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Serialized Error: { details: 'The request timed out.', docsPath: undefined, metaMessages: [ 'URL: http://localhost', 'Request body: {"method":"anvil_mine","params":["0x64","0x0"]}' ], shortMessage: 'The request took too long to respond.', version: '2.47.7', url: 'http://127.0.0.1:8545/884', walk: 'Function<walk>' }

Canceling since a higher priority waiting request for Pull request-feat/verify-hash-access-key exists

The operation was canceled.

Canceling since a higher priority waiting request for Pull request-feat/verify-hash-access-key exists

Canceling since a higher priority waiting request for Pull request-feat/verify-hash-access-key exists

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, nick-fields/retry@v3, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, nick-fields/retry@v3, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, actions/setup-node@v4, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, actions/setup-node@v4, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, actions/setup-node@v4, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, andresz1/size-limit-action@master, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, codecov/codecov-action@v4, nick-fields/retry@v3, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Codecov: Failed to properly upload report: The process '/home/runner/work/_actions/codecov/codecov-action/v4/dist/codecov' failed with exit code 1

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, codecov/codecov-action@v4, nick-fields/retry@v3, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Codecov: Failed to properly upload report: The process '/home/runner/work/_actions/codecov/codecov-action/v4/dist/codecov' failed with exit code 1

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, nick-fields/retry@v3, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Attempt 1 failed. Reason: Child_process exited with error code 1

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, nick-fields/retry@v3, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/

Attempt 1 failed. Reason: Child_process exited with error code 1

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@49933ea5288caeca8642d1e84afbd3f7d6820020, nick-fields/retry@v3, pnpm/action-setup@a7487c7e89a18df4991f7f222e4898a00d66ddda. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 will be removed from the runner on September 16th, 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/