We noticed that socket_connect() implementation in LWIPStack.cpp performs a blocking connect call to the underlying LWIP netconn API. Due to this, our application connectivity thread using mbed-os TLSSocket APIs hangs for sometime trying to connect to our backend. The default semaphore wait timeout also seems to be set to infinite.
Is there a specific reason for choosing blocking vs. non-blocking implementation for netconn_connect API?