temporalio / temporalio/features
[Feature Request] SDKs should backoff aggressively on `ResourceExhaustedError`
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 32
- Forks
- 28
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
SDKs currently backoff on retryable errors, some errors e.g. ResourceExhaustedError should backoff more aggressively than others.
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 files, tests, or specific SDKs are named. Start by locating the SDK retry and backoff implementations and their handling of ResourceExhaustedError; define what “more aggressively” means for each affected SDK, then add coverage showing the stronger backoff behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100