The github action failed to post reports
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 57
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Description
From a recent run:
Run title_date=$(date +%Y-%m-%d)
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 69480 100 296 100 69184 736 168k --:--:-- --:--:-- --:--:-- 168k
{
"message": "Validation Failed",
"errors": [
{
"resource": "Issue",
"code": "custom",
"field": "body",
"message": "body is too long (maximum is 65536 characters)"
}
],
"documentation_url": "https://docs.github.com/rest/reference/issues#create-an-issue"
}
100 69480 100 296 100 69184 736 168k --:--:-- --:--:-- --:--:-- 168k
I am guessing that the recent debugger tests fallouts resulted in a super long report that couldn't be posted in one go due to rescritions of GitHub. We probably need to update the action so that it split different parts into replies in that case.
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 from the GitHub Action step that posts the generated report and reproduce the failure with a report containing the recent debugger test fallouts. Trace how the report is sent to GitHub, then verify that oversized reports are split into replies and each posted body stays within GitHub's 65,536-character limit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, shell
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100