WaitExecution operation validation

[George Gensure]

Comments for Execution::WaitExecution fail to describe the response in the case of an unknown/malformed operation name:

  // Wait for an execution operation to complete. When the client initially
  // makes the request, the server immediately responds with the current status
  // of the execution. The server will leave the request stream open until the
  // 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.

A forgetful service may lose the tracking for an operation name that was previously returned by Execute.

What do folks think of adding NOT_FOUND (and perhaps INVALID_ARGUMENT for malformed names) to the documentation here in possible errors as something that indicates that the clients may interpret as an opportunity to restart an Execute?

Regards,

-George

[Ed Schouten]

Returning NOT_FOUND sounds good to me. Buildbarn already does that. Why the special case for malformed names? Can’t we let that return NOT_FOUND as well?

Ed

--
You received this message because you are subscribed to the Google Groups "Remote Execution APIs Working Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to remote-execution...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/remote-execution-apis/CALa2%2BBzVHFD6h_Vrm-qhVBnY5%2BfueexvGdeXvhZm1BfNpNqrMg%40mail.gmail.com.

--

Ed Schouten <e...@nuxi.nl>