Command reference
oko contributions pending
Lists the records report would send, without sending them: the work.accepted event of each task the task map settles as done that the ledger holds no standing acceptance of, with the task as its subject and the judge's vote, and the retraction of each standing acceptance whose task the operator or a later defect reopened.
Invocation#
oko contributions pending [--ledger URL] [--json]Inputs and options#
- The task map's tasks with their status. Nothing judges a prompt by its words; only the verdict on its work counts.
- With a ledger named, the ledger is asked what it holds. Each task's history is read from what the ledger holds, one request per generation: a task's first acceptance is the event `<task>`, its retraction `<task>#retracted`, and the acceptance after a retraction `<task>#<n>` for the n-th, retracted as `<task>#<n>#retracted`. A done task with no standing acceptance owes its next acceptance; a task that is no longer done and whose acceptance stands owes its retraction. With none named, each done task's first acceptance is listed and no retraction is known. --ledger URL names the contribution ledger (compute.wisent.com); without it, OKO_CONTRIBUTION_LEDGER_URL does. The bearer is read from the item playing oko-contribution-ledger under consumer oko-contribution-client.
Output and state effect#
- Prints `<event> <kind> <member> <time>` per acceptance owed and `<retraction> retracts <acceptance> <time>: <cause>` per retraction owed, then `<task> not reported: <reason>` for each done task whose verdict states no settled time (no time is invented for it), then `<n> event(s) owed, <m> with no settled time; <k> acceptance(s) the ledger already holds` (or that no ledger was named). --json prints `{ledger, events, held, undated}`, `held` null with no ledger; an acceptance carries `subject` and `votes`, a retraction `retracts` and `cause` and no kind. Sends nothing.
Refusals and safe exits#
- `oko contributions: a task carries no id, author or status in the task map: <entry>`, and an unreadable task map refuses with its cause.
- `oko contributions: the ledger names a held record that is no identity: <value>` and a ledger answer with no held list are refused by name.