Dmitry Spikhalsky

As we discussed with @mmcshane, `createNamespace`, `listNamespaces` and other namespace-focused APIs read and write directly to the database, while other APIs (like activity/workflow worker long polls) use a namespace cache....

Confirm that the workaround posted by @appdirect-kasidit works. It will include sources from all the submodules though, even if the module is not configured in ``` dependencies { jacocoAggregation project(':')...

@niegus We typically don't provide ETAs for feature requests. Contributions are welcomed, this is a great starter issue.

I think to have it consistent, it should be `doNotRetryPedicate` and retry doesn't happen if `ex.getErrorType in retryOptions.getDoNotRetry() || doNotRetryPedicate(ex)`. But I'm getting back the comment about the great starter...

There is a report that the similar exception appears in java-sdk 1.8.0 using test-server. ``` java.lang.ArithmeticException: Duration of this magnitude not supported at com.uber.m3.util.Duration.checkMultiplicationLongOverflow(Duration.java:340) at com.uber.m3.util.Duration.ofMillis(Duration.java:109) at io.temporal.internal.common.ProtobufTimeUtils.toM3Duration(ProtobufTimeUtils.java:49) at io.temporal.internal.replay.ReplayWorkflowExecutor.completeWorkflow(ReplayWorkflowExecutor.java:109)...

Most likely directly related to #1346 and the structure of the current workflow task execution flow

@neshield From what I see from Step 4 logs, gRPC actually tries to establish a new connection (as it should) and it fails, which causes the request to fail: ```...

Related to #391 and shows that the #391 issue wasn't addressed by #531

The result depends on if workflow run times out before workflow task heartbeat (local activity is used in that test) is received by the server or after.

Assigning low priority. Test Server is intended for testing Workflow implementations, full on-par support of all administrative endpoints is not really a goal. Workflow logic shouldn’t trigger listopenworkflowexecutions, it's an...