Record gateway correction and reset-echo verification

This commit is contained in:
Joseph Doherty
2026-10-13 10:02:44 -04:00
parent 509114360d
commit 9688707d82
2 changed files with 4 additions and 0 deletions
@@ -25,3 +25,5 @@
- **2026-10-13 SQL Events route/timezone #39 merged (PR #44, main `2dd3917`, fix `0599e12`).** Full bare 37-column OPENQUERY uses fixed widened inner UTC bounds and exact outer date/source parameters before ordering/cap; unlimited mode retained. Explicit `RuntimeDb:EventReceivedTimeZoneId` required when SQL event reads enabled; historical DST conversion rejects gaps/overlaps and missing timestamps, with no inferred host/event offset. Twenty-two new cases; server 1,121 passed/58 skipped; full offline solution 1,917 passed/157 skipped/0 failed, three suites, exit0. Independent review clear; merged tree equals tested branch; #39 closed. Operator zone configuration/local rollout/generated-query live checks tracked #45; #28 identity/duplicate/timestamp persistence remains open. No deployment.
- **2026-10-13 local #45 rollout failed its event-read verification and was rolled back.** Operator confirmed `Eastern Standard Time`; new Linux image resolved the ID and historical DST rules, startup/health stayed Healthy. Authenticated event reads failed with Unavailable. Exact bounded SQL comparison found new ISO T date literals rejected with SQL7321 (50 ms), while the prior verified space form returned nine affected rows (366 ms). #39 reopened; #46 tracks the narrow provider literal correction. Existing image/config restored with both health endpoints200; temporary read-only key revoked and key-store row captured. No event writes. The earlier offline/merge evidence does not establish deployed query compatibility; #28 identity/persistence and historical zone provenance remain open.
- **2026-10-13 provider date correction #46 merged (PR #48, main `6934f9f`, tested fix `a8e582d`).** OPENQUERY dates use the live-verified space separator. Regression rejected the prior T form; 17 SqlEventReader cases passed and hermetic full solution passed 1,918/157 skipped/0 failed. Review clear; merged tree equals tested tree. Corrected local image `zb-historiangw:issue46-6934f9f` built and compose/zone/DST checks passed; separate reroll approval pending. Original local image/config remains restored; #39/#45/#46 live gates remain open. First full attempt inherited live variables and confirmed an unintended 42.0/quality192 historical write to HistGW.LiveTest.Sandbox; other enabled write-test execution is unknown. All involved processes stopped, no cleanup writes; #47 tracks explicit read/write opt-in test gates. Successful rerun stripped live settings.
@@ -1,3 +1,5 @@
# ScadaBridge — index history
- **2026-10-13 existing fixes verified and issues closed.** Main `513fa1aa` already includes #35 fail-closed unavailable configured body/SQL redactors (`006202f3`) and #37 Flow Debugger structured/raw validated method inputs (`b5eb08f1`). Fresh full AuditLog project 407 passed/0 failed; FlowDebuggerPageTests 47 passed/0 failed; both terminal exit0. Remote ancestry confirmed; #35/#37 closed with evidence. No source changes/deployment/MES transactions. #36 runtime reset-echo overload is implemented, but QA/prod script port remains tracked; #30 per-site PSK deployment gate remains open.
- **2026-10-13 #36 runtime regression proof refreshed.** Rebuilt HandshakeResetEchoTests passed all three cases with local fakes, terminal exit0; an earlier no-build attempt matched no tests and is excluded from evidence. Tracker now distinguishes implemented runtime b623fdb0 from remaining QA/prod database-owned script rollout (deployment register row119, scripts13/14/36 and15/16/25/26/37/38). No database writes, deployments or fresh live rig claims.