Scenario request: Continue as new with too-frequent signals
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 102
- Forks
- 29
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 22
Description
Describe the scenario you'd like
Run <workflow-count> workflows where each will wait for of signals to be received, for each received signal, run a local-activity that produce a marker. Each workflow would take to finish (maybe control by local-activity). Once of signal is received, drain the signal channel and continue as new.
Separately, there is a client that keeps sending signals to the workflow (can be a long running activity that started by the workflow), and the time between signals has chance shorter than . This will cause workflow to have chance to fail continue_as_new with "unhandled command".
The variables can be set based on good numbers that stress the 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
No file, test, or entry point is named in the issue. Start by locating the load-generator entry point and existing Temporal workflow scenarios, then implement a configurable scenario matching the signal, local-activity, and continue-as-new timing described; done means it can stress the environment and reproduce the reported unhandled-command failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100