Detect github failures
Nobody has claimed this yet.
- Dominant language
- Raku
- Stars
- 19
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
<AlexWithFootgun> quotable6:
/^ ‘bisect: ’ /
<quotable6> AlexWithFootgun, No! It wasn't me! It was the one-armed man! Backtrace: https://gist.github.com/d8844867cb88bf607903dd8566124d2f
<AlexWithFootgun> yay github outage
The exception makes almost no sense to the user (in fact, this error message ideally should never appear). My best guess is that github simply failed to act accordingly (there was a “Minor service outage”), and therefore it failed completely. We should handle this kind of thing.
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 with the linked backtrace and trace the code path that emits the nonsensical exception during a GitHub failure. Reproduce or inspect behavior when GitHub reports an outage, then define the expected user-facing handling and add coverage for that failure.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100