temporalio / temporalio/features
Show retry policy on activity info
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 32
- Forks
- 28
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
Describe the solution you'd like
Retry policy is available via proto (and core) on activity tasks, need to make it available for activities the same way it is available for workflows. Note, retry policy can be updated for an activity in some upcoming features, but it only applies to successive tasks not the current.
Per-SDK Tickets
- Go - https://github.com/temporalio/sdk-go/issues/1919
- Java - https://github.com/temporalio/sdk-java/issues/2481
- Core - Done
- TypeScript - https://github.com/temporalio/sdk-typescript/issues/1680
- Python - https://github.com/temporalio/sdk-python/issues/831
- .NET - https://github.com/temporalio/sdk-dotnet/issues/457
- Ruby - https://github.com/temporalio/sdk-ruby/issues/248
- PHP - https://github.com/temporalio/sdk-php/issues/602
- Temporal CLI - N/A
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 proto and core support mentioned in the issue, then review the per-SDK tickets for Go, TypeScript, Python, .NET, Ruby, and PHP; Java and Core are marked done. Done means activity information exposes the retry policy consistently with workflow information, while preserving the note that updates apply only to successive tasks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, java, php, python, ruby, typescript
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100