Skip to content

fix(pack): fetch a GitHub release asset with curl when tinyhttps cannot read GitHub's long header line - #70

Merged
Sunrisepeak merged 2 commits into
mainfrom
fix/0.0.17-long-header-lines
Oct 23, 2026
Merged

Sunrisepeak merged 2 commits into
mainfrom
fix/0.0.17-long-header-lines

Conversation

@Sunrisepeak

Copy link
Copy Markdown
Owner

The 0.0.17 Release run (40022574908) failed in every payload job: GitHub's 302 for a release download now carries a 9243-byte content-security-policy header line, and tinyhttps 0.3 (packaging only; the server does not use it) gives up on header lines over 8192 bytes (Incomplete headers: line exceeds 8192 bytes without a CRLF). PR CI never downloaded: its payload cache had the archives.

On that one error, pack::fetch downloads the file with curl (on every runner) and verifies it against the lock exactly as before (sha256, size). Reproduced locally with an empty cache: the fallback fetched clangd-23.1.0-mcppls.5-linux-x64.tar.gz and the part assembled. The real fix belongs in tinyhttps (a longer line limit); remove this when it has one.

🤖 Generated with Claude Code

…etched with curl

GitHub's redirect for a release asset now carries a 9.2 KB content-security-policy line; tinyhttps 0.3 gives up on
header lines over 8 KB, so every payload job of the 0.0.17 Release run failed to fetch the engine. On that error the
file is downloaded with curl and verified against the lock as before.
@Sunrisepeak
Sunrisepeak merged commit 2b8cf98 into main Oct 23, 2026
46 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant