e.self.config.clock.f¶
Nothing was waiting, but these two clocks disagree by too much for that to mean anything.
Retrying the same thing changes nothing.
What a response says¶
The mailbox was empty and {witness} reports a clock {seconds} seconds from this one, which is further than {tolerated} — far enough that a timeliness check at the far end would refuse what was asked, and an empty answer is what that looks like.
The placeholders are filled from witness, seconds, tolerated, which travel positionally in the args member of the response.
What to do¶
Nothing here says whose clock is wrong, only that they cannot both be right — so this names a fault rather than a party. Fix whichever host is adrift, usually by letting it sync its time, and ask again; retrying under the same clocks reads the same. The reported gap is the one that must exist, so it is a floor and not an estimate.
Where it sits¶
| Sorter | e — Error. The problem clearly defeats someone's intentions. |
| Obstacle | e.self. — Us — our fault, or we cannot attribute it |
| Disposition | f — Final. Retrying the same thing changes nothing. |
A handler can match this code exactly, or by any prefix above it: e.self., e.self.config., e.self.config.clock..
Declared in heti.