celestiaorg / celestiaorg/go-header
p2p: PeerTracker getPeers should sort peers by score
Open
- Dominant language
- Go
- Stars
- 21
- Forks
- 33
- Avg merge
- 5d 20h
- Merged PRs (30d)
- 7
Description
Considering that we take the first 4 for the request, we should sort them by the score and ensure the first 4 are the best ones
_Originally posted by @Wondertan in https://github.com/celestiaorg/go-header/pull/53#discussion_r1281689753_
Contributor guide
Research direction
Start at the PeerTracker getPeers entry point and inspect how peers are selected for a request. Ensure the first four selected peers are the highest-scoring ones, then verify the behavior with the relevant existing tests or test coverage for PeerTracker.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100