Maxim Fateev
Maxim Fateev
We should support loading a message from a binary file and specifying the encoding through the command line. This would support any future message format.
This might be useful: https://medium.com/swlh/unit-testing-cli-programs-in-go-6275c85af2e7
Running` go mod vendor` before make fixes it.
Also had to install the linter: `brew install golangci/tap/golangci-lint`
Ideally, the same API can be reused to complete the workflow asynchronously. This would allow workflows to be implemented fully async without tying up a thread when a workflow is...
This requires a server-side change. The service must mark reapplied signals to distinguish them from the newly received signals.
> The failure is retryable. This call should IMHO be a noop to avoid wasting an activity attempt without having a chance to get started and triggering the next retry...
We already have two samples that cover async activity execution: https://github.com/temporalio/samples-go/tree/main/splitmerge-future https://github.com/temporalio/samples-go/tree/main/splitmerge-selector
@WorkflowInterface defines a workflow type. There is no "Retryable" workflow type to register.
The WorkflowClient.newWorkflowStub call [validates](https://github.com/temporalio/sdk-java/blob/201240a4f1075a48e23a3af17fd11a6d1c89bcd6/temporal-sdk/src/main/java/io/temporal/client/WorkflowClientInternalImpl.java#L175) that only methods that are annotated with signal/update/query are allowed at the interface.