haskell-distributed / haskell-distributed/distributed-process
Should Node Controller and Network Listener be linked?
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 751
- Forks
- 99
- Avg merge
- 45m
- Merged PRs (30d)
- 2
Description
If the forkIO thread running handleIncomingMessages terminates, nothing happens to the thread in runNodeController. Isn't this wrong? The node is now cut off from the outside world and there's no means to start handleIncomingMessages - or is there some magic in the Network.Transport layer that handles this? I can't see anything obvious.
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
Trace the forkIO thread running handleIncomingMessages alongside runNodeController, then inspect how Network.Transport reports listener termination. Determine whether the two lifecycles are expected to be linked and identify the failure behavior that should be covered. Done means the issue has a clear lifecycle decision and corresponding handling or documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100