Record failed Gateway event-read rollout and rollback evidence

This commit is contained in:
Joseph Doherty
2026-10-13 09:43:48 -04:00
parent cfd371ce18
commit 509114360d
@@ -23,3 +23,5 @@
- **2026-10-13 SQL event fault classification #42 merged (PR #43, main `3c4748d`, fix `3d289e7`).** SQL iteration, mapping and response delivery faults are separated; structured SQL error 681 and mapping defects return Internal, availability faults remain Unavailable, RPC/caller cancellation retain their status with constant safe detail. Reader/command/connection cleanup attempts all resources and preserves primary faults. Eighty new cases; affected 259 passed; full offline solution 1,895 passed /157 skipped /0 failed across three suites, exit 0. Independent review clear; merged tree equals tested branch; #42 closed. No deployment or live query recovery claim. #39 approved route probes show OPENQUERY can read all nine affected rows with NULL Priority/Severity/IsAlarm/offset, while local/four-part projections fail 681; full mapper projection and ReceivedTime UTC conversion remain unverified. Inner ID IN predicate was not honored; #39/#28 remain open.
- **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.