dohertj2/scadaproj
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(secrets): link the Akka deadlock to its tracking issues

Browse Source 
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.
This commit is contained in:
Joseph Doherty
2026-07-18 14:13:23 -04:00
parent eb445ea7e7
commit 57d2d193fc
1 changed files with 3 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
components/secrets/GAPS.md
+3
View File
@@ -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).