errors
etrack.infra.errors
infra/errors: the one root of every error — each layer imports its exceptions from here, none defines its own.
CoreError is the root. One branch per kind of module: ProviderError (a provider failed at its border), ProcessorError,
LogicError and OpsError. A provider fails as a driver (DriverError: a system outside the process) or as an
adapter (AdapterError: a library inside it). A sink is met on both natures — the OTLP exporter over the wire,
the live buffer in memory — so SinkError is honestly both.
AdapterError
Bases: ProviderError
A library inside the process failed: it refused its input, or the provider it wraps is not open.
AuthError
Bases: DriverError
Credentials that cannot be found or refreshed: a driver cannot sign what it sends.
BusError
ChannelError
Bases: LogicError, ValueError
An event the channel cannot validate against its model: a reserved key missing or of the wrong type.
DriverError
Bases: ProviderError
A system outside the process failed: unreachable, refusing, slow, or answering outside its contract.
FactError
Bases: LogicError, TypeError
A fact that does not meet its own class: a field of the wrong type, or a label that is no closed set.
FileError
LayoutError
Bases: ProcessorError, ValueError
A topology that cannot be placed: an edge to a node it does not declare.
ProviderError
Bases: CoreError
A provider failed at its border: what a third-party library raised, or a call on a provider that is not open.
ServerError
SinkError
SourceError
Bases: AdapterError
A source that cannot bind a run: the host's config is not of the shape its framework takes.