temporalio / temporalio/sdk-java
Test server timeouts improperly set to 10 years when not user set
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 433
- Forks
- 249
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 26
Description
Expected Behavior
Current server doesn't set WorkflowExecutionStartedEventAttributes.workflow_execution_timeout or PollActivityTaskQueueResponse.schedule_to_close_timeout if the user didn't
Actual Behavior
Test server sets these to 10 years when not set. While this may make sense internally to bound the timer, e.g. the API for https://www.javadoc.io/static/io.temporal/temporal-sdk/1.16.0/io/temporal/activity/ActivityInfo.html#getScheduleToCloseTimeout() should be accurate.
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 tracing the test server's handling of WorkflowExecutionStartedEventAttributes.workflow_execution_timeout and PollActivityTaskQueueResponse.schedule_to_close_timeout. Verify the behavior when the user leaves each timeout unset, then confirm the exposed ActivityInfo API reports the unset value rather than a ten-year default.
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