microsoft / microsoft/durabletask-python
Composite tasks do not notify parent composites
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 40
- Forks
- 33
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 6
Description
WhenAllTask and WhenAnyTask mark themselves complete, but do not notify their parent composite.
This means the following orchestration does not resume when all activities complete:
all_task = task.when_all(activity_tasks)
winner = yield task.when_any([cancel_task, all_task])
A current workaround is to wait for each leaf task with repeated when_any calls. The workaround preserves cancellation, but Durable Task Scheduler no longer shows the standard Fan-out group.
Could composite completion propagate to the parent in the same way that CompletableTask.complete() does?
A regression test can compose when_any([cancel, when_all([a, b])]), complete a and b, and verify that the outer task completes with the inner when_all task.
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 WhenAllTask and WhenAnyTask, then compare their completion behavior with CompletableTask.complete(). Add the regression test described in the issue for when_any([cancel, when_all([a, b])]); done means completing a and b causes the outer task to complete with the inner when_all task.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 72/100