lfg2025/archy
1
0
Fork 0
Code Issues 9 Pull Requests Actions Packages Projects Releases 44 Wiki Activity

docs(gate): two-node result — stop blocker FIXED; residual red is bitcoin-IBD + node prep

Browse Source 
.228 104/110, .198 94/110 with the 3-fix binary. Every package.stop test passes on
healthy apps. .198's 14/16 failures trace to bitcoin in IBD (test 83: ~137k blocks
behind) cascading to lnd/btcpay/electrumx/mempool. 2 node-independent: companion
recreate (31, both nodes), fedimint orphan pollution (44). Path to green 5x gate is
now infra (sync bitcoin, re-quadletize .228) + minor (test 31), not lifecycle bugs.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
archipelago 2026-06-22 11:09:12 -04:00
parent b090235b04
commit 47a5148865
1 changed files with 23 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
docs/PRODUCTION-MASTER-PLAN.md
View File

@ -269,10 +269,29 @@ were the host-port watchdog firing while I rapid-cycled stop/start (fixed by #2)
key mismatch" was actually the live-UI-companion launch-port issue (#3). "Grace vs gate-timeout"
(electrumx 300s) was moot — a healthy electrumx honours SIGQUIT and stops in <1s.
**Status: validating breadth.** electrumx suite GREEN on .228 (the previously-failing repro). Full
single-iteration gate (all suites, DESTRUCTIVE) running on .228 to confirm the other apps; then .198,
then the 5× canonical gate. `.228` is still contamination-flavored (plain podman) but the fixes are
runtime-agnostic and electrumx passed there regardless. Re-quadletizing .228 + the 5× runs remain.
**TWO-NODE GATE RESULT (1×, DESTRUCTIVE, both with the 3-fix binary):**
- **.228: 104/110.** All previously-failing `package.stop` tests now PASS (bitcoin/btcpay/electrumx/
fedimint/immich). Remaining 6: test 31 (companion recreate), 44 (fedimint orphan — probe
pollution), 55 (immich restart timing), 83 (bitcoin not archival-synced), 94/99 (endpoint/lnd-proxy
cascade from 83).
- **.198: 94/110.** **14 of 16 failures are one root cause: bitcoin is in IBD** (test 83 says
`blocks=817652 headers=954850` — ~137k behind). Everything chained to bitcoin cascades: lnd
(16,85), btcpay (22,23,103), electrumx (37), mempool stack (71,72,73,101), endpoints (94),
bitcoin.getinfo (7,12). The other 2 are node-independent: **31** (companion recreate) and **44**
(fedimint orphan pollution).
**CONCLUSION: the lifecycle-stop blocker is FIXED and validated on both nodes.** The residual red is
NOT lifecycle bugs — it is (a) **bitcoin still syncing (IBD)** on the test nodes [test 83 is an
explicit precondition; nothing electrumx/lnd/btcpay/mempool can pass until it finishes], (b) **.228
plain-podman contamination** (my cascade-gate), and (c) two minor items: **test 31** companion-unit
recreate (both nodes — likely the 90s window vs reconcile tick + image step; investigate) and **test
44** orphan fedimint container left by my probing.
**To reach a literally-green 5× gate (now infra/node-prep, not code):**
1. Let bitcoin finish IBD on a test node (or point the gate at an archival-synced bitcoin).
2. Re-quadletize .228 (reinstall its backends so `.container` units regenerate, matching .198).
3. Investigate test 31 (companion recreate) — confirm code-bug vs load-timeout; clear test-44 orphans.
4. Then run `ARCHY_ITERATIONS=5 ARCHY_ALLOW_DESTRUCTIVE=1` on the synced+quadlet node, then the other.
**Quadlet context (still true, but SEPARATE from the bug above):** quadlet IS the intended backend
runtime — .198 has the backend `.container` files (bitcoin-knots/btcpay-server/fedimint/filebrowser/