You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I work mainly in TypeScript on durable execution and agent-runtime infrastructure, so trigger.dev is right in the area I want to keep building in. To start, I would like to fix #4002.
The logical replication client in internal-packages/replication/src/client.ts uses 946080000000 as the Postgres-to-Unix epoch offset in two spots (the keepalive decode around L366 and the standby status ack around L661), but the correct value is 946684800000 (2000-01-01 UTC). It is off by exactly 7 days, and the sibling parser pgoutput.ts already has it right. I would centralize a single named POSTGRES_EPOCH_MS constant, use it in both places, and add a unit test pinning it to the real epoch. I already have the fix and a container-free regression test working locally (typecheck, lint, and test all green).
Most of my open-source work is TypeScript backend/runtime and durable-execution adjacent: a graph-extractor fix to Vercel's Workflow SDK (durable workflow framework), plus merged fixes in Open Design (an agent-orchestration daemon) and Vexa (a meeting-bot/transcription platform, including a security fix).
Activity
matt-aitken commentedon Oct 7, 2026
We have a new Vouch policy, please see the discussion here: #5010