Maxim Fateev
Maxim Fateev
We are going to introduce support for something like SignalWithReply that is going to block until the signal handler returns. I'll update this issue as soon as it is added.
We are actively working on the synchronous update feature. [This stack answer ](https://stackoverflow.com/questions/57197874/how-to-model-a-workflow-that-has-to-return-a-result-in-one-of-the-steps)outlines the current workarounds.
I think sending signal to itself is an exception which is not worth optimizing. So just allowing own ID in the SignalExternalWorkflows should be enough IMHO.
I would also support AddFuture(f, nil) to not require the function if future is not read.
The first stack trace appears incomplete. Could you post the complete chain? The second happens when a decision task takes longer than the decision task timeout. Do you do any...
This doesn't make sense as no decision task should be running while workflow is kicked out of the cache. The only possibility is that there is a race condition between...
Add defer into the main workflow function. It is always called even when a workflow cleaned up from worker memory.
Consider merging Client.StartWorkflow and ExecuteWorkflow as ExecuteWorkflow returns a future that might be used to get runID and workflowID and waiting for completion through Get is optional.
Fix: https://github.com/uber/cadence-java-client/pull/381
Should we use[ Multi-Release Jars ](http://openjdk.java.net/jeps/238)to support multiple Java versions?