Skip to content
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

User can set a batch session timeout #2812

Closed
yomybaby opened this issue Nov 5, 2024 · 1 comment · Fixed by #2824
Closed

User can set a batch session timeout #2812

yomybaby opened this issue Nov 5, 2024 · 1 comment · Fixed by #2824
Assignees
Labels
urgency:4 As soon as feasible, implementation is essential.
Milestone

Comments

@yomybaby
Copy link
Member

yomybaby commented Nov 5, 2024

In session launcher, user can set a batch session timeout.

Let's start implementing the UI even though the API is not ready yet.

@yomybaby yomybaby added this to the 24.12 milestone Nov 5, 2024
@agatha197 agatha197 added the urgency:4 As soon as feasible, implementation is essential. label Nov 8, 2024
agatha197 added a commit that referenced this issue Nov 14, 2024
resolves #2812
related PR: lablup/backend.ai#3066

Add batch job timeout duration to the session launcher.
User can select the time unit and input the timeout duration.

**How to test:**
> test endpoint: 10.82.230.49
1. Modify the support version of `batch-timeout` in `backend.ai-client-esm` for testing. (24.09)
2. Set session type to the batch.
3. Enable `Batch Job Timeout Duration`
  - eg
    start command: sleep 20 && echo \"hello world\"
    timeout: 3s

**Checklist:**
- [ ] Batch job timeout value remains after refreshing
- [ ] The 'Confirm and Launch' page has the same value if you set the 'Batch job timeout duration'.
- [ ] (API is not implemented yet) Create a new session with batch session timeout option.

**Screentshots:**
![image.png](https://graphite-user-uploaded-assets-prod.s3.amazonaws.com/2HueYSdFvL8pOB5mgrUQ/5adbf314-e521-4410-bed8-075124fad6c8.png)

![image.png](https://graphite-user-uploaded-assets-prod.s3.amazonaws.com/2HueYSdFvL8pOB5mgrUQ/c9dd0f12-695e-4960-ba98-9b6371c6a47a.png)

![image.png](https://graphite-user-uploaded-assets-prod.s3.amazonaws.com/2HueYSdFvL8pOB5mgrUQ/4075faa3-a61e-4ce3-833c-c858e6d6b75a.png)

![image.png](https://graphite-user-uploaded-assets-prod.s3.amazonaws.com/2HueYSdFvL8pOB5mgrUQ/600fd8cb-0040-43e4-b8fe-307730d292c0.png)

![image.png](https://graphite-user-uploaded-assets-prod.s3.amazonaws.com/2HueYSdFvL8pOB5mgrUQ/55116de0-e7eb-4ef7-8077-abde8ea73b3b.png)

**Checklist:**

- [ ] Documentation
- [ ] Test case: Verify timeout can be enabled/disabled
- [ ] Test case: Confirm time picker accepts valid duration formats
- [ ] Test case: Check default value initialization
- [ ] Test case: Validate timeout enforcement on batch sessions
@agatha197
Copy link
Contributor

resolved by #2824

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
urgency:4 As soon as feasible, implementation is essential.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants