Printer refuses to connect after setting low latency flag fails

[foosel]

Problem

Since rolling out 1.7.0, there have been a small number of people running into connection issues when setting low latency mode on the serial port fails, e.g. on this thread and also some comments here and there on Discord and elsewhere.

While the error resulting from failing to set the low latency flag itself is gracefully handed, apparently the involved serial ports don't even like the attempt and then no longer work correctly.

Solution

Short term as part of the bug fix release 1.7.1: Turn requesting low latency mode off by default.

Longer term: Maybe close and reopen the port on mode setting failure? That would however require someone who can reproduce the issue to collaborate so possible mitigations can be tested. I currently don't have discovered any system on hand that shows the problematic behaviour and thus can only guess so far.

[draeath]

Well, shoot. That was my PR and I feel crappy about it causing people problems :(

[foosel]

I'm going to close this as at least the buggy situation seems to have seem fixed now with not using the low latency flag by default.

Long term I'd still like to find a printer this affected and see I can find a work around to fully recover from a failed attempt automatically so we can default to this again, but until this is the case, this will have to stay off by default 🤷‍♀️