Command reference
oko failures defect
Records one kept failure as a defect now, whatever held it — one answered before the intake started among them — linking it to the defect an earlier failure of it holds.
Invocation#
oko failures defect ID [--json]Inputs and options#
- A failure's id is its session and the harness's call id joined by `:`, as `oko failures list` prints it.
- The register is OKO_CALL_FAILURES_REGISTER, else call-failures.json beside the defect register (`<defects>.call-failures.json` when OKO_DEFECT_REGISTER moves it); each call's whole output is kept, owner only, in the call-failures directory beside it (`oko failures location`).
Output and state effect#
- Prints `failed call <id> is defect <defect>`; --json prints the failure with its defect.
Refusals and safe exits#
- “failed call <id> is already linked to defect <defect>”; “failed call <id> was refused by a gate before its tool ran; a refusal is no product defect”.
- “failed call <id> was not recorded: <cause>”, with the cause a pass would keep: a declared answer, a command no catalog product installs, Stado's catalog or the defect register refusing.