bcoe / bcoe/conventional-release-labels
Failure with misleading Error: <!DOCTYPE html>...
- Dominant language
- JavaScript
- Stars
- 331
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
Apparently the current code is not resilient to GITHUB API glitches and fails in a very ugly when it encounters them, displaying the HTML body instead of also mentioning the more important stuff like the HTTP return code!
See https://github.com/ansible/tox-ansible/actions/runs/22717526719/job/65870875772?pr=537
I can only guess that this might be the unicorn page, but there is no indication in the entire HTML body about what happened.
Expected behavior would to have some backed-in retry mechanism with exponential backoff logic and also to display the HTTP return code instead of dumping the HTML.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the GitHub API request path implicated by the linked GitHub Actions run and inspect how failed responses are currently surfaced. Use the reported HTML response as the reproduction case; done means failures identify the HTTP return code, avoid dumping an opaque HTML body, and include the requested retry behavior with exponential backoff.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100