Send errors come from trying to send a message to another process,
either locally or on another node.
A message can fail by timing out, or by the node being entirely
unreachable (offline or can’t be found in PKI). In either case,
the message is not delivered and the process that sent it receives
that message back along with any assigned context and/or lazy-load-blob,
and is free to handle it as it sees fit.
In the local case, only timeout errors are possible and also cover the case
in which a process is not running or does not exist.
A message can be a request or a response. Within a response, there is
a result which surfaces any error that happened because of a request.
A successful response will contain the context of the request it
matches, if any was set.
On-exit is a setting that determines what happens when a process
panics, completes, or otherwise “ends”.
NOTE: requests will always have expects-response set to false by kernel.
˗ˏˋ ♡ ˎˊ˗
System Utils
˗ˏˋ ♡ ˎˊ˗
Prints to the terminal at a given verbosity level.
Higher verbosity levels print more information.
Level 0 is always printed – use sparingly.
Context, like a message body, is a protocol-defined serialized byte
array. It is used when building a Request to save information that
will not be part of a Response, in order to more easily handle
(“contextualize”) that Response.