temporalio / temporalio/temporal
Support reset to any point with pending ChildWorkflows
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Mirror Cadence feature request(with proposal): https://github.com/uber/cadence/issues/3914
cc @yux0 @yycptt @meiliang86 LMK if you have any plan to implement this feature :D
This becomes problematic because people want to use ChildWorkflow naturally. today, a workflow with childWorkflow can be not resettable which will be hard to recover from outage.
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
Read the linked Cadence proposal at github.com/uber/cadence/issues/3914 first, then trace Temporal's reset handling for workflows with pending ChildWorkflows. The issue names no files, tests, or entry points, so the implementation scope and completion criteria need to be established before work begins.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100