Chad Retz
Chad Retz
Yes, there are discussions to be had on whether the performance difference is worth it. I am gathering feedback from others.
Yes, this issue is blocked on https://github.com/temporalio/temporal/issues/38 or similar since we share https://github.com/temporalio/api-go. I will leave this open pending that issue.
The best approach for this may be to go ahead and support #543 so a catch-all workflow implementation can be written
The first getClusterInfo fails after restarting a temporalite cluster in a multi cluster environment
This does not seem related to Temporalite specifically, but rather the Java SDK. To clarify @neshield, are you saying that your same client isn't able to successful call after server...
> Under test, it throws PanicError in the logs when the code is executed multiple times (retries) but the test succeeds with exit code 0. IIUC the original issue correctly,...
> So you imply we should check the invocation count assertions via env.GetWorkflowError()? I thought that's what env.AssertExpectations(t) is for. My mistake, yes, you can and should use that function...
> invocation count assertions should probably best be avoided Concur. And on a general best-practices note, the ease of adding counts can tempt one to overly assert counts leading to...
@dorsec - I am assuming you're talking about `testsuite.TestWorkflowEnvironment.ExecuteWorkflow` and not `mocks.Client.ExecuteWorkflow`, correct? Can you provide more information on how you are using the context to `Client.ExecuteWorkflow`? The context is...
> The code in my workflows/activities may rely on context information (e.g. user ID). But you can't inject user values into the context that is given to your workflow (unless...
This may be fixed by #779, but we will have to test after that is merged.