temporalio / temporalio/temporal
Add ScheduleToStart timeout to WorkflowTaskScheduledEvent
Open
Nobody has claimed this yet.
API
devexp
difficulty: easy
good first issue
up-for-grabs
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
See image above, which indicates "10" seconds, however the server is hardcoded to 5 seconds and the task actually does timeout in 5 seconds, which can be confusing to the user:
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 WorkflowTaskScheduledEvent handling and the server path where the ScheduleToStart timeout is hardcoded to 5 seconds. Compare that behavior with the 10-second value shown in the issue; done means the event and server behavior report and enforce a consistent timeout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100