fix: keep bridge readiness stable during live state updates

Wuast94 commented

2026-10-13 00:41:51 +02:00

Owner

Normal WLED state updates invalidated whole-Bridge readiness until each entity and availability ACK, causing 117/844 production probes to return 503 despite connected HA/MQTT. Readiness now retains confirmed initialization for the current HA generation during state/attribute writes. Every write and latest-revision recovery remains independent and ACK-bound; new entities, configuration changes, restore/reconnect and cleanup still invalidate initialization.

Three real HA/HTTP regressions cover held identical writes, rejection/stale ACK/recovery, new entities, configuration/reconnect/offline and successful probes with one async worker and held CPU capacity. Existing generation watchers reset on a new reconcile attempt. The previously failing resize fixture captures visible marker geometry atomically while preserving all assertions.

Validation: reproduced the original 503, targeted connector/HTTP/browser tests passed, then full just gate exit 0 (82 Rust tests, existing frontend/tooling suites, strict Clippy/deny/machete). Shared S3 cache verified without backend errors. JSON formats, automations, production resources and image namespace unchanged. Native CI/candidate acceptance required before merge; release/SBOM and primary kube GitOps follow.

Normal WLED state updates invalidated whole-Bridge readiness until each entity and availability ACK, causing 117/844 production probes to return 503 despite connected HA/MQTT. Readiness now retains confirmed initialization for the current HA generation during state/attribute writes. Every write and latest-revision recovery remains independent and ACK-bound; new entities, configuration changes, restore/reconnect and cleanup still invalidate initialization. Three real HA/HTTP regressions cover held identical writes, rejection/stale ACK/recovery, new entities, configuration/reconnect/offline and successful probes with one async worker and held CPU capacity. Existing generation watchers reset on a new reconcile attempt. The previously failing resize fixture captures visible marker geometry atomically while preserving all assertions. Validation: reproduced the original 503, targeted connector/HTTP/browser tests passed, then full just gate exit 0 (82 Rust tests, existing frontend/tooling suites, strict Clippy/deny/machete). Shared S3 cache verified without backend errors. JSON formats, automations, production resources and image namespace unchanged. Native CI/candidate acceptance required before merge; release/SBOM and primary kube GitOps follow.

Wuast94 added 2 commits

2026-10-13 00:41:51 +02:00

test: observe timeline marker geometry atomically on resize eec2998c03

fix: keep bridge readiness stable during live state updates

CI / Quality (pull_request) Successful in 4m13s

Details

CI / Build production (pull_request) Has been cancelled

Details

e7db56f193

Wuast94 added 1 commit

2026-10-13 00:43:02 +02:00

docs: register verified ab2rss Rust migration [skip ci] 6526eeda9f