use of reset() increases robustness but obscures debugging

[sgbaird]

Mainly because it renders the following after any error in the try block is raised:

PROBLEM IN THONNY'S BACK-END: Exception while handling 'Run' (ConnectionError: EOF).
You may need to press "Stop/Restart" or hard-reset your MicroPython device and try again.

See Thonny's backend.log for more info.

Process ended with exit code 1.

Commenting reset() while debugging is one option:

self-driving-lab-demo/src/public_mqtt_sdl_demo/main.py

Line 288 in bbf2b10

reset()

There could also be a debug flag that gets set at the beginning, where if it's True, then it doesn't run the reset line. Similarly, there could be a num_hard_reset_tries variable or similar.

[sgbaird]

Maybe doing a soft reset via sys.exit() before doing reset() would make sense here.