temporalio / temporalio/sdk-java
Child workflow cancellation can trigger SDK event loop without a WFT Started
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 433
- Forks
- 249
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 26
Description
Expected Behavior
Child workflow cancellation would not trigger the event loop without a WFT Started
Actual Behavior
Child workflow cancellation can trigger SDK event loop without a WFT Started
Steps to Reproduce the Problem
see: https://github.com/temporalio/sdk-java/issues/2155
Fixing this would be a non deterministic change so we will need to version this change.
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 temporal-sdk/src/main/java/io/temporal/internal/statemachines/WorkflowStateMachines.java around line 884 and review the related reproduction in sdk-java issue 2155. Trace child-workflow cancellation and the event-loop behavior, then determine how the versioning requirement affects the fix. Done means cancellation no longer triggers the SDK event loop without a WFT Started while preserving the required versioning behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100