Improve error reporting for fatal errors like `Bad Credentials`
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.3k
- Forks
- 1.4k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 24
Description
Describe the enhancement
When the runner receives a 401 (or something else) that it deems to be fatal, it should provide enough http response information that someone could do something with it (like file a ticket to https://support.github.com).
Roughly, that's the response code (and http version), server, date, x-github-*, and x-ratelimit-* fields plus the response body.
Code Snippet
Additional information
See #769 and https://github.com/github/feedback/discussions/14439
Contributor guide
No contributing guide indexed for this repository
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 in the runner application’s handling of fatal HTTP responses, especially 401 cases, and review #769 and discussion 14439 for context. Trace where the response is classified as fatal, then verify that the resulting error reports the response code and HTTP version, relevant headers, and response body.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100