You'll notice
Useful2 Signal1
Typing after a remote session's stream closes is discarded rather than throwing an error.
What's wrong with this entry?
Anonymous. No account, no email.
What
In remote sessions, terminal input was written straight into the session stream and could throw if the stream had already closed. Writes now check first and are silently discarded once it has ended.
Details
- The first drop on each input channel is reported once with the channel name, which is
stdinfor terminal input; later drops are silent. - Applies to all remote transports with no setting to change it.
Evidence
cli_remote_io_inbound_dropped_after_close
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.