microsoft / microsoft/durabletask-dotnet
Semantics of CallSubOrchestrator in SDK is different from Core
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 193
- Forks
- 60
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 4
Description
In error handling tests (e.g. NotFoundErrorsAreNotRetried) calling Bogus sub-orchestrator results in failure. In Core the same results in not completed task and increasing backoff of the dispatcher (questionable to say the least given that no timeout or cancellation option is provided).
Was this change of semantics intentional?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the NotFoundErrorsAreNotRetried error-handling test and compare the CallSubOrchestrator behavior in the SDK with the corresponding Core behavior. Trace how the dispatcher handles the failed or incomplete task. Done means the semantic difference is explained and the agreed behavior is captured by aligned tests or documentation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100