feat: idempotency key, the INTERRUPTED phase, and a real-hub skew suite
The hub now takes an idempotency key and reports INTERRUPTED for a run its process did not survive, so the client exposes both. The real-hub suite gained the cross-language half of the idempotency guard: a repeated key has to answer with the first run's outputs, which only a real hub can prove. Signed-off-by: flemming-it <sf@flemming.it>
This commit is contained in:
parent
b6c6cc8295
commit
0db793494d
4 changed files with 39 additions and 2 deletions
|
|
@ -439,6 +439,10 @@ message InvocationStatus {
|
|||
SUCCEEDED = 3;
|
||||
FAILED = 4;
|
||||
CANCELLED = 5;
|
||||
// The hub went down while this run was executing (added in hub
|
||||
// 0.25). The run did not finish and did not fail on its own; a
|
||||
// caller that owns the work decides whether to submit it again.
|
||||
INTERRUPTED = 6;
|
||||
}
|
||||
Phase phase = 1;
|
||||
// Step currently executing (RUNNING), empty otherwise.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue