From 57d2d193fc48ebba0ec7c8d81daaccbe95198b74 Mon Sep 17 00:00:00 2001 From: Joseph Doherty Date: Sat, 18 Jul 2026 14:13:23 -0400 Subject: [PATCH] docs(secrets): link the Akka deadlock to its tracking issues scadaproj#1 holds the defect (the library lives here); lmxopcua#482 is the consumer-side tracker keeping Secrets:Replication:Enabled=false until it is fixed. --- components/secrets/GAPS.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/components/secrets/GAPS.md b/components/secrets/GAPS.md index b205dc8..f710e40 100644 --- a/components/secrets/GAPS.md +++ b/components/secrets/GAPS.md @@ -125,6 +125,9 @@ real host process. Root cause NOT yet identified — candidates: `DistributedPub - ⬜ **Do NOT enable `Secrets:Replication:Enabled` in OtOpcUa.** The Akka topology is not adoptable until this deadlock is root-caused and fixed, with a regression test that creates the actor through DI in a hosted process rather than directly from a test. + **Tracked:** [`scadaproj#1`](https://gitea.dohertylan.com/dohertj2/scadaproj/issues/1) (the defect, + where the library code lives) and [`lmxopcua#482`](https://gitea.dohertylan.com/dohertj2/lmxopcua/issues/482) + (the consumer-side tracker: bump the package, re-run the gate, then consider enabling). - ✅ ScadaBridge's hub topology **is** live-validated and safe to enable (config + a shared KEK). Harness: `scratchpad/livegate/` (two scenarios, `akka` / `sql`; not committed).