Assistance with handling and tracking down the cause of: Error: .getCursorLocation() timed out about terminal-kit HOT 2 CLOSED

Hi @MichaelLeeHobbs ,
What you did is probably already the best solution.

To give you some insight, the terminal "protocol" is not really reliable, and in fact, a terminal that does not handle a cursor location request will just silently ignore it, thus the only way to guess if it does not support that feature is to set up a timeout.

So increasing that timeout value is what you need to do.

However, it sounds weird that you need to set it to a value as big as 3000 ms.

Do you try to use Terminal-kit before the end of the SSH negotiation phase? (in your sample code, it seems that the terminal is created once the SSH connection is fully functional, but I'm not sure how the underlying lib works).
If so, I would suggest you to simply wait for a fully functional connection before using Terminal-kit high-level features like .inputField(), and set the the timeout to something like 500 ms.

Also it's worth noting that there is almost no side-effect with a big timeout value, except that if something is not working, it would take more time to fail.

Also that error does nothing with to SDTIN, you should still be able to use Terminal-kit even after that error.

from terminal-kit.

@cronvel Thanks for the info. The high value is likely due to our older SSL VPN we are phasing out. Saying it's terrible is unfair to the word terrible. I'll set the value back down to a normal value and do some testing/debugging on why the terminal seems to break after an error. It's very likely it could be something we are doing as we are doing man-in-the-middle operations to manage the remote passwords. We had a lot of issues early on where we caused the streams to break or close.

from terminal-kit.