lambdaclass / lambdaclass/lambda_ethereum_consensus
Assertoor error msgs during execution
Open
Nobody has claimed this yet.
P2
- Dominant language
- Elixir
- Stars
- 109
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
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=1324Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Assertoor block_proposal check and the linked workflow run; trace the 404 during block-event processing. Determine which endpoint or resource is missing and verify that the warning no longer appears during the check without affecting execution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100