think-backandClaude Opus 5.5 abd60ce60a fix(store): acknowledge analytics versions after projection commits (#404) ...

The analytics worker acknowledged projected queue versions inside its
repeatable-read projection transaction. Request updates keep rewriting
pending queue rows through the source triggers, and once such a change
commits after the worker snapshot, the acknowledgement row lock fails with
a serialization error instead of skipping the stale version. Under steady
traffic every cycle rolled back the whole projection batch, the queue kept
growing and the worker stayed in backoff.

Commit the projection and publication first, then acknowledge the exact
versions in a separate read-committed transaction. Row locks there
re-check the latest committed version, so rewritten versions no longer
match and stay queued for replay, while locked rows are still skipped.

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-12 13:50:02 +08:00

..

apps

perf(store): scale request analytics and isolate request history (#389)

2026-10-11 20:57:36 +08:00

crates

fix(store): acknowledge analytics versions after projection commits (#404)

2026-10-12 13:50:02 +08:00

migrations

fix(observability): preserve query budgets and usage history

2026-10-12 00:15:40 +08:00

Cargo.lock

chore(deps): bump the minor-and-patch group in /backend with 5 updates (#399)

2026-10-12 12:05:19 +08:00

Cargo.toml

fix(providers): align Codex 0.162 protocol handling

2026-10-09 12:10:02 +08:00

rust-toolchain.toml

refactor: migrate backend to Rust 1.97 and edition 2024

2026-07-12 19:10:56 +08:00