Andrew Leech

Hi, that's interesting that the socket timeout is lost after reconnect, I feel that's perhaps an upstream bug that should be addressed. In the mean time, re-setting the timeout certainly...

> I have since read @pfalcon's comment in PR #117: > > > guarantee that check_msg() return immediately and can be used in main loops doing something else (otherwise, check_msg()...

> The setblocking() calls are both executed in the umqtt.simple module which knows nothing about "robustness"; storing additional variables in that class, for this purpose seems... improper! Agreed though, the...

@ian-llewellyn This does look quite good to me, nice cleanup. Keeps it all quite simple and I feel true-to-intention.

Looks good to me, I'll have to leave it to @jimmo for a final review.

I just had the same problem trying to install my first project, also in Windows WSL. The git filemode fix above didn't work for me however, after that and retrying...

I've run into the same problem (also using mbed 5.5) and tried target code level debugging to narrow the scope of the issue, without a lot of success. The same...

@dlech yes it's a good question that I'm still not 100% certain about. The irq priorities might be enough protection, that's why pend and systick are in the list being...

So the pre-processing of linker scripts comes with an undesirable side-effect - lines like `*lib/mbedtls/*(.text* .rodata*)` throw errors because it include `/*` in the middle of the line. While it...

My initial test of this was effortlessly delightful and incredibly powerful. Thanks @jimmo