Repository navigation
Bug: engine-toggle-permanent-config-fault-logs-every-poll #948
Description
Activity
Restoring sections dropped by the promotion tooling.
Suspected Cause / Notes
The configuration fault is cached in
AsyncLazy, and the coordinator has no back-off or reset policy, so each cache-missgetPressedpoll re-primes and logs again. A stale marker intermittently suppressed the repeats until #944 removed it. This is a retry-policy decision, not a correctness defect in #944. Source: #944 spec, Rollout and Follow-up item 2.Proposed Fix / Validation Ideas
- Decide on a policy: back off re-primes after a fault, log only on a state change, or call
ResetConfigAsyncLazyto recover. - Deterministic test: under a fake
TimeProvider, N polls against a cached fault produce a bounded number of log entries. - Sequence this after Bug: engine-toggle-prime-marker-registration-races-removal #944 merges.
- Decide on a policy: back off re-primes after a fault, log only on a state change, or call
Summary
When the engine configuration load faults permanently,
AsyncLazycaches the fault, so every cache-missgetPressedpoll re-primes and logs the same error again. A stale marker used to suppress repeats intermittently. Once #944 removes the stale marker, every poll that reachesStartPrimeIfNeededlogs.Environment
TaskMaster/Ribbon/EngineToggleStateCoordinator.cs, and the configurationAsyncLazywithResetConfigAsyncLazySteps to Reproduce
getPressed.TaskMaster\bin\Debug\logs\debug_<date>.log).Expected Behavior
A permanent configuration fault is logged once, or at a bounded rate, and recovery is either explicit or backed off.
Actual Behavior
After #944, one error is logged per cache-miss poll, without bound.
Logs / Screenshots
Impact / Severity
Source
From: docs/features/potential/2026-09-30-engine-toggle-permanent-config-fault-logs-every-poll.md