haskell-distributed / haskell-distributed/distributed-process
DiedDisconnect due to IPv6 localhost resolution
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 751
- Forks
- 99
- Avg merge
- 45m
- Merged PRs (30d)
- 2
Description
Summary
Minimal example fails when nodes are using IPv6 localhost addresses.
Context
I tried the minimal example at https://hackage.haskell.org/package/distributed-process-simplelocalnet-0.2.4/docs/Control-Distributed-Process-Backend-SimpleLocalnet.html
It works fine on my Windows computer using WSL2 (Windows subsystem for Linux).
But on Linux (Fedora 36), it fails with DiedDisconnect.
Eventually I realised on Linux the nodes are assigned IPv6 localhost addresses (::1).
temporary fix
Disable IPv6 on Linux:
https://www.techrepublic.com/article/how-to-disable-ipv6-on-linux/
extra reference
past me discovered that Linux would bind localhost as IPv6 only
https://www.reddit.com/r/haskell/comments/6emo9g/comment/did1j1m/
request
Perhaps note this down under the troubleshooting section in the doc at https://hackage.haskell.org/package/distributed-process-simplelocalnet-0.2.4/docs/Control-Distributed-Process-Backend-SimpleLocalnet.html .
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 with the Control.Distributed.Process.Backend.SimpleLocalnet documentation and its troubleshooting section, then reproduce or review the minimal example described in the issue. Document that Linux systems resolving localhost to IPv6 (::1) can cause DiedDisconnect, including the relevant environment context and workaround. Done means the troubleshooting guidance is present in the source that generates the linked Hackage page.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- distributed-systems, documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100