Skip to content

Code-first video & image, rendered natively on WebGPU.

docs(renderer-service): RunPod Serverless retest results

okanasle2e054b97589
diff --git a/apps/renderer-service/PLAN.md b/apps/renderer-service/PLAN.md
index c79b0831..a64723db 100644
--- a/apps/renderer-service/PLAN.md
+++ b/apps/renderer-service/PLAN.md
@@ -629,13 +629,14 @@ Each phase is its own PR-sized step with tests.
- **Results never reached RunPod:** every POST to the SDK's `job-done` URL returned 500, so RunPod re-queued finished jobs. The URL in the log was `…/job-done/<worker>/<job>&isStream=false`: the platform's URL had no query string, and the SDK appends `&isStream=…`. The shim now adds the missing `?` before importing the SDK and logs the URL's shape.
- **The network volume reports 2.3 PB,** so free-space eviction is off for it; the serverless template sets `FF_CACHE_MAX_GB`.
- RunPod started three workers on an endpoint with `max: 1`.
+ - **Retest with `:2.2.0-beta.2` (RTX 4000 Ada and RTX A4500):** this time RunPod's URLs had a query string (`…/job-done/<worker>/$ID?gpu=…`, from the shim's startup log), so the fix didn't need to apply. Progress reached `/status` (phase, frame, fps, ETA) and both jobs ended `COMPLETED` with their results. `threeD`: 43 s total. `all`: 174 s total (checkout 17.5 s, install 14.7 s, render 139 s, upload 2.7 s). LFS was a cache hit from the network volume on both fresh workers.
- **LFS end to end:**
- `src/git/lfs.test.ts` runs real git-lfs (3.8) against file:// origins. It covers a cold download into the shared store, a warm hit, objects shared across repos, include patterns with the `LFS_POINTERS_LEFT` warning, LFS off, and a missing object (`LFS_OBJECT_MISSING`).
- In the arm64 container (git-lfs 3.6.1), a repo whose framefields tarball and logo PNG are both LFS-tracked installed from the LFS tarball and rendered the logo (centre pixel red). The job reported `cache.lfs: "miss"`.
- Two file://-only bugs were found and fixed. With `-c lfs.storage`, git-lfs's local transfer agent also looked for the remote's objects in our store, so the setting now goes in the repo config. The agent drops `GIT_CONFIG_GLOBAL` and `-c` but reads `$HOME/.gitconfig`, so the session's isolated config now lives there, with `safe.directory` for local repos (otherwise "dubious ownership" on a mounted repo).
- **Engine issue found and fixed in framefields (§8.7):** on linux-arm64, H.264 renders failed with "Encoder 'h264_rkmpp' cannot be used for quantizer-based encoding". The cause was @mediabunny/server taking FFmpeg's first registered H.264 encoder (node-av's build lists `h264_rkmpp` before libx264), not `@napi-rs/webcodecs`. With the fixed framefields (packed locally), an H.264 job in the arm64 container rendered 48/48 frames with libx264 on lavapipe. `FF_GPU=require` on the same container fails readiness with `GPU_UNAVAILABLE`.
- Pinned SSH host keys, the RunPod templates and `create-template.sh`, `docker-compose.yml` with MinIO, `env.example`, the release workflow, and the README guide as listed above.
- - **Still to do:** an amd64 build (CI), a serverless run that returns its result (after the shim fix), the nightly host smoke tests (6.5), and a page on the docs website.
+ - **Still to do:** an amd64 build (CI), the nightly host smoke tests (6.5), and a page on the docs website.
9. **(Later)**
- Chunked distributed rendering: split a frame range across N jobs and concat with a stream copy.
- Webhooks on completion (`output.webhook` with an HMAC signature).