Naiyuan Qing 78789e8da8 fix(comments): lock thread root to serialize concurrent resolves ...

Under READ COMMITTED, two concurrent resolves of different comments in
the same thread could each miss the other's uncommitted resolution in
ClearOtherThreadResolutions and commit two resolved rows. Take a FOR
UPDATE lock on the thread root in its own statement before clearing, so
the loser blocks and its clear re-runs on a fresh snapshot that sees the
winner's committed resolution.

Also updates the stale loadCommentForActor docstring that still
described the backend as a plain setter with frontend-derived
resolution — the single-resolution invariant is now enforced on write.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-06-10 14:30:01 +08:00

..

cmd

Revert "MUL-3132: harden /uploads/* (auth, no listing, nosniff, tight CSP) (#…" (#3944)

2026-06-09 14:50:56 +08:00

internal

fix(comments): lock thread root to serialize concurrent resolves

2026-06-10 14:30:01 +08:00

migrations

fix(db): drop FK on agent_task_queue.initiator_user_id (MUL-2645) (#3959)

2026-06-09 19:59:20 +08:00

pkg

fix(comments): lock thread root to serialize concurrent resolves

2026-06-10 14:30:01 +08:00

go.mod

test(migrate): concurrent migration race test using real Postgres (MUL-2956) (#3712)

2026-06-08 13:33:16 +08:00

go.sum

…

sqlc.yaml

…