Distant manager unresponsive when Ctrl-C after running `distant spawn -- htop`
chipsenkbeil opened this issue · 4 comments
My guess is that we are receiving data frequently from the server and there's a logic mistake somewhere in distant where we aren't freeing up async processing time to handle new requests. I'm not seeing a log of the request coming in.
Even after killing htop remotely, the manager is still unresponsive to the request, but authentication works fine. So something around request processing is stuck.
This does NOT happen with a locally-run server on my M1 Mac mini via distant launch manager://localhost followed by distant spawn --pty -- htop. I couldn't run it without --pty on my M1 Mac mini. Ctrl-C the htop instance let me do it again without issue.
With my test linode linux instance, I am able to run without --pty and it DOES hang when I Ctrl-C the htop instance and then try again with anything. The Linode instance only has a single core/thread, but I don't know if that would impact or not.
Appears to be resolved thanks to #202 being resolved.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.