mirror of
https://github.com/stablyai/orca.git
synced 2026-10-24 08:03:58 +00:00
Neil
80cc71714b
Regression from the previous commit. Keeping the stale in-flight marker across resetTarget stops overlap, but it also swallows the new connection's result: the new apply reports 'unplaced', hits the guard because the superseded apply still owns the marker, and the superseded callback then exits on its stale generation without scheduling. Nothing replayed the dropped report, so no chain started - the retry silently never ran for that connection. A blocked unplaced report is now recorded, and the marker's owner replays it on release. Only the stale path reaches the finally still owning the marker, so the normal path - which released early and scheduled its own outcome - cannot replay twice.