Roey Berman

In Python you can start a test env from a client. We should support instantiation from a `Connection`. I would rather also have the worker be powered by the same...

@bkniffler AFAICT you still need the sdk’s webpack bundler after you generate your js bundle with esbuild. How are you instantiating your worker?

This is a known limitation of sinks. As you pointed out, the data is transferred over `postMessage` from a worker thread to the main Node.js thread which uses the structured...

> This is no longer pertinent, since SDK tracing support is being removed. Note this is true for internal SDK traces, not user traces. I reopened this issue.

Use `workflowInfo().unsafe.now()`

I'd write this workflow as shown below. Does this look better to you? ```ts export async function myWorkflow() { let internalCount = 0; for (;;) { try { await CancellationScope.cancellable(async...

Or with a generator: ```ts export async function myWorkflow() { async function* compute(internalCount = 0) { for (;;) { try { yield ++internalCount; await CancellationScope.cancellable(async () => { const scope...

I think technically you can implement async generator support for cancellation scopes with something like this: ```ts import { CancellationScope } from '@temporalio/workflow'; import { storage } from '@temporalio/workflow/lib/cancellation-scope'; export...

You should read the implementation of `CancellationScope`, it's fairly straightforward: https://github.com/temporalio/sdk-typescript/blob/main/packages/workflow/src/cancellation-scope.ts. The heavy lifting is done by node's `AsyncLocalStorage`. You might want to create scopes around each "sleep" or other...

@Irvenae I'm curious what you ended up doing with this.