Theoretical handling of stream non-availability or delayed availability

[cte]

Context

Earlier today I encountered another instance of the task UI hanging indefinitely after a command execution. I didn't have the logging in place to diagnose the issue, and I'm still trying to repro it in my dogfooding build, but in the meantime these are some theoretical edge cases that may be worth handling.

• If for some reason an execution stream is undefined by we have a process object then emit a stream_unavailable event so that we can close the process out instead of waiting indefinitely for a stream that is never to going to be available. This is a theoretical fix; I don't know if it can happen in practice.
• Add a 10s timeout to await streamAvailable using Promise.race. This ensures that we can unlock the UI if there's some delay on stream availability. Again, this is theoretical.
• Adds additional logging.

Implementation

Screenshots

before	after

How to Test

Get in Touch

---

Important

Prevent UI lock by handling unavailable streams and adding timeouts in terminal command executions.

• Behavior:
  • Emit stream_unavailable event in TerminalManager if execution stream is undefined but process object exists.
  • Add 10s timeout to await streamAvailable in TerminalProcess using Promise.race to prevent indefinite UI lock.
• Logging:
  • Add additional logging in TerminalManager and TerminalProcess for better diagnostics.
• Events:
  • Add stream_unavailable event to TerminalProcessEvents in TerminalProcess.ts.

^{This description was created by for eee7bbe. It will automatically update as commits are pushed.}