capsule.dot v2 change 4 (held): fan `void` out beside `mutate`/`mutate_b` needs filesystem isolation for parallel makers
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start with docs/designs/REVIEW-pipelines-2026-09.md, especially §§3.3 and 4 change 4, and review the Q1 constraint described here. Compare the proposed worktree, copy-on-write scratch directory, and merge-step approaches. Done means a design is selected and a test demonstrates that two concurrent makers cannot clobber each other.
Written by the indexing model from the issue text.
Description
From the pipeline review (docs/designs/REVIEW-pipelines-2026-09.md §3.3 / §4 change 4, merged via #71). The only structural clock saving found (~90 → ~72 min/round) is running void in parallel with the mutate pair. Blocked on Q1: the three makers write into the same working tree; parallel execution needs per-branch isolation (worktree per branch, or a copy-on-write scratch dir, or a merge step) before the fan-out is safe. This issue tracks the isolation design; do not apply change 4 until it is answered with a design + a test that two concurrent makers cannot clobber each other.
- Dominant language
- Python
- Stars
- 2
- Forks
- 2
- Avg merge
- 7h 42m
- Merged PRs (30d)
- 3
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing 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.
More from microsoft/amplifier-bundle-dot-runner
-
ready:spec
Difficulty 3/5 1-2 days Newbie friendliness 74/100
microsoft/amplifier-bundle-dot-runner#85 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
microsoft/amplifier-bundle-dot-runner#61 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
microsoft/amplifier-bundle-dot-runner#60 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
microsoft/amplifier-bundle-dot-runner#35 ·
Maintainers usually reply within 1 day
All issues in microsoft/amplifier-bundle-dot-runner
Similar issues
-
intake mcp-intake needs-ac needs-human-review priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Ikalus1988/MisakaNet#3848 · 2 comments ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 75/100
521xueweihan/HelloGitHub#4105 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
igormcsouza/bookloud#54 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
aws-samples/sample-per-model-bedrock#526 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ok-oldking/ok-wuthering-waves#1802 ·
Maintainers usually reply within 2 days