temporalio / temporalio/features
Waiting on update result should auto-skip time in time-skipping environments
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 32
- Forks
- 28
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
Describe the solution you'd like
Today in time-skipping environments, we auto-skip time when waiting on workflow results. We should do the same when waiting on update results.
Per-SDK Tickets
- Go - N/A (no time-skipping environment)
- Java - https://github.com/temporalio/sdk-java/issues/2283
- Core - N/A (no time-skipping environment)
- TypeScript - https://github.com/temporalio/sdk-typescript/issues/1549
- Python - https://github.com/temporalio/sdk-python/issues/675
- .NET - https://github.com/temporalio/sdk-dotnet/issues/360
- Ruby - N/A (workflows not built yet)
- PHP - N/A (no time-skipping environment)
- Temporal CLI - (no time-skipping environment)
Contributor guide
No contributing guide indexed for this repository
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 the linked Java, TypeScript, Python, and .NET SDK tickets, then compare each SDK's existing time-skipping behavior while waiting for workflow results. Add equivalent coverage for update-result waits in the applicable SDK repositories; done means those waits auto-skip time consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, java, python, typescript
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100