fix(force-analyze): release running lease so worker drops stale-payload local (0.87.20)
0.87.11 followup. The UPDATE matched pending+running but the worker holds the pre-update `force=false` in an in-memory local — so on the running branch the row flipped but the worker's skip-if-done still acked done without re-analyzing. Now `jobs::release` any running row the UPDATE matched, so the worker's ack_done no-ops (state guard) and a fresh lease picks up the updated payload. New test mints the running-state shape, asserts state=pending + force=true + attempts=0 post-click. Mutation-confirmed. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
2
backend/Cargo.lock
generated
2
backend/Cargo.lock
generated
@@ -1517,7 +1517,7 @@ checksum = "c41e0c4fef86961ac6d6f8a82609f55f31b05e4fce149ac5710e439df7619ba4"
|
||||
|
||||
[[package]]
|
||||
name = "mangalord"
|
||||
version = "0.87.19"
|
||||
version = "0.87.20"
|
||||
dependencies = [
|
||||
"anyhow",
|
||||
"argon2",
|
||||
|
||||
Reference in New Issue
Block a user