You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
SDK workers need to set (converted) query failures on to the new failure field on Add Failure to query result api#503, but making sure to keep setting error_message to the same value as failure.message.
SDK clients need to check for this QueryFailedFailure gRPC failure details on query response gRPC failure and if present and failure is present, need to set that as the cause of whatever is returned/thrown/raised today. For backwards compatibility, do not change the error that is used today though, only update the cause.
Per-SDK Tickets
Work cannot commence until temporalio/temporal#6947 is released in a testable dev server. Core-based SDKs don't technically need to wait on Core since it already accepts a full failure type, but in order to test that this works end to end, they need to be able to generate a query failure that is properly serialized, so Core is needed first.
Go - TODO after server released
Java - TODO after server released
Core - TODO after server released
TypeScript - TODO after Core
Python - TODO after Core
.NET - TODO after Core
Ruby - TODO after Core
PHP - TODO after Go
Temporal CLI - TODO after Go
The text was updated successfully, but these errors were encountered:
Describe the solution you'd like
failure
field on Add Failure to query result api#503, but making sure to keep settingerror_message
to the same value asfailure.message
.QueryFailedFailure
gRPC failure details on query response gRPC failure and if present and failure is present, need to set that as the cause of whatever is returned/thrown/raised today. For backwards compatibility, do not change the error that is used today though, only update the cause.Per-SDK Tickets
Work cannot commence until temporalio/temporal#6947 is released in a testable dev server. Core-based SDKs don't technically need to wait on Core since it already accepts a full failure type, but in order to test that this works end to end, they need to be able to generate a query failure that is properly serialized, so Core is needed first.
The text was updated successfully, but these errors were encountered: