docs(index): record historian cleanup status fix
This commit is contained in:
@@ -15,3 +15,5 @@
|
||||
- **2026-10-13 Docker auth documentation #37 merged (PR #38, main `eaeb4fe2`, docs `2bb2557`).** Runbook/CLAUDE/compose comment now match existing dashboard LDAP login and secrets-selected API-key mode; pepper must remain stable across recreation. Corrected Production reflection claim. Effective Compose values unchanged; independent review and diff check clear. #37 closed. #30 candidate Release publish/image prepared at code `9f711c1`, but isolated metadata smoke blocked by unresponsive local Docker; existing service not replaced, candidate cleanup remains unconfirmed. No unrelated services or daemon restarted.
|
||||
|
||||
- **2026-10-13 #30 local Docker rollout verified.** After Docker recovered, isolated candidate passed missing/existing metadata controls; candidate keys all retired and container removed. Normal Compose rolled code `9f711c1` image `sha256:8cc430d7…` into the local Gateway with matching server/SDK artifact hashes, unchanged effective environment and ApiKey auth, preserved data volume, retained rollback image and restricted stopped-service data backup. Live GetTagMetadata: nonexistent absent479ms, SysTimeSec present77ms; health200. Deployed test key independently verified revoked. #30 closed for this local deployment; no wonder-host rollout/remote execution. #29/#27 and OtOpcUa #694/#700 remain open.
|
||||
|
||||
- **2026-10-13 history cleanup #35 merged (PR #40, main `fb12572`, fix `b1343b8`).** Raw/materialized Raw/Aggregate/AtTime require native EndQuery success; refusal/missing status/fault/timeout marks sticky unsafe for existing pool discard and permit release. Original result/error and independent three-second uncancelled cleanup retained. New generated-gRPC lifecycle RED37fail/18pass; affected SDK84/84, Gateway134/134; full offline solution1,681passed/157skipped/0failed, three suites. Independent review clear; merged tree equals verified branch. #35 closed; #26 cancellation and #29 live history timeout remain open. No deployment or live cursor-leak claim.
|
||||
|
||||
Reference in New Issue
Block a user