libp2p / libp2p/go-libp2p-pubsub
Peer declared dead, respawning writer.
Open
Nobody has claimed this yet.
kind/bug
- Dominant language
- Go
- Stars
- 364
- Forks
- 221
- PR merge metrics
- No merged PRs in 30d
Description
I just saw hundreds (thousdands?) of "peer declared dead but still connected; respawning writer: ..." messages. It looks like we need some form of backoff/delay.
Contributor guide
No contributing guide indexed for this repository
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
No file or test is identified. Search the repository for the exact "peer declared dead but still connected" log message, trace the writer-respawn path, and reproduce the repeated logging if possible; done means the failure is understood and repeated respawns are controlled without losing valid peer connections.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100