Roey Berman
Roey Berman
This is done in Java SDK, could lead to significant memory savings in some cases.
Currently it's only possible to configure static HTTP headers on the Client, we need to add a way to specify dynamic ones. A typical use case for this would be...
E.g. you might try to cancel the child workflow in a signal handler in which case the child workflow may or may not have been started as far as core...
In #202 we tied the logging of retries to the retry config's `max_retries`. I feel like a better experience would be to start logging immediately when failed to connect to...
Might be nice to create a combined register & submit convenience function for all these. _Originally posted by @Sushisource in https://github.com/temporalio/sdk-core/pull/163#r685379701_
Yeah so this can't stay as-is then, clearly. It's still a nice thing to be able to detect, though. Maybe we can upgrade this to also check that there is...
When compiling the node SDK, I got the following error with an M1 CPU. ``` npm ERR! error: failed to run custom build command for `temporal-sdk-core v0.1.0 (/Users/bergundy/temporal/sdk-node/packages/worker/native/sdk-core)` npm ERR!...
We have these 2 concept pages in the docs that contains duplicate and sometimes outdated information relative to the source. Docs: - https://docs.temporal.io/references/events - https://docs.temporal.io/references/commands Source: - https://github.com/temporalio/api/blob/master/temporal/api/history/v1/message.proto - https://github.com/temporalio/api/blob/master/temporal/api/command/v1/message.proto...
As discussed on slack with @mfateev and @Spikhalskiy we'd like to apply a semver incompatible versioning scheme for SDKs. Temporal SDKs can break compatibility in either public APIs or history...