Maxim Fateev
Maxim Fateev
Sorry, I'm still confused. Could you explain why exactly my proposal doesn't solve your problem?
Sorry, but my proposal solves your issue. It will register B::foo and C::foo, but is not going to register A::foo. What do I miss?
Here is my proposal (not yet implemented) that I put at the beginning of this thread: Treat all base interfaces as non activity interfaces. Only the interfaces that an activity...
Have you changed the code after the workflow has started? Could you reproduce the problem with the freshly created workflows? If you can, post here the instructions on how to...
This works as designed. The NonDeterministicWorkflowPolicy is associated to a specific workflow type. As you are starting workflow with a different type the worker rejects the workflow it doesn't support....
The root cause is the unit test time skipping logic together with a large workflow timeout. The time skipping automatically moves time to the next task in a timer queue....
Another request is to be able to specify logging behavior per specific error. For example we recommend failing an activity constantly to implement polling. And in this case the error...
My current view is that we should add a flag (or separate method for creation) to allow creating an ApplicationFailure that is not logged. All other failures are logged.
Such refactoring should keep the strongly typed way to call this method the current implementation provides.
The relevant Java PR: https://github.com/temporalio/sdk-java/pull/441