Dmitry Spikhalsky

Workflow should have an access to an activity id of the activity it scheduled

3

**Is your feature request related to a problem? Please describe.** There is a scenario when a workflow needs to cancel an activity if it gets an external signal. For example,...

## Actual Behavior Currently, Test Server never paginates the history and returns it always in one chunk. This makes the SDK internals that are getting triggered only if the server...

## Expected Behavior Temporal JavaSDK explicitly supports the idea of fixing a bug leading to an exception in the workflow implementation. Workflow can throw a non `ApplicationFailure` exception and such...

## Expected Behavior ActivityStubs should be created for each workflow instance / execution separately. But if somebody uses Dependency Injection frameworks with Temporal it's very easy to misconfigure the wiring...

Temporal strives to provide reasonable defaults for Retry options. Also, we try to not expose `RpcRetryOptions` because of how easy they are to misconfigure. But in some cases, our default...

**Is your feature request related to a problem? Please describe.** We don't report the completion of workflows during replays. This is a good default behavior for these main completion counters,...

Temporal JavaSDK has an untyped `WorkflowStub` that is bound to a specific method invocation (workflow method), while a currently existing ActivityStub is bound to the AcitivityInterface and not to the...

GrpcRetryer retry method by its nature is expected to throw InterruptedException because they 1. perform waiting on a timer 2. could get an Interrupted flag from GRPC calls with a...

**Describe the bug** This problem is related to the main bug submitted as #3291. After getting the described error it becomes visible in the trace, as can be seen in...

Python 3.14 support

3

Python 3.14 was released, but ruptures v1.1.10 requires Python =3.9. Please make a py 3.14-compatible release.