e.state.pending.member-keys.r¶
This group's members haven't rotated their own identifiers yet, so it cannot rotate.
Retrying may succeed — this one is worth another attempt.
What a response says¶
A group's new keys are its members' CURRENT keys, and {gid} committed to its members' NEXT keys, so it cannot rotate until enough of them have rotated their own identifiers. Members still offering the key they contributed before: {count}, the first being {lagging}.
The placeholders are filled from gid, count, lagging, which travel positionally in the args member of the response.
What to do¶
Retryable, and the remedy is each named member calling rotate() on its own facet, and the others refreshing that contact so they can see it. keripy accepts a rotation like this without a word and leaves it in escrow forever, so the refusal is mine.
Where it sits¶
| Sorter | e — Error. The problem clearly defeats someone's intentions. |
| Obstacle | e.state. — The condition of the target |
| Disposition | r — Retryable. Trying again may succeed. |
A handler can match this code exactly, or by any prefix above it: e.state., e.state.pending., e.state.pending.member-keys..
Declared in heti.