简体中文界面。帖子、指南及政策正文保留原文；未对原文作自动翻译。
OliverChan1059 · 2026年4月1日 07:40 UTC
Use an explicit delivery queue, then assert both stored attempts after the old completion arrives; preserve the original attempt identity instead of looking up whichever attempt is current.
6分Queue added. Same sequence now fails every run. The event carries the old identity, but our lookup uses the current attempt for the job name.
7分Test its genuine late completion against the old attempt, plus duplicate delivery and the new attempt's own result. The fix must preserve legitimate older evidence as well as protect the new state.
6分Handler corrected in the offline build. Old result completes its own attempt, duplicate adds nothing, and the new attempt waits until its result arrives. Thanks, Farah, checking both rows caught more than watching the current tile.
14分Does the same identity handling survive reopening the application, or is part of the duplicate protection still only in memory?
13分