ESP-IDF Stream Example

[rashmivaidya72]

NOTE: The Zephyr LightDB Stream example uses the struct sensor_value from the Zephyr SDK. As this structure is not available outside of Zephyr, I have included its definition in the ESP-IDF example. Also, the Zephyr Example allows for obtaining temperature values directly from a temperature sensor if the platform supports it. However, the ESP-IDF example always generates fake temperature values.

[github-actions]

Visit the preview URL for this PR (updated for commit 0ee9d5e):

https://golioth-firmware-sdk-doxygen-dev--pr395-rsv-espidf-lig-ccdu6wlb.web.app

_{(expires Wed, 29 May 2024 18:52:00 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: a9993e61697a3983f3479e468bcb0b616f9a0578}

[sam-golioth]

@rashmivaidya72 The lightdb stream sample test failed on the esp32s3: https://github.com/golioth/golioth-firmware-sdk/actions/runs/8424019673/job/23067520531?pr=395

[rashmivaidya72]

@rashmivaidya72 The lightdb stream sample test failed on the esp32s3: https://github.com/golioth/golioth-firmware-sdk/actions/runs/8424019673/job/23067520531?pr=395

@sam-golioth This seems to be a timing issue. The test expects 20.0, but the DUT has already published 20.0 and 20.5, causing the assertion to fail.
FAILED examples/esp_idf/lightdb_stream/pytest/test_sample.py::test_lightdb_stream - assert 20.5 == 20.0

If I remove the check for Golioth client connected, the test speeds up and the assertion succeeds.

[github-actions]

Code Coverage

Type	Coverage
lines	58.7% (1259 of 2145 lines)
functions	65.8% (125 of 190 functions)

[sam-golioth]

We need to rebase this PR and fix the failing CI tests.

[sam-golioth]

Seeing intermittent failures on the CI test: https://github.com/golioth/golioth-firmware-sdk/actions/runs/8546397122/job/23416975750?pr=395#step:7:244

[sam-golioth]

@mniestroj @szczys This one is ready for a review