Skip to content

Pass catalog arrays to jq as files, not arguments - #272

Merged
ArtemSirobaba merged 1 commit into
mainfrom
fix/release-manifest-arg-limit
Aug 5, 2026
Merged

ArtemSirobaba merged 1 commit into
mainfrom
fix/release-manifest-arg-limit

Conversation

@neo-sky

@neo-sky neo-sky commented Aug 5, 2026

Copy link
Copy Markdown
Collaborator

The release workflow has failed on every push to main since the catalog reached 28 tools carrying both schema and prompt artifacts:

./scripts/generate-manifest.sh: line 204: /usr/bin/jq: Argument list too long

No release has been cut since, so the catalog is frozen at release-2026-08-05-105 and #271's prompt-doc artifacts cannot reach the signed catalog.

The cause is MAX_ARG_STRLEN, the 128KB cap on a single argv entry, not ARG_MAX. ARG_MAX is 2MB on the runner and the whole catalog is ~173KB, which is why the error reads as impossible until you notice the limit applies per argument. The tools array crossed it once tools started carrying schemas and prompts together.

Both arrays now reach jq as files via --slurpfile instead of --argjson. Temp files go to mktemp -d with a trap, deliberately not $STAGING, whose contents are uploaded as release assets.

Verified by reproducing the failure directly: a 150010-byte single argument fails with the same error under --argjson and succeeds under --slurpfile. Every other --argjson in the script is a number, a single artifact, or bounded by an existing cap (32 schemas, 64 prompts, 256 bundle files), so the final aggregate was the only unbounded one.

@vercel

vercel Bot commented Aug 5, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
ironhub-web Error Error Aug 5, 2026 2:52pm

Request Review

@ArtemSirobaba
ArtemSirobaba merged commit daa4707 into main Aug 5, 2026
30 of 35 checks passed

This branch was previously deployed

1 inactive deployment
Preview — b8fe81ef Deployed Aug 5, 2026 by vercel[bot]
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.

2 participants