libp2p / libp2p/universal-connectivity
Files break the go-peer
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 167
- Forks
- 75
- PR merge metrics
- No merged PRs in 30d
Description
So presently if you send a binary file of 5 or 10MB into chat from the js-peer and a go-peer is listening it will panic and crash. Even though it seems to restart it goes deaf and won't receive other messages nor send them in the chat interface.
I also ran a headless go-peer and received the same sort of behavior. It just seems to go completely deaf, even though everything looks normal it won't accept connections any more and needs a manual restart.
Sorry I don't have more details. I had a 10 peer mesh up and it brought the whole thing down with a single file. Once I get things straightened out I'll try on a 2-node setup now I know what to look for and see what I can deduce.
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
Start by reproducing the failure with a 5–10MB binary sent from the js-peer to a go-peer, then compare the mesh and headless go-peer behavior described in the issue. Done means the go-peer does not panic or become deaf, and continues accepting connections and exchanging chat messages after receiving the file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, typescript
- 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