pub enum BackendError {
InitializationError(String),
ProcessingError(String),
ModelError(String),
CommunicationError(String),
InvalidInput(String),
Protocol(ProtocolError),
}Expand description
Errors returned by crate::IpcBackend and crate::HybridFlowBackend.
These cover initialization, processing, model persistence, IPC communication,
invalid caller input, and structured-message protocol rejection. Most
variants carry a human-readable String. BackendError::Protocol carries
a ProtocolError so a hybrid-flow receiver can reject an unexpected
crate::IpcMessage variant without overloading a transport or validation
failure.
Variants§
InitializationError(String)
Backend failed to initialize (e.g. model load failure, ZMQ connect error).
ProcessingError(String)
Error during process_batch (e.g. shape mismatch, backend internal failure).
ModelError(String)
Model save/load or filesystem I/O error.
CommunicationError(String)
IPC / transport communication error (ZMQ send/recv, framing, timeout).
InvalidInput(String)
Caller supplied invalid input (e.g. empty batch where disallowed, bad config).
Protocol(ProtocolError)
A structured message was valid on the wire but not acceptable for this call.
Hybrid-flow receivers return this when an inbound crate::IpcMessage
decodes and validates, then turns out to be a different variant than the
method accepts. The frame is already consumed; it is not dropped silently
and it is not retried.
Trait Implementations§
Source§impl Debug for BackendError
impl Debug for BackendError
Source§impl Display for BackendError
impl Display for BackendError
Source§impl Error for BackendError
impl Error for BackendError
Source§fn source(&self) -> Option<&(dyn Error + 'static)>
fn source(&self) -> Option<&(dyn Error + 'static)>
1.0.0 · Source§fn description(&self) -> &str
fn description(&self) -> &str
use the Display impl or to_string()