Close archive writers when the delivery engine stops (closes #280) #332

Merged

clawbot merged 2 commits from issue-280-close-archives-at-stop into next

2026-09-29 08:30:24 +02:00

Author	SHA1	Message	Date
clawbot	d03bb0ed08	Correct the stop timeout comments on the archive writers check / check (push) Successful in 4m28s Details The comments on the engine's stop and on the timeout test gave false reasons for leaving archive writers open when the stop budget runs out. Closing them would wait for any write in progress, and a worker still running would then open new writers that nothing closes, so closing gains nothing over a kill. Model: opus-5-5	2026-09-29 05:48:54 +00:00
clawbot	4452ef71fb	Close archive writers when the delivery engine stops (closes #280 ) The engine cached archive writers and never closed them at shutdown, so after a clean stop an archive's rows could sit in its -wal while the .db held no table. The engine's stop hook now evicts every cached writer once its workers have returned, the same way deleting a webhook does, so a clean stop leaves each archive as one file and a late write is refused. If the workers do not return within the stop budget, the writers are left open as a kill would leave them. The README no longer says archives keep their sidecars across a clean stop. Model: opus-5-5	2026-09-29 05:48:33 +00:00

Author

SHA1

Message

Date

clawbot

d03bb0ed08

Correct the stop timeout comments on the archive writers

check / check (push) Successful in 4m28s

Details

The comments on the engine's stop and on the timeout test gave false
reasons for leaving archive writers open when the stop budget runs
out. Closing them would wait for any write in progress, and a worker
still running would then open new writers that nothing closes, so
closing gains nothing over a kill.

Model: opus-5-5

2026-09-29 05:48:54 +00:00

clawbot

4452ef71fb

Close archive writers when the delivery engine stops (closes #280 )

The engine cached archive writers and never closed them at shutdown,
so after a clean stop an archive's rows could sit in its -wal while
the .db held no table. The engine's stop hook now evicts every cached
writer once its workers have returned, the same way deleting a webhook
does, so a clean stop leaves each archive as one file and a late write
is refused. If the workers do not return within the stop budget, the
writers are left open as a kill would leave them.

The README no longer says archives keep their sidecars across a clean
stop.

Model: opus-5-5

2026-09-29 05:48:33 +00:00