distant action --interactive pegging to 100% CPU about distant HOT 2 CLOSED

See rust-lang/rust#46774 . Looking back, I'm not using thread::yield_now or thread::sleep in the loop as I just let it block on reading stdin. Would make sense to add some delay there. Still don't know if that's the cause, though.

from distant.

Resolved by de69b41

Turns out this was only happening when the stdin stream for action had closed as the loop was not checking for EOF on the stream, meaning that it went into an endless loop with no break inbetween checks that finished immediately. We now properly kill the stdin thread once it reaches EOF as well as issue std::thread::yield_now() between successful calls.

from distant.