feat(budget): Worker runtime budgets — CPU measurement, deploy gate, and fleet analytics #402
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
gmackie/ForgeGraph!402
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "feat/worker-runtime-budgets"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
What
Worker runtime budgets: measure and enforce CPU time for Cloudflare Workers, and report compliance across the fleet.
@forgegraph/worker-budget— wraps a Worker's entrypoint (including an OpenNext adapter) to measure CPU time per request, clamp declaredcpu_ms, and emit violations as structured telemetry. Cron and marker support included./runtime-budgetsdashboard plusforge budget workers cpu,forge budget violations tail, andforge budget summary.Verification
go build ./...andgo test ./...inagent/— green.tsc --noEmitforapps/web— clean.vitest runinapps/web— 169 files, 1033 passed, 40 skipped.Rebased onto
mainat18b3f957with no conflicts.Note for review
TestImmutableWorkerArtifactRunsInstalledWranglerDryRunWithWritableScratchlooked for wrangler and zod underapps/web/node_modules, but pnpm keeps workspace dependencies at the workspace root — so it hard-failed in every environment including CI and never actually exercised Wrangler. It now resolves them by walking up from the app directory the way node resolution does, and skips rather than fails a Go-only checkout. The test now genuinely runs the dry-run (~4s).🤖 Generated with Claude Code
e2906d856a1663361330