You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Is Task.WhenEach/IAsyncEnumerable properly supported / safe to use in Durable Orchestrators
#3499
Task.WhenEach returns an IAsyncEnumerable<Task> and yields tasks in completion order. Task.WhenAll and Task.WhenAny are known to be safe and been around for long time.
However is Task.WhenEach considered fine to be used within the orchestrator or does the IAsyncEnumerable have issues? And if so are samples on how to do so properly, and if not will the use of it be expected in future updates?
Asking this as there are cases where currently Task.WhenAny patterns are done and the await foreach(var t in Task.WhenEach(tasks) would make it more cleaner and simplified. And I did a test, and maybe I am doing something wrong or need to configure, and all the tasks have completed but the orchestrator does not seem to be reported to be ever finished. Which would indicate something with the hub history/instances not proper, but would not be first case that something might have to be done differently with a feature.
Note: This is separate from the IAsyncEnumerable support returned activities or so.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Task.WhenEachreturns anIAsyncEnumerable<Task>and yields tasks in completion order.Task.WhenAllandTask.WhenAnyare known to be safe and been around for long time.However is
Task.WhenEachconsidered fine to be used within the orchestrator or does the IAsyncEnumerable have issues? And if so are samples on how to do so properly, and if not will the use of it be expected in future updates?Asking this as there are cases where currently
Task.WhenAnypatterns are done and theawait foreach(var t in Task.WhenEach(tasks)would make it more cleaner and simplified. And I did a test, and maybe I am doing something wrong or need to configure, and all the tasks have completed but the orchestrator does not seem to be reported to be ever finished. Which would indicate something with the hub history/instances not proper, but would not be first case that something might have to be done differently with a feature.Note: This is separate from the
IAsyncEnumerablesupport returned activities or so.All reactions