Create a retry policy for Hackbot actions to mitigate transient 500 errors
Open
Nobody has claimed this yet.
hackbot
- Dominant language
- Python
- Stars
- 570
- Forks
- 351
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 65
Description
Add automatic retry with backoff at the action-execution layer for transient upstream 5xx errors (Bugzilla, Phabricator, Slack, etc). This is distinct from the existing manual "Retry failed actions" button in the UI, which requires a human to notice the failure and click retry.
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 at the action-execution layer and compare its handling of upstream failures with the existing manual "Retry failed actions" flow in the UI. Trace the Bugzilla, Phabricator, and Slack actions, then verify that transient 5xx failures retry with backoff while non-transient failures do not.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100