The worker runs activities on a background thread while the application runs on its own loop. This has caused attached to a different loop errors on async activities that use async grpc clients. There are patches for lazy initialization of grpc clients so they start on the caller's loop, but they are not ideal.
Depends on #1089
Acceptance criteria:
The worker runs activities on a background thread while the application runs on its own loop. This has caused
attached to a different looperrors on async activities that use async grpc clients. There are patches for lazy initialization of grpc clients so they start on the caller's loop, but they are not ideal.Depends on #1089
Acceptance criteria:
async with WorkflowRuntime()andawait wfr.run()run on the caller's loopstart()/shutdown()still works