FA-42068 / Listener lifecycle / Member archive

Paused debounce listener still delivers timer callbacks · case 03

Paused debounce listener still delivers timer callbacks; the returned lifecycle plan violates the stated transition contract.

Member previewVariant 3 · 3 implementations · 8 checks per implementation

Case contract

Plan a trailing debounce listener. Every accepted event replaces pending payload and restarts a timer at now+delay. A stale timer token cannot flush a newer payload. Completion flushes pending data only under flush policy; cancellation never flushes. At equality a current timer is due. Pause preserves payload while withholding timer delivery. For the maximum-wait projection, use the earlier of the quiet deadline now+delay and the fixed burst deadline burst_start+max_wait. Pause spans are disjoint half-open suspension intervals. Remaining debounce delay counts elapsed active time only, clipping spans to [timer_start,now]. Inputs are finite state snapshots, including transitional and stale states; output fields are the exact independent actions/metadata defined by the corrected expression table. Numeric fixture capacities and counts vary with N. Field definitions, each independently computed from the input snapshot: deadline = s['now']+s['delay'] if s['incoming'] is not None else s['due']; pending = s['incoming'] if s['incoming'] is not None else s['pending']; token = s['token']+int(s['incoming'] is not None); current_timer = s['fired']==s['token']; due = max(0,s['delay']-max(0,s['now']-s['timer_start']-sum(max(0,min(b,s['now'])-max(a,s['timer_start'])) for a,b in s['pause_spans']))); timer_flush = s['pending'] is not None and s['fired']==s['token'] and s['now']>=s['due'] and not s['cancel'] and not s['paused']; complete_flush = s['complete'] and s['flush'] and s['pending'] is not None and not s['cancel']; cancel_timer = s['cancel'] or s['complete']; cancel_payload = min(s['now']+s['delay'],s['burst_start']+s['max_wait']); schedule = s['incoming'] is not None and not s['cancel'] and not s['complete']

Why this case matters

Observer implementations need to preserve this state while subscriptions enter, execute, and leave their lifecycle.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
transition 0	`{"cancel_payload": 1, "cancel_timer": true, "complete_flush": false, "current_timer": false, "deadline": 15, "due": 2, "pending": "new", "schedule": false, "timer_flush": true, "token": 10}`	`{"cancel_payload": 1, "cancel_timer": true, "complete_flush": false, "current_timer": false, "deadline": 15, "due": 2, "pending": "new", "schedule": false, "timer_flush": false, "token": 10}`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.