Skip to content

fix(sandbox): support large run-code payloads - #172

Merged
iamjr15 merged 1 commit into
mainfrom
fix/research-pdf-run-code
Aug 5, 2026
Merged

fix(sandbox): support large run-code payloads#172
iamjr15 merged 1 commit into
mainfrom
fix/research-pdf-run-code

Conversation

@iamjr15

@iamjr15 iamjr15 commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

Why

Rich Markdown PDF generation builds a renderer script larger than the public exec argv-element limit. ProjectSandbox.runCode reused that exec path, so the validated 8,790-character renderer failed before execution with an 8,192-character Zod limit.

What changed

  • keep public exec argv limits unchanged
  • transport validated run-code source as bounded base64 request-environment chunks
  • pipe source to Node or Python over stdin, preserving top-level module behavior
  • execute inside the existing runCode lease without writing source onto the persistent workspace volume
  • document the separate runCode and exec transport contracts

Verification

  • pnpm lint
  • pnpm typecheck
  • pnpm turbo build --force
  • pnpm deadcode
  • pnpm architecture:check
  • pnpm turbo skills:build
  • confirmed the production renderer script is 8,790 characters and the prior production error identifies command element 3 exceeding 8,192 characters

Production research and PDF acceptance will be rerun after deployment.

@vercel

vercel Bot commented Aug 5, 2026

Copy link
Copy Markdown

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

1 Skipped Deployment
Project Deployment Actions Updated (UTC)
cheatcode Skipped Skipped Aug 5, 2026 9:49am

@iamjr15
iamjr15 merged commit 4d6f818 into main Aug 5, 2026
6 checks passed
@iamjr15
iamjr15 deleted the fix/research-pdf-run-code branch August 5, 2026 09:51
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