Alarms: residuals from the #587/#586 reviews #597
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
#587 fixed one-event-per-method; its reviews recorded these as not done.
Sources: closing comments on #586/#587; src/Server/ZB.MOM.WW.OtOpcUa.OpcUaServer/OtOpcUaNodeManager.cs:1291-1296,1555-1660; docs/AlarmTracking.md; docs/security.md.
UnshelveTimereads ~24.8 days (MaxTimeShelved = int.MaxValue, shelvingTime 0) though the engine expires it on time — project the real remaining time/alertsack path has no testEventsMonitoredunit never reaches conditions materialised later under a subscribed folder — only costs an audit event while auditing is onFiled 2026-10-08 by the pending/deferred-work sweep after the #562–#591 issue sweep.
Resolved on master (
bd638106, 83e9ffd2; mergesca0f1e77andb99aea46).UnshelveAtUtc, so UnshelveTime counts down to the real expiry instead of ~24.8 days. Review R1 follow-up: the SDK timed-unshelve timer is now a no-op because the engine owns expiry (otherwise both pair nodes routed a "system" Unshelve ahead of the engine's AutoUnshelve).Part9StateMachineTests,ConditionMethodEventTests).AlertsAckPathTests(AdminUI.Tests).BadInvalidStatewith nothing routed, applied or reported (NativeAlarmAckPrimaryGate, fed fromIDriverPrimaryRoleSource); the previous flap is gone. Primary verdict is published from host start (b99aea46).Closed 2026-10-08 by the hardware-available issue sweep (master
d898262c).