Daniel Sutton
906d5fafb6
## Summary - Introduce the Mollifier: a Redis-backed buffer for `trigger()` API calls during traffic spikes, with a per-env trip evaluator and a drainer ack-loop. - Phase 1 is dual-write monitoring — every mollified trigger is buffered to Redis AND continues to `engine.trigger`. No customer-facing behaviour change. - Telemetry events: `mollifier.would_mollify`, `mollifier.buffered`, `mollifier.drained`, plus the `mollifier.decisions` counter. - Gated behind a feature flag (default off). ## Test plan - [x] `pnpm run test --filter @trigger.dev/redis-worker` - [x] `pnpm run test --filter webapp -- mollifier` - [x] Manual: with flag off, no behaviour change vs main - [x] Manual: with flag on + threshold lowered, observe `mollifier.buffered` + `mollifier.drained` log pairs with matching `runId` --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
7 lines
254 B
TypeScript
7 lines
254 B
TypeScript
// Load apps/webapp/.env into process.env so env.server's top-level
|
|
// EnvironmentSchema.parse(process.env) succeeds in vitest workers.
|
|
import { config } from "dotenv";
|
|
import path from "node:path";
|
|
|
|
config({ path: path.resolve(__dirname, "../.env") });
|