Repository navigation
v0.7.2 — Resilience verification: every process proven to survive restarts
v0.7.1 added broker and database reconnection, but its CI proof was a single
"restart db, run the sample" step with no per-process assertions. This release
closes that: the docker CI job now proves, per process, that the worker,
publisher and scheduler each survive a broker restart and a PostgreSQL
restart with no process restart.
The reconnection matrix
| Process | Broker restart | PostgreSQL restart |
|---|---|---|
| Worker | docker step (reconnecting in) + pytest test_a_dropped_connection_redelivers_and_completes_exactly_once |
docker step (post-restart run reaches SUCCEEDED) |
| Publisher | docker step (Publisher recovered) |
docker step (Publisher recovered) |
| Scheduler | N/A — the scheduler never connects to the broker; container ID unchanged | docker step (Scheduler recovered) |
Each step asserts the recovery log, diffs container IDs before/after (a manual
restart would change them), and requires a freshly queued run to reach
SUCCEEDED on its own.
Still UNVERIFIED (no named test)
- Clock skew across processes.
- Multi-node / quorum failover, disk loss — only single-node crash safety.
- A worker that is killed, not merely disconnected.
Verification
All five CI jobs green on PR #34:
https://github.com/Abolfazlrwm/flowforge/actions/runs/39670184431
The proof is CI-only — it needs real PostgreSQL and RabbitMQ, which only the
docker job restarts.
Full changelog: https://github.com/Abolfazlrwm/flowforge/blob/v0.7.2/CHANGELOG.md