retry certian failed activations in case of system error
Open
enhancement
invoker
RAS
- Dominant language
- Scala
- Stars
- 6.8k
- Forks
- 1.2k
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 2
Description
some system errors - like a failure to start a container - are safe to retry since we know no observable side effects could have occurred. we should consider doing this by re-queuing the activation request.
Contributor guide
Research direction
Start by tracing how an activation request handles system errors, especially failures to start a container, and where the request could be re-queued. Done means the project has a defined and tested retry behavior for errors with no observable side effects.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, scala
- Domain
- backend, cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100