Fork sky.execute when stream_logs=False

[gmittal]

Mainly looking at this from a UX perspective, but if you turn stream_logs=False (only pipe output to file, not stdout) you get this awkward interaction where sky execute still has control of the main terminal and it looks like it's just hanging while all the output goes to a logfile. Instead, we should run the process in the background and return control to the user's shell session so they can do other things (e.g. tail the logfile, launch another run, launch a gpunode, write code, etc.).

[franklsf95]

I agree that if we are not planning to print anything anymore, we should return the shell to the user. But then we'd need something like sky ps to monitor the progress, running jobs, etc.

[gmittal]

Yep, this is something that will be added to CLI. Gautam

…

On Wed, Nov 24 2021 at 11:00 AM, Frank Luan ***@***.***> wrote: I agree that if we are not planning to print anything anymore, we should return the shell to the user. But then we'd need something like sky ps to monitor the progress, running jobs, etc. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#59 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAPL7FQQTLJ2Q4TH7O4TVW3UNUY4TANCNFSM5IVPPIHA> .

[infwinston]

in this case, we'll be also needing CLI to kill a given sky task.

[concretevitamin]

This is subsumed by #134: Use -d for sky run/exec.