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

docs(opcuaclient): #657 review — correct stale rebuild comment, note cold-host residual

Browse Source 
Claude-Session: https://claude.ai/code/session_01Ef2ozxS7QPanGT8uoATbTe
This commit is contained in:
Joseph Doherty
2026-10-09 07:15:26 -04:00
parent 48a80b5962
commit 24eed8addd
2 changed files with 5 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/AlarmTracking.md
+1 -1
View File
@@ -98,7 +98,7 @@ same condition is wired as an **event notifier of every referencing equipment fo
flagged — so a host already showing that state writes nothing, and a host that retained the condition Active gets a
real "Cleared". Pre-#657 a respawn wrote a duplicate "Activated" + "Cleared" pair per inactive+unacked condition, and
an inactive+acked first sight went out as `Unspecified` (an "Activated" row for an inactive alarm; a retained-Active
condition was never cleared). E2E: `Runtime.Tests/NativeAlarmRestatementEndToEndTests`.
condition was never cleared). Residual (pre-existing, not a regression): a cold host treats an unseen condition as acked, so after a node restart each upstream inactive+unacked condition still writes "Activated" + "Cleared" once. E2E: `Runtime.Tests/NativeAlarmRestatementEndToEndTests`.
### Native condition state survives a full rebuild (Gitea #641)