Record OtOpcUa documentation merge and CI follow-up evidence
This commit is contained in:
@@ -370,3 +370,6 @@ AddRoute of the dev Mac (`oee-tagdump-mac`, `10.181.206.245.1.1`) on the two tes
|
|||||||
- **2026-10-13 #702 resolved (PR #704, master `0ccfbbee`, fix `dccab57d`).** Restart wire assertion accepts explicit definitive session/closed-channel loss reasons, preserving all outage/value/frozenstamp/count/reinitialization recovery checks. Production unchanged. Actual red reason BadSessionIdInvalid captured; corrected isolated1/1, deterministic routes30/30, full integration122/122, full offline solution14,613 passed /611 skipped /0failed (host266pass/14environment-fixture skips). Independent review clear; merged tree matches verified branch; #702 closed. Main checkout fast-forwarded preserving user changes.
|
- **2026-10-13 #702 resolved (PR #704, master `0ccfbbee`, fix `dccab57d`).** Restart wire assertion accepts explicit definitive session/closed-channel loss reasons, preserving all outage/value/frozenstamp/count/reinitialization recovery checks. Production unchanged. Actual red reason BadSessionIdInvalid captured; corrected isolated1/1, deterministic routes30/30, full integration122/122, full offline solution14,613 passed /611 skipped /0failed (host266pass/14environment-fixture skips). Independent review clear; merged tree matches verified branch; #702 closed. Main checkout fast-forwarded preserving user changes.
|
||||||
|
|
||||||
- **2026-10-13 alarm identity #705 merged (PR #706, master `7b238750`, fix `10916362`).** Transport-only nonzero GUIDs survive direct retry/copy and derive from persisted queue keys for durable retry/restart/replication/legacy/revival. Exact queue JSON/key/schema/dedup, business equality/hash and AlarmId unchanged; SQL/QuestDB identity logic unchanged. RED empty wire and changing queue IDs reproduced; Core 51/51, migration/convergence 16/16, Gateway 453 passed / 6 live skipped. Full offline solution 14,635 passed / 611 skipped / 0 failed across 62 suites; independent review clear and merged tree equals verified branch. #705 closed. No deployment/live writes/historical rewrite; Gateway #28/#39 live persistence/timestamp gates remain open, as do #29 and lmxopcua #694/#700.
|
- **2026-10-13 alarm identity #705 merged (PR #706, master `7b238750`, fix `10916362`).** Transport-only nonzero GUIDs survive direct retry/copy and derive from persisted queue keys for durable retry/restart/replication/legacy/revival. Exact queue JSON/key/schema/dedup, business equality/hash and AlarmId unchanged; SQL/QuestDB identity logic unchanged. RED empty wire and changing queue IDs reproduced; Core 51/51, migration/convergence 16/16, Gateway 453 passed / 6 live skipped. Full offline solution 14,635 passed / 611 skipped / 0 failed across 62 suites; independent review clear and merged tree equals verified branch. #705 closed. No deployment/live writes/historical rewrite; Gateway #28/#39 live persistence/timestamp gates remain open, as do #29 and lmxopcua #694/#700.
|
||||||
|
|
||||||
|
- **2026-10-13 Galaxy acknowledgement documentation merged (PR #708, master `495606b9`).** Corrected AlarmTracking, ScriptedAlarms and the historical design note to distinguish the correlated Gateway acknowledgement RPC from actor failure handling and the already committed local OPC UA acknowledgement. Documentation-only review against current implementation; #614 remains open for H6 live AVEVA history acknowledgement and multiplatform ScanStateParity acceptance. Main checkout fast-forwarded; pre-existing .gitignore/CLAUDE.md contents and untracked .claude/ preserved. No deployment.
|
||||||
|
- **Current CI follow-up #707:** run #952 executed 14,630 tests but failed 18 across unrelated suites on a heavily loaded 22-CPU runner with fully used swap. Seven selected hermetic cases passed in five sequential Release invocations (0 failures/skips). Contention is a hypothesis, not a proven common cause. #606 remains open for a verified green CI run; workflow resource bounds await a concrete approved design.
|
||||||
|
|||||||
Reference in New Issue
Block a user