thunder-rpc 0.1.1

HiveLLM binary RPC — one crate: wire codec (v1, frozen), multiplexed client, and the family server hot path, behind features (SPEC-001/003/004)
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35

//! Error-string helpers for the two modelled conventions (SRV-021).
//!
//! `Response.result` errors are plain strings that travel verbatim
//! (WIRE-040); Thunder models exactly two prefix conventions — the
//! RESP3-style tokens `ERR`/`NOAUTH`/`WRONGPASS`/`NOPERM`, and the
//! bracket-code form `"[code] message"`. `ErrorConvention::Both` composes
//! them and is the standard, because a superset needs no negotiation.
//! These helpers exist so applications never hand-roll the spellings.

/// Family-pinned auth-required error (`Resp3Prefixes`, SRV-011).
pub const NOAUTH: &str = "NOAUTH Authentication required.";

/// Family-pinned bad-credentials error (`Resp3Prefixes`).
pub const WRONGPASS: &str = "WRONGPASS invalid username-password pair or user is disabled.";

/// Family-pinned insufficient-privilege error (`Resp3Prefixes`).
///
/// Thunder's listener never emits this itself — authorization beyond the
/// handshake is the product's, raised from its [`Dispatch`](super::Dispatch)
/// — but Synap ships exactly this token for its admin ACL, so the family
/// pins one spelling instead of letting each product invent another. Clients
/// classify it as an auth-class error (CLT-051).
pub const NOPERM: &str = "NOPERM this command requires admin privileges";

/// Format the machine-readable convention: `"[<code>] <message>"`
/// (PRO-014 `BracketCode`).
pub fn format_bracket_code(code: &str, message: &str) -> String {
    format!("[{code}] {message}")
}

/// Format the generic-error convention: `"ERR <message>"`
/// (PRO-014 `Resp3Prefixes`).
pub fn format_err(message: &str) -> String {
    format!("ERR {message}")
}