Repository navigation
Creating a release with files sometimes fails upoading the files and tanks the release #6651
Description
Activity
- addedpriority-3Affects a small number of users or is largely cosmeticAffects a small number of users or is largely cosmeticand removedneeds-triageneeds to be reviewedneeds to be reviewed
on Nov 23, 2022 Fixed in 7caf7da
@mislav Another example of error/failure of
gh release create:Post "https://uploads.github.com/repos/busytex/busytex/releases/87511879/assets?label=&name=fonts.conf": unexpected EOF@vadimkantorov This happened even with the latest release?
Unlikely. I'm using apk for alpine:
runs-on: ubuntu-20.04 container: alpine:3.17 steps: - name: Install Prerequisites run: apk add --update --no-cache libnsl libnsl-dev build-base coreutils cmake git xz wget perl gperf p7zip python3 strace && ln -sf python3 /usr/bin/python - name: Install Hub run: apk add --no-cache -X http://dl-cdn.alpinelinux.org/alpine/v3.17/testing github-cli
and
ghavailable by default on ubuntu-20.04 properAnother error (coming from default
ghon ubuntu-20.04:HTTP 400: Bad Content-Length: (https://uploads.github.com/repos/busytex/busytex/releases/87606152/assets?label=&name=ubuntu-texlive-base.data)I can try using the latest release. Does it exist as static binary that I can just wget on my alpine and ubuntu GH Actions jobs?
For
Bad Content-Length, it could be trying to add an empty asset to the release, but it's strange to fail like so@vadimkantorov You can download and untar a precompiled binary for any GitHub CLI release, e.g. https://github.com/cli/cli/releases/tag/v2.21.2
I think that our Linux binaries should work on Alpine: #2556.
I think that our Linux binaries should work on Alpine: #2556.
I will check, but it would be better if there was a simple binary as an asset - that would save decompression. Probably it's quite small anyway. And it would also be better if file names / release notes were clear if the binaries is built fully statically (including musl libc) and are alpine/anylinux compatible or not.

Describe the bug
Sometimes when using
gh release create <files>..., uploading files fails (and ends up with a partial release).Steps to reproduce the behavior
Expected vs actual behavior
As proposed by @mislav on #6645 , the retry mechanism for file uploads could be more robust to handle these failures as well.
Originally posted by @mislav in #6645 (comment)
Logs
Examples of failures from our CI [1]:
[1] https://github.com/submariner-io/releases/actions/runs/3491034412/jobs/5843200596#step:4:536