Damien George

> Thank you for the link. > Is it going to be part of the micropython? Actually, this is a better version: https://github.com/peterhinch/micropython-mqtt Eventually we would like to add links...

> just trying to get the code coverage metric up. Just one more tricky timing line to hit before the code coverage bot is satisfied. I don't think it's possible...

> Hmmm though now it does seem like the qemu tests are failing for some reason It looks like GitHub Actions have updated ubuntu-latest to ubuntu-24.04, and that's causing the...

> Once the other CI issues PR is merged, I can update mine here to sit on top of that change. The CI should now be fixed, so please rebase...

I have a few comments: 1. The docs need fixing in the sense that they are still documenting the `ssl` module, whereas this new functionality is in the MicroPython-specific `tls`...

@keenanjohnson I'm doing a final review here and trying to test it, but not having any luck. Do you have some (simple) example (Micro)Python code for both a DTLS server...

I finally managed to write a test where MicroPython is both a DTLS server and client, and they connect to each other, do a handshake, and transfer some data between...

I'm in favour of this change. I think it makes `mpremote` more consistent, in the following cases: 1. `mpremote repl` does not do a soft reset. 2. `mpremote run a.py...

Another argument for making resume the default: currently if you do: ``` $ mpremote exec "x=1" exec "print(x)" ``` then that works as expected, it sets and prints `x`. But...

I've run this updated test on a PYBD_SF6 and RPI_PICO2_W, and it passes without the fix from this PR. Not sure what to make of that... @andrewleech can you please...