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
first of all i'd like to thank you for fixing the issue #127 which helps a lot with invalid slurm file input! 👏
Referring to that issue i'd like to ask, if you could imagine to implement a command line switch for running a config test that exits with status code != 0 in case of any issue, e.g. an invalid slurm file? 😉
The reason is that despite the error message regarding the invalid slurm file entry, the rtr client connection still times out so that the service is not available/usable.
With the option of a "check/test mode", it can be included in a container image build process test stage to verify that the image runs without any issue before its pushed into the registry for deployment.
Thanks and best regards!
The text was updated successfully, but these errors were encountered:
Hello,
first of all i'd like to thank you for fixing the issue #127 which helps a lot with invalid slurm file input! 👏
Referring to that issue i'd like to ask, if you could imagine to implement a command line switch for running a config test that exits with status code
!= 0
in case of any issue, e.g. an invalid slurm file? 😉The reason is that despite the error message regarding the invalid slurm file entry, the rtr client connection still times out so that the service is not available/usable.
With the option of a "check/test mode", it can be included in a container image build process test stage to verify that the image runs without any issue before its pushed into the registry for deployment.
Thanks and best regards!
The text was updated successfully, but these errors were encountered: