-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(launcher): add new API endpoint /v1/launcher/time-limit
and update LauncherDialog
#2012
Conversation
I think the back-end should call this new endpoint inside the |
As stated in this issue: #1783 The API endpoints related to this form should be consolidated into one, that returns a structured json with all the necessary data like launcher versions, nb cpu, time limit, outputs list etc. |
e15b830
to
bd98824
Compare
…min`, `defaultValue` and `max`
…`, `defaultValue` and `max` values
Description:
This pull request introduces a new API endpoint,
/v1/launcher/time-limit
, which retrieves the time limit for a job (in seconds) for a given launcher: "local" or "slurm". The value is read from theapplication.yaml
configuration file.In addition, the
LauncherDialog
has been updated to use this endpoint to initialize the default and maximum values for thetimeLimit
field. The minimum value is set to 3600 seconds. The time limit is displayed in hours, with a step of 1 hour.This enhancement provides a more dynamic and configurable approach to setting the time limit for jobs, allowing for greater flexibility and control in job execution.