DuncanandWill Pfleger 3a9bd9908b fix(relay): make admin cancel atomic + ownership-fenced (cross-report 409) ...

cancel_action fenced only on id+state='failed'+step_marker IS NULL, with
no report/community constraint, and discarded the report-reopen row count.
POST /reports/A/cancel {actionId:B} cancelled B's action, stranded B as
processing with a terminal action, and returned a fabricated {status:"open"}
for A.

Make cancellation one atomic, ownership-fenced transition mirroring
finalize_success: the action UPDATE now also fences report_id +
report_community_id, the report UPDATE now also fences status='processing',
and both updates must each affect exactly one row or the whole transaction
rolls back to false -> 409 with zero state change. This is what makes the
handler's hard-coded "status":"open" legitimate.

Adds an HTTP->DB regression: two processing reports sharing a community,
each with a distinct failed action; /reports/A/cancel {actionId:B} must 409
and leave both reports and both actions byte-for-byte unchanged.

Co-authored-by: Will Pfleger <pfleger.will@gmail.com>
Signed-off-by: Will Pfleger <pfleger.will@gmail.com>

2026-08-13 05:47:01 -04:00

..

src

fix(relay): make admin cancel atomic + ownership-fenced (cross-report 409)

2026-08-13 05:47:01 -04:00

Cargo.toml

feat(tracing): add PostgreSQL tracing spans (#3678)

2026-08-12 08:04:54 +10:00