dev_agentandClaude Opus 5.5 f95a31472b Bound the suggestion batch's end write like a job's final write ...

runBatch recorded the batch's end with an uncancellable context and no
deadline, before its handler returned, so a writer connection that
stayed busy could hold the worker, and shutdown, open indefinitely.

jobs.FinalWriteContext now gives every final write one bounded attempt
context (FinalWriteTimeout, 5 seconds, not cancelled with ctx); the
runner's record and finishBatch both use it. On timeout at shutdown the
handler returns, the job and batch stay running, the next Start fails
the job as interrupted and the next StartBatch fails the orphaned batch.

TestBlockedBatchEndDoesNotHoldShutdown holds the writer while a batch
reaches finishBatch and asserts the worker stops within the bound and
the batch is reconciled after restart. TestBlockedFinalWriteDoesNotHoldShutdown
no longer sets a runner field, so it compiles against earlier heads.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-07 00:40:52 -04:00

..

batch.go

Bound the suggestion batch's end write like a job's final write

2026-10-07 00:40:52 -04:00

suggest_test.go

Bound the suggestion batch's end write like a job's final write

2026-10-07 00:40:52 -04:00

suggest.go

Bound the suggestion batch's end write like a job's final write

2026-10-07 00:40:52 -04:00