27e3fc51ff
Two defects in tools/async_delegation.py: - _push_completion_event called _persist_completion unguarded before publishing onto completion_queue. One sqlite3 error (locked/full state.db) dropped the completion event, left the record parked on "finalizing" (a permanently leaked max_concurrent_children slot) and let recover_abandoned_delegations later rewrite a succeeded unit as "unknown". The write is now try/except: the failure is logged and the event is still delivered, so _finalize flips the status and frees the slot. A lost durable row is acceptable degradation; a lost result and a leaked slot are not. - _prune_completed_locked treated anything != "running" as finished, while the module's own _LIVE_STATES also names stalling/finalizing. A stalling record has no completed_at, so it sorted oldest and was the first eviction candidate once the retained cap overflowed; its late runner return then hit the missing-record path and the real result was dropped. The predicate is now `status not in _LIVE_STATES`. Slim redo of #76606 (earliest fix) and #112031: the converge/shield/ delete-row machinery both PRs built around the write is dropped as defense-in-depth; the two core hunks are ported as-is. Fixes #76605 Fixes #112030 Co-authored-by: luckystar2026 <1393268817@qq.com>
3 lines
40 B
Plaintext
3 lines
40 B
Plaintext
luckystar2026
|
|
# PR #112031 author email
|