Open
Description
This is not impacting the execution of assertoor tests right now, probably just a missing endpoint that autoresolves through other nodes, but still something to have a look in the future:
[assertoor] time="2025-01-31T20:26:51Z" level=info msg="received cl block 19 [0x69f9b64d2c50e2e251e8ed3f9628d8bd1e2e42dc96bf1cc8158e0b285b675b10] streamed" client=3-geth-lambda module=consensus
[assertoor] time="2025-01-31T20:26:51Z" level=warning msg="failed processing block event: could not process block: GET failed with status 404: {\"code\":404,\"message\":\"Resource not found\"}" client=3-geth-lambda module=consensus```
These errors appear during assertoor run in the block_proposal check, here is an example: https://github.com/lambdaclass/lambda_ethereum_consensus/actions/runs/13080097954/job/36501495170?pr=1324
Metadata
Metadata
Assignees
Type
Projects
Status
No status