Skip to content

Recover not completed archives after restart.#8

Open
iparask wants to merge 1 commit into
feat/ORMfrom
feat/restart_recovery
Open

Recover not completed archives after restart.#8
iparask wants to merge 1 commit into
feat/ORMfrom
feat/restart_recovery

Conversation

@iparask

@iparask iparask commented Jul 14, 2026

Copy link
Copy Markdown
Member

Archiving is asynchronous and tracks it as an in-memory concurrent.futures.Future. That future is the problem: it lives in a in-process queue. If the server dies mid-copy the archives is not completed. Currently nothing re-picks it up and the archive is silently dropped.

This PR introduces a recovery logic that is run once at startup. This checks if the archive was actually completed or not and updates the DB accordingly. Any archive that is not marked completed, but consumed returns in a non-consumed state and the consumption threads picks it up.

This PR also fixes a postgres bug that did not allow a postgres integration to run.

🤖 Assisted by Claude Opus 4.8

@iparask
iparask requested review from JBorrow and tskisner July 14, 2026 21:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant