Barrier followed by context destruction causes some participants to fail
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.5k
- Forks
- 368
- Avg merge
- 19h 32m
- Merged PRs (30d)
- 3
Description
The shutdown code may be a bit too aggressive here. We should have a stress test for the termination scenario where we loop on (context creation, barrier, context destruction) and verify nobody raises.
May be related to write queues not draining when getting a closure signal from another pair.
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 shutdown code and trace the termination path around context creation, the barrier, and context destruction. Add a stress test that loops through those operations and verifies that no participant raises; use the write-queue closure behavior as a lead when investigating failures.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- distributed-systems, testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100