haskell-distributed / haskell-distributed/distributed-process
Can we report when the NC or incoming event handler crashes or blocks?
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 751
- Forks
- 99
- Avg merge
- 45m
- Merged PRs (30d)
- 2
Description
When the NC thread or handleIncomingEvents crash, the application will probably block without further hints. It would be better if we printed some message in the console to report the problem. This won't help much, though, if the NC simply blocks not really terminating with an exception.
Another related aspect to consider is whether the NC really needs to die if there is an error handling any of the messages.
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 by locating the NC thread and handleIncomingEvents entry points named in the issue, then trace how crashes, blocking, and message-handling errors are currently handled. Done means the relevant failure or blocking behavior produces a useful console diagnostic and the termination behavior is explicitly settled.
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
- 25/100