Open idrise opened 4 years ago
Hey @idrise! Thanks for the report. Sounds like an easy fix.
I was looking at this issue - while it does indeed seem like an easy fix, I'm not sure which feedback should concurrently provide.
It'd be nice to print the usual "blabla exited with
I think a clean exit, killing the running processes makes the most sense IMHO. Could be that any throw ends up leaving processes hanging.
Recreate
concurrently --kill-others -n api,ui \"nx serve api\" \"nx serve ui\" | lnav -t
Then press q to quit lnav and this error is reported and both API and UI continue to be served in the background. It would be great if concurrently shut down when the write stream is destroyed.