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
Currently if the user forgets to set a result ticket for a one-shot table rpc, they get an awfully obscure error:
grpc-api_1 | 2021-08-31T02:02:55.007Z | c-nio-worker-ELG-3-2 | ERROR | .g.t.TableServiceGrpcImpl | io.grpc.StatusRuntimeException: FAILED_PRECONDITION: Cannot parse ticket: found 0x (hex)
grpc-api_1 | at io.grpc.Status.asRuntimeException(Status.java:535)
grpc-api_1 | at io.grpc.protobuf.StatusProto.toStatusRuntimeException(StatusProto.java:52)
grpc-api_1 | at io.deephaven.grpc_api.util.Exceptions.statusRuntimeException(Exceptions.java:15)
grpc-api_1 | at io.deephaven.grpc_api.util.ExportTicketHelper.ticketToExportIdInternal(ExportTicketHelper.java:267)
grpc-api_1 | at io.deephaven.grpc_api.util.ExportTicketHelper.ticketToExportId(ExportTicketHelper.java:66)
grpc-api_1 | at io.deephaven.grpc_api.session.SessionState.newExport(SessionState.java:330)
grpc-api_1 | at io.deephaven.grpc_api.table.TableServiceGrpcImpl.lambda$oneShotOperationWrapper$15(TableServiceGrpcImpl.java:406)
grpc-api_1 | at io.deephaven.grpc_api.util.GrpcUtil.rpcWrapper(GrpcUtil.java:33)
grpc-api_1 | at io.deephaven.grpc_api.table.TableServiceGrpcImpl.oneShotOperationWrapper(TableServiceGrpcImpl.java:393)
grpc-api_1 | at io.deephaven.grpc_api.table.TableServiceGrpcImpl.fetchTable(TableServiceGrpcImpl.java:252)
[ ... ]
The batch operation allows the user to do this on purpose, so that they may create what Devin calls "tainted" nodes in the DAG that cannot guaranteed to be recovered. This should just be a better error message "hey, I can do this, but don't you want me to write it some place?".
The text was updated successfully, but these errors were encountered:
Currently if the user forgets to set a result ticket for a one-shot table rpc, they get an awfully obscure error:
The batch operation allows the user to do this on purpose, so that they may create what Devin calls "tainted" nodes in the DAG that cannot guaranteed to be recovered. This should just be a better error message "hey, I can do this, but don't you want me to write it some place?".
The text was updated successfully, but these errors were encountered: