Traceback is printed to Debug I/O window after exception reported.

edit

I'm currently seeing this bug in 9.1.2.1 (rev a76268badf6d). If it helps I'm raising an exception inside the scope of a relevant pytest.raises context manager. When I try to access the exception value in the debug console I'm told that isn't allowed until the context manager is complete.

The stack trace in the debug window appears to be in some sort of markup language, as follows.

<exception syntax="no"> <traceback> <frame lineno="341" filename="/Users/sholden/.venvs/meshtastic/lib/python3.10/site-packages/_pytest/runner.py" name="from_call"> result: Optional[TResult] = func()</frame> <frame lineno="241" filename="/Users/sholden/.venvs/meshtastic/lib/python3.10/site-packages/_pytest/runner.py" name="&lt;lambda&gt;"> lambda: runtest_hook(item=item, **kwds), when=when, reraise=reraise</frame> <frame lineno="502" filename="/Users/sholden/.venvs/meshtastic/lib/python3.10/site-packages/pluggy/_hooks.py" name="__call__"> return self._hookexec(self.name, self._hookimpls.copy(), kwargs, firstresult)</frame> <frame lineno="120" filename="/Users/sholden/.venvs/meshtastic/lib/python3.10/site-packages/pluggy/_manager.py" name="_hookexec"> return self._inner_hookexec(hook_name, methods, kwargs, firstresult)</frame> ... filename="/opt/homebrew/Cellar/python@3.10/3.10.13/Frameworks/Python.framework/Versions/3.10/lib/python3.10/unittest/mock.py" name="patched"> return func(*newargs, **newkeywargs)</frame> <frame lineno="60" filename="/Users/sholden/Projects/meshtastic/python/meshtastic/tests/test_serial_interface.py" name="test_SerialInterface_multiple_ports"> SerialInterface(noProto=True)</frame> <frame lineno="41" filename="/Users/sholden/Projects/meshtastic/python/meshtastic/serial_interface.py" name="__init__"> raise OSError(</frame> </traceback> </exception>

It was mostly an annoyance while debugging but its awesome that it turned up a more significant issue. Now I just have to get onto version 6 to get the patch. :)