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 }}
This repository has been archived by the owner on Feb 27, 2024. It is now read-only.
Currently, a submit commands runs the submitted job on some executor. Log files containing the stdout/stderr are created on the executor. That makes debugging a bit harder than necessary. Hence, I suggest a different mode for running Strymon submit in foreground. In this mode, the job would not be detached but the submit command would continue to show the stdout/stderr streams.
This can be implemented in two stages.
Provide support for running local jobs in foreground as the log files are locally available
Add support for remotely executing jobs
The text was updated successfully, but these errors were encountered:
Currently, a submit commands runs the submitted job on some executor. Log files containing the stdout/stderr are created on the executor. That makes debugging a bit harder than necessary. Hence, I suggest a different mode for running Strymon submit in foreground. In this mode, the job would not be detached but the submit command would continue to show the stdout/stderr streams.
This can be implemented in two stages.
The text was updated successfully, but these errors were encountered: