jcoffey-dev is traveling from Thursday 1 October through Sunday 4 October. Issues and pull requests are welcome, and will get an answer after that. Thanks for your patience.
The v2026.9.30.1 binaries job lost a 50 MB upload to Gitea on each of its two runs: curl 92 (HTTP/2 PROTOCOL_ERROR), and host1 nginx logged 400 with no body. It was arm64 the first time and amd64 the second. The uploads cross Cloudflare; Gitea-built releases never did. A failed run also left the release missing the file it had just deleted.
Uploads now use HTTP/1.1, and every API call in the step retries (5 tries, 15 s apart).
This only runs on a tag, so the next release tests it. 2026.9.30.1s files were attached by hand from host1 over localhost, reproducing this jobs steps.
No new strings.
The v2026.9.30.1 binaries job lost a 50 MB upload to Gitea on each of its two runs: curl 92 (HTTP/2 PROTOCOL_ERROR), and host1 nginx logged 400 with no body. It was arm64 the first time and amd64 the second. The uploads cross Cloudflare; Gitea-built releases never did. A failed run also left the release missing the file it had just deleted.
Uploads now use HTTP/1.1, and every API call in the step retries (5 tries, 15 s apart).
This only runs on a tag, so the next release tests it. 2026.9.30.1s files were attached by hand from host1 over localhost, reproducing this jobs steps.
No new strings.
The v2026.9.30.1 binaries job lost a 50 MB upload to Gitea's release
API on each of its two runs (curl 92, HTTP/2 PROTOCOL_ERROR; the origin
logged 400 with no body), arm64 the first time and amd64 the second.
The uploads cross Cloudflare. A failed run also left the release short
of the file it had just deleted.
Uploads now go over HTTP/1.1, and every API call retries 5 times.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The v2026.9.30.1 binaries job lost a 50 MB upload to Gitea on each of its two runs: curl 92 (HTTP/2 PROTOCOL_ERROR), and host1 nginx logged 400 with no body. It was arm64 the first time and amd64 the second. The uploads cross Cloudflare; Gitea-built releases never did. A failed run also left the release missing the file it had just deleted.
Uploads now use HTTP/1.1, and every API call in the step retries (5 tries, 15 s apart).
This only runs on a tag, so the next release tests it. 2026.9.30.1s files were attached by hand from host1 over localhost, reproducing this jobs steps.
No new strings.