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
Currently, if a user uses the --launch-command option --to launch the job on a compute node-- and something goes wrong (e.g. they specified a non-existing queue or something is off in their job submission), jupyter-forward gets stuck in a re-try loop. We should make sure to detect this kind of failures and report them and exit.
The text was updated successfully, but these errors were encountered:
Currently, if a user uses the
--launch-command
option --to launch the job on a compute node-- and something goes wrong (e.g. they specified a non-existing queue or something is off in their job submission),jupyter-forward
gets stuck in are-try
loop. We should make sure to detect this kind of failures and report them and exit.The text was updated successfully, but these errors were encountered: