Joseph Doherty
7a94f7adf0
v2-ci / build (pull_request) Failing after 41s
v2-ci / unit-tests (tests/Core/ZB.MOM.WW.OtOpcUa.Cluster.Tests) (pull_request) Has been skipped
v2-ci / unit-tests (tests/Server/ZB.MOM.WW.OtOpcUa.ControlPlane.Tests) (pull_request) Has been skipped
v2-ci / unit-tests (tests/Server/ZB.MOM.WW.OtOpcUa.OpcUaServer.Tests) (pull_request) Has been skipped
v2-ci / unit-tests (tests/Server/ZB.MOM.WW.OtOpcUa.Runtime.Tests) (pull_request) Has been skipped
v2-ci / unit-tests (tests/Server/ZB.MOM.WW.OtOpcUa.Security.Tests) (pull_request) Has been skipped
v2-ci / integration (tests/Server/ZB.MOM.WW.OtOpcUa.Host.IntegrationTests) (pull_request) Has been skipped
v2-ci / integration (tests/Server/ZB.MOM.WW.OtOpcUa.OpcUaServer.IntegrationTests) (pull_request) Has been skipped
The gateway now populates Runtime.dbo.Events.Source_Object from the event SourceName (gateway C4 fix: HistorianProtoMapper threads SourceName into the `source_object` event property). So an ad-hoc alarm SendEvent is now source- filterable on readback, and Alarm_SendEvent_then_ReadEvents asserts the round- trip instead of skipping with the old "ad-hoc sends land without Source_Object" reason. Poll window widened to 60s for the live event-view flush latency. Live-proven at the gateway level (HistorianGateway EventSourceObjectProbeTests, 2026-06-27); this asserts the same round-trip through the OtOpcUa alarm writer + data source adapters. Claude-Session: https://claude.ai/code/session_012SDSQ3AcaXqPcBtDESBRii