You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Unable to view/list command-line processes in Editor #3588
We saw users get confused when trying to run the same server (command-line) app twice. The second run fails because "address is already in use", which is correct. However, the user did not know that a previous server was running (which originally opened the port)
The original tab for the output view was closed, but the original process continued to run.
Problem: Users don't know that the script/program is still running, and they are confused when the most recent run fails immediately. There is no way to reference or stop the previous script/program.
Possible suggestions:
provide an easy to use View for all running command-line processes
let a user kill a command-line process
prompt a user: "You are already running this script. Stop the old process before running?"
The route I went is to terminate the launched process when you close the console associated with it. That way you can never get into the situation where a process is running in the background. This route means we don't need a UI to manage running processes.
Activity
jwren commentedon Jun 12, 2012
Added this to the IO2012 milestone.
devoncarew commentedon Jun 16, 2012
Set owner to @devoncarew.
devoncarew commentedon Jun 18, 2012
The route I went is to terminate the launched process when you close the console associated with it. That way you can never get into the situation where a process is running in the background. This route means we don't need a UI to manage running processes.
Added Fixed label.
sethladd commentedon Jun 18, 2012
Thanks Devon. This will help!
[deps] rev core, dartdoc, ecosystem, http, i18n, native, shelf, tools…