Bill Carter

Seeing same issue here, we get no event when the server connection drops? What I'm seeing here is that the entire process just exits.

It would be great to see loboris comment, but I fear that this project is now abandonware. He is actively committing to his Kendryte K210 project in the repository adjacent...

There are a lot of great features, but the build system lets you conveniently set a huge number of parameters and burn both the firmware and the filesystem plus contents...

Would be glad to participate, can I get an invitation?

That address should work, thanks.

For convenience [I've put up a repository that just has a README](https://github.com/carterw/loboris_backports) in which we can capture things people think are important.

Having spoken with some of the mainstream MicroPython contributors on Slack, my sense is that not much of the loboris port will be incorporated. The _thread module was pulled in...

I agree those modules are very useful, and it would be great if they were included in the mainstream builds. I don't know where they originally came from. I suggest...

Here's what I do; ``` export LOBO="${HOME}/esp32/LoBo export MODULES="${LOBO}/MicroPython_ESP32_psRAM_LoBo/MicroPython_BUILD/components/micropython/esp32/modules" export FSIMAGE="${LOBO}/MicroPython_ESP32_psRAM_LoBo/MicroPython_BUILD/components/internalfs_image/image" MFILES="your comma-separated list of files or directories to embed into the firmware" FSFILES="your comma-separated list of files or directories...

Good catch. But you might have to just fix it in your own codebase, there haven't been any commits here since September of last year.