From 068363a3625e166056c155f6441cfb35ca8dfbf2 Mon Sep 17 00:00:00 2001 From: George Gensure Date: Tue, 27 Jun 2023 16:17:05 -0400 Subject: [PATCH] Document NOT_FOUND Execution error reporting (#259) --- build/bazel/remote/execution/v2/remote_execution.proto | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/build/bazel/remote/execution/v2/remote_execution.proto b/build/bazel/remote/execution/v2/remote_execution.proto index 0800ede2..b7ae5bc4 100644 --- a/build/bazel/remote/execution/v2/remote_execution.proto +++ b/build/bazel/remote/execution/v2/remote_execution.proto @@ -125,6 +125,14 @@ service Execution { // operation completes, and then respond with the completed operation. The // server MAY choose to stream additional updates as execution progresses, // such as to provide an update as to the state of the execution. + // + // In addition to the cases describe for Execute, the WaitExecution method + // may fail as follows: + // + // * `NOT_FOUND`: The operation no longer exists due to any of a transient + // condition, an unknown operation name, or if the server implements the + // Operations API DeleteOperation method and it was called for the current + // execution. The client should call `Execute` to retry. rpc WaitExecution(WaitExecutionRequest) returns (stream google.longrunning.Operation) { option (google.api.http) = { post: "/v2/{name=operations/**}:waitExecution" body: "*" }; }