Failure in rolling build "Init stage 0 Go toolset": "curl: (18) transfer closed with X bytes remaining to read"
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 431
- Forks
- 44
- Avg merge
- 21h 18m
- Merged PRs (30d)
- 30
Description
...
97 123M 97 120M 0 0 36.5M 0 0:00:03 0:00:03 --:--:-- 44.1M
curl: (18) transfer closed with 2912825 bytes remaining to read
...
Filing this issue to keep track in case it ends up happening often.
A long-term fix is to pre-install Go into a build prereqs Dockerfile: #5.
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 with the linked Azure build log and review issue #5, which is identified as the long-term fix. Then inspect the build prereqs Dockerfile referenced by the issue and determine how the rolling build's Init stage 0 Go toolset is handled. Done should address the tracked transfer failure or establish whether it recurs often enough to require that fix.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dockerfile, go
- Domain
- build-system, ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100