Priya RamanandPaperclip 35b9432c11 fix(server): stop Sentry from re-crashing the process on the neutralized postgres fault ...

Sentry's default `OnUncaughtException` integration registered its own
`uncaughtException` listener. Node calls every registered listener, not
just the first one, so that listener still ended the process on the
known, neutralized postgres driver crash even after the guard's own
listener logged and returned. The initializer now removes that default
integration, and the guard reports every uncaught exception it does not
neutralize to Sentry itself (through `captureException`, then
`shutdownSentry` to flush) before it ends the process. Documents
POSTGRES_NULL_SOCKET_GUARD_ENABLED in doc/observability.md.

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

2026-09-04 01:45:17 +00:00

..

scripts

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

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

src

fix(server): stop Sentry from re-crashing the process on the neutralized postgres fault

2026-09-04 01:45:17 +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