Skip to content

Commit 3f8e1cb

Browse files
committed
refactor(server): clarify the missing worktree guard
1 parent c5ac414 commit 3f8e1cb

1 file changed

Lines changed: 2 additions & 4 deletions

File tree

‎apps/server/src/orchestration-v2/Orchestrator.ts‎

Lines changed: 2 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -5380,10 +5380,8 @@ const makeOrchestrator = Effect.fn("orchestrationV2.Orchestrator.layer")(functio
53805380
(candidate) => candidate.id === projection.thread.activeProviderThreadId,
53815381
);
53825382
const activeRun = projection.runs.find(isBlockingRun);
5383-
// A message can arrive after worktree setup failed or was stopped without a
5384-
// worktree, whether it was queued during setup or sent fresh afterwards. It
5385-
// waits, held, like the messages queued before the failure, instead of
5386-
// starting in the project checkout.
5383+
// Messages after failed or stopped worktree setup must wait for a worktree,
5384+
// rather than start in the project checkout.
53875385
const latestRun = latestExecutedRun(projection.runs);
53885386
const worktreeMissingRun =
53895387
activeRun === undefined &&

0 commit comments

Comments
 (0)