temporalio / temporalio/sdk-java

Test service continue-as-new implementation is not atomic

Open
#1,538 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug test server
Dominant language
Java
Stars
433
Forks
249
Avg merge
5d 6h
Merged PRs (30d)
26

Description

Expected Behavior

No signal is rejected when sent to a workflow that calls continue as new.

Actual Behavior

Signal sender can receive NOT_FOUND if it is sent while target workflow is executing continue-as-new.

Steps to Reproduce the Problem

See https://github.com/temporalio/sdk-java/pull/1537 for reproduction.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the reproduction described in pull request 1537, then trace how signals are handled while a workflow executes continue-as-new. Confirm the NOT_FOUND path and add a regression test showing that a signal sent during the transition is accepted rather than rejected.

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
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.