Terminating a program that utilizes durable task without launching dapr causes the program to hang

[RyanLettieri]

This issue stems from an issue reported by a user in the dapr .NET SDK repository here: dapr/dotnet-sdk#1191

To reproduce the issue:

Pull down the dapr dotnet-sdk and navigate to the following directory: https://github.com/dapr/dotnet-sdk/tree/master/examples/Workflow/WorkflowConsoleApp

Run dotnet run and observe that the program starts.

Attempt to cancel the program with CTRL+C

Notice that the program never actually closes and the following logs are displayed endlessly:

...
info: Microsoft.DurableTask[3]
      The gRPC server for Durable Task gRPC worker is unavailable. Will continue retrying.
info: Microsoft.DurableTask[3]
      The gRPC server for Durable Task gRPC worker is unavailable. Will continue retrying.
info: Microsoft.DurableTask[3]
      The gRPC server for Durable Task gRPC worker is unavailable. Will continue retrying.
...

[jviau]

I am not familiar with how dapr process works, but looks like the CTRL+C is not propagated to the durabletask process. CTRL+C there will terminate the program. This loop will exit when the host cancellation token source is tripped, and is tripped when CTRL+C (or any other exit signal) is sent.

https://github.com/microsoft/durabletask-dotnet/blob/main/src/Worker/Grpc/GrpcDurableTaskWorker.Processor.cs#L64