Priya RamanandPaperclip 312bbad10a fix(server): keep Sentry reporting for uncaught exceptions when the postgres guard is off ...

Sentry's default `OnUncaughtException` integration was removed
unconditionally, but the postgres null-socket write guard only owns the
process's `uncaughtException` decision while it is enabled. With
POSTGRES_NULL_SOCKET_GUARD_ENABLED=false, no listener took its place, so
an unrelated uncaught exception reached no error reporter.

`sentry.ts` now reads the same opt-out through a new leaf module,
postgres-null-socket-guard-env.ts, and keeps the default
OnUncaughtException integration active whenever the guard is disabled.
Splitting the opt-out check into its own module avoids a circular import
between sentry.ts and postgres-null-socket-guard.ts.

Co-authored-by: Paperclip <noreply@paperclip.ing>

2026-09-04 02:08:07 +00:00

..

scripts

fix(server): stamp built commit into service.version (#11748)

2026-08-19 21:20:40 -07:00

src

fix(server): keep Sentry reporting for uncaught exceptions when the postgres guard is off

2026-09-04 02:08:07 +00:00

CHANGELOG.md

fix: bound workspace Git scans (#11572)

2026-08-17 22:11:30 -05:00

package.json

feat(server): add a process-level guard for the postgres driver null-socket write crash

2026-09-04 01:14:47 +00:00

tsconfig.json

Fix root TypeScript solution config

2026-03-09 14:09:30 -05:00

vitest.config.ts

feat(runner): add hidden server PRP coordinator (#12176)

2026-08-25 14:17:14 -05:00