Jan Petykiewicz

Thanks! I have encountered this as well, and will work on fixing it next. Sub-issues: - [x] poor handling of disconnect/reconnect - [ ] no way to tell from within...

I think I've fixed the issues with exceptions not propagating correctly; I'll keep an eye out for further problems.

Thanks! Haven't seen this before, will try to replicate. You can get additional output by changing `logging.basicConfig(level=logging.INFO,` to `logging.basicConfig(level=logging.DEBUG,` in `mxpp/main.py`; I will add a config file interface for making...

Yep, that figure is correct -- glad to hear that the project might be useful for you! I don't personally use MUCs, but I'll certainly take a look at implementing...

I've implemented basic MUC support. You have to join/leave manually with text commands since I haven't found a way to reliably test invitations, but messaging seems to work fine.

Without the truncation, the invocation of ```ip link add dev ... type ifb``` below the affected code errors out with the message ``` : interface enx78e7d1ea46da world_in input rate 73mbitError:...

Per pexpect/pexpect#669 this is unlikely to be fixed upstream, but it is having some impact downstream already ( blink1073/oct2py#237 and blink1073/oct2py#248 ). Would `REPLWrapper.run_command()` be a reasonable place to check...

Same issue on v137.0.1 (on Debian). Similar errors in the console (log attached below). No problem in Chromium. The left pane of the "sandwich" view is rendered, but everything else...

Just checked, same symptoms when on the latest commit (67e139e6) of your launcher-improvements branch.

I'm running the linux-native launcher. I believe 1.8 attempts to launch the game itself via proton, and that's the code that is failing.