mirror of
https://github.com/heygen-com/hyperframes.git
synced 2026-08-31 02:41:44 +00:00
James Russo
c50f59a53b
* feat(lambda): add Lambda handler, ZIP bundling, and BeginFrame probe
Phase 6 of the distributed rendering plan: AWS Lambda turnkey adoption
(see DISTRIBUTED-RENDERING-PLAN.md §11 Phase 6 + §15).
This PR adds the new packages/aws-lambda/ workspace package that wraps
the OSS plan/renderChunk/assemble primitives in an AWS Lambda handler,
plus a build pipeline that bundles the handler + Chromium runtime +
ffmpeg into a deployable ZIP.
Architecture: ZIP deploy (not Docker image), Chrome via @sparticuz/chromium
with chrome-headless-shell fallback, dispatch on event.Action ∈ {plan,
renderChunk, assemble}.
The load-bearing concern — does @sparticuz/chromium's chrome-headless-shell
build honour CDP HeadlessExperimental.beginFrame? — is pinned by the new
scripts/probe-beginframe.ts regression guard. Probe boots the runtime
inside public.ecr.aws/lambda/nodejs:22, navigates to a static page, and
asserts beginFrame returns a PNG buffer. Verified locally + inside the
Docker container; both pass with hasDamage=true.
Sizes (sparticuz source): unzipped 157 MiB, zipped 99 MiB. Well under
the 240 MiB / 150 MiB in-house gates and the Lambda 250 MiB hard ceiling.
This is part of a stack of 8 PRs (3 in Phase 6a, 5 in Phase 6b); this is
PR 6.1.
* fix(lambda): address PR 878 review feedback
- Verify event.PlanHash against the untarred plan.json at the handler
boundary before invoking the producer primitive. Throws typed
PLAN_HASH_MISMATCH on divergence so Step Functions routes it as
non-retryable; previously the field was schema bloat the handler
ignored, leaving enforcement entirely inside the producer.
- Standardize on MiB throughout build-zip.ts, verify-zip-size.ts, and
the README. Lambda's hard ceiling is 250 MiB (AWS docs label "250 MB"
but use binary mebibytes); previously mixed units made the 248 MiB
budget look like a ~5 MB margin instead of the 2 MiB it actually is.
- stageChromeHeadlessShell now picks Chrome versions via numeric semver
comparison instead of lexicographic sort+reverse — the latter would
silently pick "99.x" over "131.x" once Chrome cached three-digit
majors that aren't width-aligned.
- Drop _setSparticuzChromiumForTests from the public index barrel.
Test-only DI seam imported directly from ./chromium.js in tests.
- Replace require("node:fs") inside walkSize() with the top-level fs
imports — file is ESM and the same module is already imported.
* docs(lambda): drop internal plan-doc refs from package README
* ci(windows): fix bun filter UNION bug excluding producer from Windows tests
`bun run --filter "!a" --filter "!b" test` composes as a UNION (any
package matching either negation runs), not an intersection. Effect:
@hyperframes/producer was still being tested on Windows even though
it's explicitly excluded — its regression harness (Docker + LFS golden
mp4 baselines) is Linux-only and was driving the 32min timeout.
Enumerate the packages we DO want to test instead.
84 lines
2.8 KiB
TypeScript
84 lines
2.8 KiB
TypeScript
#!/usr/bin/env tsx
|
|
/**
|
|
* CI gate on the Lambda ZIP size.
|
|
*
|
|
* Reads `dist/handler.zip.manifest.json` (written by `build-zip.ts`) and
|
|
* exits non-zero if either the unzipped or zipped size exceeds the
|
|
* declared limits. Lambda's hard ceiling for ZIP-deployed functions is
|
|
* 250 MiB unzipped (262144000 bytes — AWS docs label it "250 MB" but use
|
|
* binary mebibytes); the in-house budget is 248 MiB to keep headroom for
|
|
* the Chrome tarball decompression that happens at cold start.
|
|
*/
|
|
|
|
import { existsSync, readFileSync, statSync } from "node:fs";
|
|
import { dirname, join, resolve } from "node:path";
|
|
import { fileURLToPath } from "node:url";
|
|
import { formatBytes } from "./_formatBytes.js";
|
|
|
|
const scriptDir = dirname(fileURLToPath(import.meta.url));
|
|
const packageRoot = resolve(scriptDir, "..");
|
|
const distDir = join(packageRoot, "dist");
|
|
const zipPath = join(distDir, "handler.zip");
|
|
const manifestPath = join(distDir, "handler.zip.manifest.json");
|
|
|
|
interface Manifest {
|
|
unzippedBytes: number;
|
|
zippedBytes: number;
|
|
source: string;
|
|
}
|
|
|
|
const IN_HOUSE_UNZIPPED_LIMIT = 248 * 1024 * 1024;
|
|
const IN_HOUSE_ZIPPED_LIMIT = 150 * 1024 * 1024;
|
|
|
|
function main(): void {
|
|
if (!existsSync(zipPath)) {
|
|
console.error(`[verify-zip-size] ${zipPath} not found. Run 'bun run build:zip' first.`);
|
|
process.exit(1);
|
|
}
|
|
if (!existsSync(manifestPath)) {
|
|
console.error(
|
|
`[verify-zip-size] ${manifestPath} not found. The manifest is written by build-zip.ts; ` +
|
|
`re-run the build.`,
|
|
);
|
|
process.exit(1);
|
|
}
|
|
|
|
const manifest = JSON.parse(readFileSync(manifestPath, "utf-8")) as Manifest;
|
|
const actualZipped = statSync(zipPath).size;
|
|
if (actualZipped !== manifest.zippedBytes) {
|
|
console.warn(
|
|
`[verify-zip-size] note: zip file size on disk (${actualZipped}) differs from ` +
|
|
`manifest (${manifest.zippedBytes}). Using on-disk value.`,
|
|
);
|
|
}
|
|
|
|
let failed = false;
|
|
if (manifest.unzippedBytes > IN_HOUSE_UNZIPPED_LIMIT) {
|
|
console.error(
|
|
`[verify-zip-size] FAIL unzipped: ${formatBytes(manifest.unzippedBytes)} > ` +
|
|
`${formatBytes(IN_HOUSE_UNZIPPED_LIMIT)} (in-house limit; Lambda hard ceiling is 250 MiB).`,
|
|
);
|
|
failed = true;
|
|
}
|
|
if (actualZipped > IN_HOUSE_ZIPPED_LIMIT) {
|
|
console.error(
|
|
`[verify-zip-size] FAIL zipped: ${formatBytes(actualZipped)} > ` +
|
|
`${formatBytes(IN_HOUSE_ZIPPED_LIMIT)} (in-house limit; Lambda direct-upload ceiling is 50 MiB, ` +
|
|
`S3-deploy ceiling is 250 MiB).`,
|
|
);
|
|
failed = true;
|
|
}
|
|
|
|
if (failed) {
|
|
console.error("[verify-zip-size] FAILED — bundle is too large for Lambda ZIP deploy.");
|
|
process.exit(1);
|
|
}
|
|
console.log(
|
|
`[verify-zip-size] OK source=${manifest.source} unzipped=${formatBytes(
|
|
manifest.unzippedBytes,
|
|
)} zipped=${formatBytes(actualZipped)}`,
|
|
);
|
|
}
|
|
|
|
main();
|