Andy Green
Andy Green
What happens with main / v4.4-stable?
yes... everything is OK? yes... it's broken the same? Have you tried any minimal examples directly rather than your own user code?
.... hm it might feel I should magically know what broke, but in fact this is your code + the library. I am pretty sure the library works well for...
If that's your problem, the example code I gave there to bind your protocol to be the "default" one selected when no specfific one is given should also solve it.
No. As I explained in 3487, the protocol should always have a name. If it happened that the protocol was #0 then this only worked by accident. The pvo arrangements...
Well, with that on top it builds locally OK. I removed the old one from v4.4-stable, let's try this one in CI again with main
Originally there was a big difficulty implementing mbedtls support, because it is so different from openssl. So I borrowed the Espressif openssl wrapper (it's also MIT) to reduce the gulf....
You can't pull main, it is developed by force-pushing. To update to it, for example (save any changes somewhere first) `git fetch origin +main:m && git reset --hard m`
Sorry, these are on top of current main? That tree already has your patches from yesterday ``` commit ede430b93deaad93035d2210ec51b02715062afe Author: makejian Date: Thu Jul 31 19:19:35 2025 +0800 [PATCH] lws/mbedtls-openssl:...
I notice that we change the return code meaning, but we don't adapt the caller. Since mbedtls works today, are we sure that is a good idea?