temporalio / temporalio/sdk-java

Memo-s not present in listOpenWorkflowExecutions when running with temporal-testing

Open
#2,480 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Expected Behavior

I'm using temporal-testing and when I query running workflows:

        List<WorkflowExecutionInfo> executions = client.getWorkflowServiceStubs()
                .blockingStub()
                .listOpenWorkflowExecutions(
                        ListOpenWorkflowExecutionsRequest.newBuilder()
                                .setNamespace("default")
                                .build()
                )
                .getExecutionsList();

        executions.forEach(execution -> {
            System.err.println(execution.getExecution().getWorkflowId());
            System.err.println(execution.getMemo());
        });

memo is empty despite being filled in workflow.

Actual Behavior

The same piece of code run with setUseExternalService(true) and temporal server start-dev running outputs memo-s as expected.

Steps to Reproduce the Problem

I prepared reproducer project: https://github.com/rpost/temporal-test-memo/blob/main/src/test/java/rpost/MemoTest.java

Specifications

  • Version: io.temporal:temporal-testing:1.28.4

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 reproducer in src/test/java/rpost/MemoTest.java and compare its temporal-testing path with the external-service path. Trace how listOpenWorkflowExecutions supplies WorkflowExecutionInfo memo data in the testing environment. Done means the reproducer returns the workflow memo when using temporal-testing, with the behavior verified by a regression test.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend, testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.