Establish pattern for proper go routing handling/tooling
Open
kind/bug
need/triage
- Dominant language
- Go
- Stars
- 17.1k
- Forks
- 3.2k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 11
Description
## Done criteria
We have a reference example in go-ipfs or one of its dependencies that demonstrates the best practice and/or tooling for proper go routine handling so that an error in a library doesn't cause a panic for go-ipfs.
## Context:
https://discord.com/channels/899652135552167957/953032389775482880
https://filecoinproject.slack.com/archives/C0365HH2F55
https://docs.google.com/document/d/1qFBN5kP1_MW8-hMOpoqg3IPCUb2Tu5WL11LW5cc6fWo/edit#
go-libp2p did various changes for resiliency here as well in https://github.com/libp2p/go-libp2p/issues/1389
Contributor guide
Assessment
This issue has not been assessed yet.