haskell-distributed / haskell-distributed/distributed-process
[DP-113] Interrupting "call" and calling it again might produce interference
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 751
- Forks
- 99
- Avg merge
- 45m
- Merged PRs (30d)
- 2
Description
[Imported from JIRA. Reported by Facundo Dominguez @facundominguez) as DP-113 on 2015-06-02 19:11:41]
{{call}} is waiting for some messages that can leak similarly as it happens in DP-112. Another problem it has is that a later call to {{call}} can pickup the result message intended for an earlier interrupted call.
As in DP-112 the most obvious fix seems to be wrapping the {{call}} definition with {{callLocal}}.
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
Locate the definition of call and compare it with callLocal, then read the related DP-112 issue for context on message leakage. Verify how an interrupted call handles waiting messages and how a later call receives result messages. Done means interrupted calls do not leak or interfere with subsequent calls.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100