distant action --interactive pegging to 100% CPU

[chipsenkbeil]

Maybe this has to do with the stdin loop since we aren't using async per tokio's recommendation. Need to see if that's the case and if adding a yield and/or sleep of some sort will help.

[chipsenkbeil]

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.

[chipsenkbeil]

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.

[github-actions]

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.