Alan-Jowett / sonde / 26131054761

82%

push

github

fix: run decoder enrichment on WAKE blob data (#1018)

* fix: run decoder enrichment on WAKE blob data

The WAKE blob path in handle_wake_message never executed decoder
BPF enrichment — it always passed None for readings to both the
connector and handler. Decoder enrichment only ran in the APP_DATA
path (handle_app_data_message).

Nodes that piggyback sensor data on the WAKE message (e.g. SHT40)
had their data forwarded raw/unenriched, so the connector never
received decoded sensor readings for those payloads.

Add the same decoder lookup + xecute_decoder + error-handling
logic from the APP_DATA path to the WAKE blob path, so both the
connector \mit_app_data\ call and the handler \HandlerMessage::Data\
receive enriched readings regardless of delivery mechanism.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

* test: add WAKE blob decoder enrichment integration test

Exercises the full gateway-to-connector pipeline for WAKE blob
decoder enrichment: stores a program with a decoder BPF image,
sends a WAKE with a piggybacked blob, and asserts the connector
APP_DATA message contains enriched readings at CBOR key 16.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

---------

Co-authored-by: Alan Jowett <alan.jowett@microsoft.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

16 of 31 new or added lines in 1 file covered. (51.61%)

37740 of 45515 relevant lines covered (82.92%)

248.85 hits per line