fix(cli): cloud render sends one zip when it fits and uploads only the largest media (#7859)

* fix(cli): cloud render sends one zip when it fits and uploads only the largest media

* fix(cli): cloud render leaves unused media out only when the zip is over the limit

* test(cli): eight-at-once upload test waits for eight in flight, never a timer

* test(cli): eight-at-once upload test also fails when more than eight run
This commit is contained in:
Miguel Ángel
2026-11-15 21:19:22 +00:00
committed by GitHub
parent 52d43f33a3
commit 9bc2b231d3
8 changed files with 318 additions and 44 deletions
+1 -1
View File
@@ -59,7 +59,7 @@ hyperframes cloud render --resolution 4k
## Check what will upload
Media files of 5 MB or more that the project names by path upload as HeyGen assets and are referenced by public, unsigned URL, so large footage and audio do not count against the 200 MB project archive limit. Uploads are cached, so re-rendering uploads only new or changed media. Media is streamed from disk as it uploads, so a large file never has to fit in memory; editing one while the command is preparing it stops the run. Inspect what will upload before starting a render:
When the project fits under the 200 MB project archive limit, it is sent as one zip. When it does not, media no page, script or variable names is left out first, then the largest media files the project names by path upload as HeyGen assets, eight at a time, just enough for the rest to fit, and are referenced by public, unsigned URL. Uploads are cached, so re-rendering uploads only new or changed media. Media is streamed from disk as it uploads, so a large file never has to fit in memory; editing one while the command is preparing it stops the run. Inspect what will upload before starting a render:
```bash
hyperframes cloud render --dry-run
+4 -3
View File
@@ -2701,9 +2701,10 @@ Env files (`.env`, `.env.*`, `.envrc`, at any depth) and Studio's private record
under `.hyperframes/` are always left out, even when a rule re-includes them, and
each one is reported as left out with the reason `private`.
Media files of 5 MB or more that the project names by path go up as HeyGen
assets before zipping, and the zip's copy of each HTML, CSS, script and JSON
file points at the asset URL instead; your project files are not changed.
When the zip would be over the upload limit, media no page, script or variable
names is left out first, then the largest media files the project names by path
go up as HeyGen assets, just enough for the rest to fit, and the zip's copy of each HTML, CSS,
script and JSON file points at the asset URL instead; your project files are not changed.
Asset URLs are public and unsigned: anyone who has one can fetch the
media. Uploads are cached by content, so a re-render uploads only what changed.
Media the asset API does not take as is is converted on your machine first,