Files
ysolanky 13431c7477 fix: order serialized session turns by store acceptance, pin READ COMMITTED
- Stamp a per-session sequence into the payload at enqueue (Postgres advisory
  lock, Redis WATCH on the session index, in-memory lock); session election
  compares (session_seq, id) instead of (created_at seconds, uuid4), so two
  turns submitted in the same second no longer run in random order.
- Pin READ COMMITTED on the claim transaction (and serialized enqueues) instead
  of raising, which stalled every job behind a serialized head under a stricter
  engine default.
- Fetch the full candidate row in the FOR UPDATE scan, dropping a round trip
  from every claim.
- Run the serialized queue suite against the PR CI Postgres service.
2026-10-11 12:45:46 -04:00
..
2025-05-29 22:46:52 -04:00