lambdaclass / lambdaclass/lambda_ethereum_consensus
[Networking] Handle "no-peers" state
Open
Nobody has claimed this yet.
needs elaboration
- Dominant language
- Elixir
- Stars
- 109
- Forks
- 41
- PR merge metrics
- No merged PRs in 30d
Description
Created from: https://github.com/lambdaclass/lambda_ethereum_consensus/pull/225#discussion_r1337571028
Currently, the Peerbook just waits for a second and retries, but maybe there's a better way to handle this.
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 at the Peerbook handling for the "no-peers" state and trace the current one-second retry behavior. Determine what alternative handling is appropriate, then verify that the Peerbook no longer waits and retries incorrectly when no peers are available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100