microsoft
Follow with MXChip to fix the underlying socket running into unknown status if send telemetry in another thread
The telemetry sending is running in another thread, if the main thread can't send a message (socket send)within about 15s after sending a telemetry message, this socket is running into unknown status. Then send API return succeed but actually it's failed, and no API to detect it. This should be a defeat in the underlying WiFi driver, thread related.
This issue has no recent activities, please take a look and provide updates for it.
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
This issue has no recent activities, please take a look and provide updates for it.
This issue has been automatically marked as stale because it has no recent activities. It will be closed if no further activity occurs within 3 days. Thank you for your contributions.