haskell-distributed / haskell-distributed/distributed-process
Handle interrupted messages gracefully
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 751
- Forks
- 99
- Avg merge
- 45m
- Merged PRs (30d)
- 2
Description
It seem interrupting send calls of the TCP transport can sometimes produce the receiver side to append incomplete messages with unrelated messages and deliver that to upper layers.
Either interrupted messages should become impossible, or the receiver should be stopped from delivering these messages upwards.
See the discussion in https://github.com/haskell-distributed/network-transport-tcp/commit/9ec9c1af4143bb4de952c6678ac46afe782cf740#r33404578
cc @andriytk
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 reading the linked TCP transport commit discussion, then trace the transport's interrupted send calls and receiver message-delivery path. Reproduce or characterize how an interrupted message becomes combined with another message; done means incomplete messages are either prevented or no longer delivered to upper layers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- distributed-systems, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100