I noticed one occasion where leaving an Adafruit CLUE running 5.0.0 beta 5 with some very verbose output to stdout for over an hour caused the terminal output to stop but the application continues merrily. I've just reproduced this with the same application/library code on 5.0.0 but it took approximately 130 minutes to do it.
- 5.0.0 beta 5 with PuTTY 0.70 (this version misses various security fixes, not recommended for general use) on Windows 8.1 desktop
- 5.0.0 with PuTTY 0.73 on Windows 10 laptop (left YT video running in browser to stop it from hibernating/screen saving)
The application is reading analogue values from P0-P2 and graphing them. It does not have the serial console active on the display. In both cases the application continued to run. PuTTY does not indicate the serial connection has closed. Control-C still works and takes the CLUE to the serial output on the LCD but with no output over USB. It says KeyboardInterrupt: as it normally does but does not respond to further typing, e.g. can't interact with REPL. Control-C and Control-D do nothing. In both cases the CIRCUITPY drive remains accessible. In the first case the writes stopped after the first of two arguments to print which made me more suspicious of CP than the terminal program.
I could continue interacting with the CLUE on both occasions. I could restart the code by coping a file onto CIRCUITPY. I could stop it with Control-C but still with no output to serial console, just the LCD when I hit Control-C. I've tried a Reset Terminal in PuTTY - nothing changed. I can disconnect COM5 then reconnect and everything's then back to normal. The special treatment here for Control-C makes it feel less likely to be a terminal program issue too.
Briefly discussed this with in Discord.
该提问来源于开源项目：adafruit/circuitpython
