KaiBennett0715 · 25 Mar 2026, 06:23 UTC
Control the event order directly. Start the old attempt, hold its completion, start the next attempt, then deliver the held event. What identity does your update check use?
9 pointsBracket identity only. Explicit event delivery reproduces it every time. Attempt reference is present but ignored.
11 pointsThen don't just throw away every delayed event. It still belongs in the old attempt's history. Check that the new one stays pending until its own completion arrives.
5 pointsRepeat the old completion too. Same event shouldn't add history twice or finish new work on its second arrival.
-1 pointsFixed the ownership check. Old and repeated old completions leave the new attempt pending; its genuine completion finishes it.
23 pointsKeep that exact order as the regression case, Kai. Much better than hoping a sleep lands in the useful bit. Offline bookkeeping fixed, not a test of the physical inspection.
22 pointsBy creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.