lambdaclass / lambdaclass/lambda_ethereum_consensus
Long running errors ending up in peer failures
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 109
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
During the last weeks we've been still running the node sparingly in our servers, from those runs we encountered a couple of issues, mostly known ones, others need to be further investigated. Most of them end up with errors in the peerbook after failing attempts to connect. We need to look at the errors, create issues for those that are new and in the future tackle the issues with our naive implementation of the peerbook as well as take a close look to the DB errors while pruning and the libp2p resume of the initial store
Contributor 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 by reviewing the peerbook errors from the recent node runs and the linked issues about DB errors while pruning (#1326) and resuming the initial libp2p store (#1328). Done means identifying which failures are new, creating issues for them, and scoping follow-up work for the peerbook and related errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- databases, distributed-systems, networking
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100