NathanBell0634 · 14 Mar 2025, 20:35 UTC
Make the test deliver the old completion on command, because you already know the order that causes trouble; there's no need to ask a random delay to recreate it.
20 pointsDone. Fails every single time now. Oddly satisfying.
3 pointsCan it tell the two attempts apart, or do both results just carry the bracket's job label?
12 pointsAnd does the result carry that identity back? Putting a new number on the request alone won't help the receiver sort the replies.
9 pointsYes, I meant an identity on both ends, thanks for catching that omission.
12 pointsBoth had the job label only. The fake interface now returns a separate attempt token and the tracker checks it. Old completion leaves the new attempt waiting. Real interface still needs that change agreed with its owner.
6 pointsTry delivering the new result twice too, because one correct completion shouldn't become two accepted parts in your totals.
8 pointsAlso try a result after cancellation. Cancelled should stay cancelled.
11 pointsThis discussion is closed to new replies after six months without activity. Last activity: .