#[non_exhaustive]pub struct DeviceEvent {
pub lane: Option<LaneKey>,
pub edge: Edge,
pub detail: String,
}Expand description
Something the medium wants to say when nobody is calling Medium::send.
The gap #51 names: every DeviceError is the return value of a data-path
call, so a radio that loses registration, overheats, or drops off the bus is
silent until the next transmission — which on a store-and-forward link may
be an hour away, and on a dead one is never.
A plain struct rather than a channel, and that is the whole reason this
works. modem-device has three dependencies — async-trait, thiserror,
optional serde — and no tokio. Putting a watch::Receiver or a
broadcast::Receiver on the trait would drag a runtime into a crate whose
entire job is to be the seam, to obtain a channel type. An async fn
mirroring Medium::recv needs nothing, is dyn-compatible through the
async-trait already here, and has a default whose meaning is exactly
“this medium never says anything”.
Fields (Non-exhaustive)§
This struct is marked as non-exhaustive
Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.lane: Option<LaneKey>The lane it concerns, if it concerns one.
None for a device-wide condition — registration lost, over
temperature, duty-cycle budget exhausted — which is most of them.
edge: EdgeWhether this is the medium becoming unhappy or becoming happy again.
Edge-triggered by contract. A backend that repeated Raised while a
condition persisted would produce a stream no rate declaration could
honestly cover, and the consumer’s job is to publish these, not to
deduplicate somebody else’s.
detail: StringThe device’s own words.
Carried verbatim to the management plane, which is the point: until #51
a DeviceError::Device(String) reached a warn! and was discarded, so
+CME ERROR 3 — the one thing that says what is actually wrong — never
left the process.