Tags: temporalio/temporal
Tags
stop infinite activity retries in the entity workflows (#7448) ## What changed? <!-- Describe what has changed in this PR --> - Right now, entity workflows related to versioning have infinite number of retries happening. In the case of an unforeseen error, this might leave our internal entity workflows locked and might require manual intervention. - The activity context, being used in all of the activities related to the worker-deployment workflows, now has a maximum number of attempts set to 5. This shall ensure that on the eve of an unforeseen error, the deployment workflow will unlock itself after a maximum time of ~5 mins. [ ~5 mins calculated by doing math involving backoff coefficient, initial interval and maximum attempts ] ## Why? <!-- Tell your future self why have you made these changes --> - To not lock our own workflows. ## How did you test it? <!-- How have you verified this change? Tested locally? Added a unit test? Checked in staging env? --> - Current Suite of tests to verify nothing is broken. ## Potential risks <!-- Assuming the worst case, what can be broken when deploying this change to production? --> ## Documentation <!-- Have you made sure this change doesn't falsify anything currently stated in `docs/`? If significant new behavior is added, have you described that in `docs/`? --> ## Is hotfix candidate? <!-- Is this PR a hotfix candidate or does it require a notification to be sent to the broader community? (Yes/No) -->
Functional test improvements (#7435) ## What changed? - Versioning 3 tests: make tests individually time out on failure instead of blocking forever - DescribeTaskQueue tests: use `require` in `EventuallyWithT` to avoid panics ## Why? make it more clear when/how tests fail
PreviousNext