nickyleachandPaperclip 7dcdd6ae1b fix(server): make the task-drain termination audit write idempotent ...

A connection can drop after the database commits the outcome
transaction but before the driver reports success. The retry around
that transaction could not tell the two cases apart, so it could
replay a committed write and create a duplicate outcome row and a
duplicate publication.

Give each termination a stable key from its generation number, and
check for an existing row under that key before every write attempt,
including a retry. The write proceeds only when the check finds none.

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

2026-09-16 08:20:27 +00:00

..

scripts

fix(server): bundle the vendored paperclip-runner instead of hand-mirroring its deps (#13121)

2026-09-09 16:38:17 -07:00

src

fix(server): make the task-drain termination audit write idempotent

2026-09-16 08:20:27 +00:00

CHANGELOG.md

fix: bound workspace Git scans (#11572)

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

package.json

fix: preserve runner recovery, warm sessions, and task outcomes (#13338)

2026-09-12 19:41:15 -05:00

tsconfig.json

…

vitest.config.ts

fix(server): bundle the vendored paperclip-runner instead of hand-mirroring its deps (#13121)

2026-09-09 16:38:17 -07:00