cadence-java-client
cadence-java-client copied to clipboard
Java framework for Cadence Workflow Service
`com.uber.cadence.internal.external.ManualActivityCompletionClientImpl#fail` method does not set activityId on the instance of `RespondActivityTaskFailedByIDRequest`, which causes `com.uber.cadence.internal.testservice.ActivityId#ActivityId(java.lang.String, com.uber.cadence.WorkflowExecution, java.lang.String)` constructor to throw `NullPointerException`
Today the only way to use the archived history is to parse the history events, which is not a reliable way to use it.
We see NPE in ReplayDecider with line: decisionTask.getHistory().getEvents().get(0).getWorkflowExecutionStartedEventAttributes(); In ReplayDecisionTaskHandler, we have special handling for sticky decision task that has a partial history. But we do not check the returned...
When executing the tests in https://github.com/uber/cadence-java-samples (e.g. [HelloAsyncLambdaTest](https://github.com/uber/cadence-java-samples/blob/master/src/test/java/com/uber/cadence/samples/hello/HelloAsyncLambdaTest.java)) most of them log an exception even though the test itself succeeds. It seems that DecisionTask StartToCloseTimeout is being executed even after...
I used the example at https://github.com/uber/cadence-java-samples/blob/master/src/main/java/com/uber/cadence/samples/hello/HelloActivity.java to try implement it with a Spring boot application. I'm getting this following error: ``` java.lang.IllegalArgumentException: interface com.kloudlearn.newsfeed.workflow.HelloActivity$GreetingWorkflow is not visible from class loader...
While enabling a ContextPropagators to include MDC in logging I found that it did not work during my tests. After some investigation I found out that the [TestWorkflowEnvironmentInternal](https://github.com/uber/cadence-java-client/blob/master/src/main/java/com/uber/cadence/internal/sync/TestWorkflowEnvironmentInternal.java#L166) calls `WorkflowClientOptions.newBuilder(options)`....
https://github.com/uber/cadence-java-client/blob/229dd2c8604421ef081afca57907ac0405d38cf9/build.gradle#L60 The latest version is 0.10.0
At about line 429 of com.uber.cadence.internal.sync.WorkflowStubImpl.java, the building of the QueryWorkflowParameters object doesn't set the run id if present: ``` QueryWorkflowParameters p = new QueryWorkflowParameters(); p.setInput(dataConverter.toData(args)); p.setQueryType(queryType); p.setWorkflowId(execution.get().getWorkflowId()); p.setQueryRejectCondition(queryRejectCondition); ```...
Hi all :DD! I have a question regarding the `doNotRetry` parameter of MethodRetry annotation. As the name suggests, I would expect this parameter accepts an exception or a list of...
https://github.com/uber/cadence-java-client/blob/14e523a7a0eae4b8ce671c07284da1c66261287c/src/main/java/com/uber/cadence/internal/sync/ActivityTaskImpl.java#L57 In Cadence server, timestamp is based on nanoSecond, not microSecond.