historiangateway history: #115 live gate passed, #126 filed, #85/#58 status

This commit is contained in:
Joseph Doherty
2026-11-10 11:14:45 -05:00
parent e1ad6becb0
commit bcbf1d006f
@@ -76,3 +76,4 @@ for persistence evidence.
- **2026-11-10 (later):** required CI status check removed from `main` protection by user decision (merges do not wait on CI; force-push/delete still blocked). #64 closed: dashboard rail adopts the Theme kit look (local `.rail-*` overrides deleted, PR #125 → `a4adbbd`).
- **2026-11-10 HistorianGateway consumer packages 0.4.0 (historiangw#119 completed).** OtOpcUa master `16111a5eee20975cafd35dd0f7073e33e4c8f7dc` pins both Client and Contracts to 0.4.0 and documents compatibility. This isolated commit leaves the OPC UA SDK at 1.5.378.182; the 2.0 migration remains separate and is not released. Forced uncached restore verifies both packages; Release build has zero warnings/errors; Gateway.Tests 520 passed, zero failed, six existing live-fixture skips; three published-client CA-bundle probes pass (valid bundle accepted, malformed/partially imported bundle rejected). No ReadBlocks gateway API usage required adaptation. Existing caller-provided event IDs, UInt16-to-UInt4 mapping, numeric-only continuous history and DA-quality conversion remain. No new string backfill/status-field behavior is enabled against older gateways. No deployment or live writes; gateway rollout #78 and skipped live cases remain separate. ScadaBridge wire behavior unchanged.
- **2026-11-10 (#115 closed):** F1b live gate passed against `wonder-sql-vq03`+`vq04` (a HistorianPartner pair that does NOT copy tags/values/deletes between members). The gateway ran in Docker, member outages were cut by iptables DROP in a sidecar (`docker/f1b-gate/run-gate.sh`), and all 5 scenarios passed. The gate found and fixed a bug: a `FailedPrecondition` member summary was lost on `AddHistoricalValues`/`SendEvent`. PR #127 → `7819df7`. Follow-up #126 (`GetStoreForwardStatus` unavailable while `Historian:Host` is down). Redundancy plus store-forward may now be enabled together on boxes running this main. #85 probes: the job-status layout is confirmed; an idle job finishes in ~1 s and its record is kept ~31 s. #58 TLS flip is done on branch `tls-secure-default` (uncommitted, awaiting the 1.0.0 decision).