Create a retry policy for Hackbot actions to mitigate transient 500 errors

Open
#6,622 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
backend, devtools

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.

Description

hackbot

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.

Dominant language
Python
Stars
570
Forks
351
Avg merge
2d 11h
Merged PRs (30d)
61

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from mozilla/bugbug

All issues in mozilla/bugbug

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.