azure-sphere-devx / azurespheredevx Goto Github PK

Network disconnect should invoke network status changed callbacks.

to support intercore patterns that are hl write then wait for response you needed prthread wait for intercore callback to be received. Now you can set the intercore handler to NULL, write(publish) to the RT and then sit on a read (with timeout) for the response. Simplifies for RT cache and SD Cards scenarios.

Fix tested submitted and merged as want for Altair project today.

@bawilless

To demonstrate how to manage device twins strings, we should update the device_twin example with a custom handler for the string example.

I'll take this task

Hello @gloveboxes,

Thanks again for looking into that dx_utilities issue I posted last week.

I continue to make unit tests for my Azure Sphere project. And, of course, complications continue to rise. I am currently mocking some files (eventloop.c and eventloop_timer_utilities.c) that use the EventLoop, EventLoopTimer, and EventRegistration structs. However, my mocking tool (and myself) cannot seem to find the definitions for those structs. I can stub in some definitions for them to continue my work. But, if anyone re-creates my mocked files (auto generated by Ceedling), my hand-made stubs will disappear and break my test suite.

Am I missing something here? Are these definitions somewhere that I'm just not seeing? Or, are they hidden from me (intentionally or otherwise)?

Regards,
Craig

Edit: I am away from my work computer, but I recall finding one of those definitions in a C file (don't recall which one). But that still makes mocking difficult.

I've started to do some work with a unit test framework that had some problems mocking this function. Is the function pointer here malformed?

I don't think that this repo is using any submodules anymore, but the repo still has references to submodules. These should be removed and the readme.md file updated to remove the --recurse-submodules reference.

When devices don't connect to the IoTHub the error messages don't usually help the developer understand the root cause of the issue. It would be great to simulate different failure modes, and make sure that the error messages are meaningful.

For example, if my device has a wifi connection, but the connection is not to the internet devX reports ERROR: Current Application not Device Auth Ready A beter error message would be ERROR: No internet connection, check your network connection"

@bawilless A device twin update had a IoTHubDeviceClient_LL_DoWork at the end that was turning what should be an async call into an sync call. Have removed the call to dowork so a twin update wont force a a sync dowork operation. I believe this is inline with how a twin should operate. The twin update will be picked up by the main IoTHubDeviceClient_LL_DoWork on the 100ms timer in the azure_iot client