Skip to content

Commit cc420b8

Browse files
YunchuWangCopilot
andcommitted
Make abandon comment self-contained (drop Python reference)
The prior note referenced durabletask-python behavior, which is fragile: the Python single-work-item support lives on an unmerged fork PR and its details can drift. Trim the comment to the JS-only rationale for the no-op abandon on the single-work-item host path. Comment-only change. Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
1 parent fa2a17c commit cc420b8

1 file changed

Lines changed: 1 addition & 3 deletions

File tree

packages/durabletask-js/src/worker/task-hub-grpc-worker.ts

Lines changed: 1 addition & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1270,9 +1270,7 @@ class CapturingSidecarStub {
12701270
// Abandon is a no-op for the single-work-item host path: the version-mismatch abandon branch
12711271
// in _executeOrchestratorInternal calls this, but processOrchestratorRequest only surfaces a
12721272
// completion response. Record it so the caller can distinguish an abandoned work item from a
1273-
// genuine "no response produced" failure. This single-work-item helper is JS-specific for the
1274-
// Azure Functions host integration; durabletask-python has no equivalent helper, and its
1275-
// worker-loop abandon hands the item back over a real sidecar stub rather than no-opping here.
1273+
// genuine "no response produced" failure.
12761274
this.abandoned = true;
12771275
callback(null, new Empty());
12781276
}

0 commit comments

Comments
 (0)