简体中文界面。帖子、指南及政策正文保留原文；未对原文作自动翻译。
SamAli0246 · 2026年2月14日 03:35 UTC
Can your test retain the first completion in a queue, start the second attempt, then release that saved event when you choose? That would remove the timing lottery.
20分Developer can control that boundary. We are using the retained messages with their actual attempt references.
14分I'd also send the new completion twice. Otherwise you fix yesterday's message and still get two rows from today's one. The screen can look perfectly sensible while the report is a mess.
13分Give the test an expected accepted-item total and expected attempt history as well, so it checks what the next person reads rather than only whether a handler returned normally.
-7分Explicit queue reproduces the bug every time. Old completion closes the new attempt because matching uses the sample only.
8分So the sample identity is being asked to identify an attempt too. Can the state update require the current attempt reference before it marks anything complete?
4分Corrected there. Old completion no longer closes the new attempt. Current duplicate adds no second result row.
23分Decent. Keep those exact event orders in the regression set, including the downstream count Toby mentioned. Much easier to explain than 'try it until the bad thing happens'.
14分此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .