is this with debug logging? i wonder if data/a response is sent that we don’t parse correctly
i’ll try to replicate the error with debug logging, i thought it was on but i don’t think it was. part of the problem is it doesn’t halt consistently on one command, so i’ll have to try and wait it out and see if it does it again.
after more testing, finding that this may be an error with jupyter notebook interaction of some sort, as the error did not occur on the same and longer protocols when using a python script rather than a notebook
2 Likes
very odd, thanks for sharing