-
Notifications
You must be signed in to change notification settings - Fork 72
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
fix: Fixed the maximum desired number of sessions value in the Model Launcher modal to follow max_session_count_per_model_session
#2726
Conversation
Your org requires the Graphite merge queue for merging into mainAdd the label “flow:merge-queue” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge. Or use the label “flow:hotfix” to add to the merge queue as a hot fix. You must have a Graphite account and log in to Graphite in order to use the merge queue. Sign up using this link. |
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @ironAiken2 and the rest of your teammates on Graphite |
Coverage report for
|
St.❔ |
Category | Percentage | Covered / Total |
---|---|---|---|
🔴 | Statements | 5.33% (-0% 🔻) |
340/6381 |
🔴 | Branches | 4.82% (-0.01% 🔻) |
214/4439 |
🔴 | Functions | 3% | 63/2101 |
🔴 | Lines | 5.23% (-0% 🔻) |
326/6234 |
Test suite run success
90 tests passing in 11 suites.
Report generated by 🧪jest coverage report action from 25973e0
f66479e
to
cf140d3
Compare
cf140d3
to
5ff923f
Compare
When max value is 0, the error message was showing "value between 0 and 0", so �I fixed that as well. @yomybaby |
1a7b543
to
e7800ef
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, please check my commits.
Merge activity
|
…Launcher modal to follow `max_session_count_per_model_session` (#2726) ### This PR resolves [#2723 Issue](#2723) [teams](https://teams.microsoft.com/l/message/19:[email protected]/1727418901786?tenantId=13c6a44d-9b52-4b9e-aa34-0513ee7131f2&groupId=74ae2c4d-ec4d-4fdf-b2c2-f5041d1e8631&parentMessageId=1727418901786&teamName=devops&channelName=Backend.AI%20Talks&createdTime=1727418901786) This PR introduces a new query to fetch the user's resource policy and applies the `max_session_count_per_model_session` limit to the service launcher page. The changes include: - Added two new queries: `ServiceLauncherPageContent_UserInfoQuery` and `ServiceLauncherPageContent_UserResourcePolicyQuery` - Utilized `useLazyLoadQuery` to fetch user information and resource policy - Applied the `max_session_count_per_model_session` from the user's resource policy to the session count input field These changes allow for dynamic session count limits based on the user's resource policy, improving the flexibility and customization of the service launcher. **Checklist:** - [ ] Documentation update for new resource policy feature - [ ] Minimum required manager version: 23.09.6 - [ ] Test cases to verify the application of custom max session count limits
f2e7b26
to
25973e0
Compare
This PR resolves #2723 Issue
teams
This PR introduces a new query to fetch the user's resource policy and applies the
max_session_count_per_model_session
limit to the service launcher page. The changes include:ServiceLauncherPageContent_UserInfoQuery
andServiceLauncherPageContent_UserResourcePolicyQuery
useLazyLoadQuery
to fetch user information and resource policymax_session_count_per_model_session
from the user's resource policy to the session count input fieldThese changes allow for dynamic session count limits based on the user's resource policy, improving the flexibility and customization of the service launcher.
Checklist: