The review-participant recovery comment said the row holds a null responsible user only while queued. It does not say claimQueuedRun can cancel a queued row before it resolves that value, so a cancelled row keeps a null value for good. It also said resolving the value at this insert would add a throw inside the release transaction. The immediate-recovery writer resolves its value the same way, in the same transaction, so that was not the actual reason. State the real one: claimQueuedRun already resolves and writes a responsible user for every queued run when it claims one, so this writer leaves that work to it. Co-authored-by: Paperclip <noreply@paperclip.ing> |
||
|---|---|---|
| .. | ||
| scripts | ||
| src | ||
| CHANGELOG.md | ||
| package.json | ||
| tsconfig.json | ||
| vitest.config.ts | ||