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

fix: Fixed the maximum desired number of sessions value in the Model Launcher modal to follow max_session_count_per_model_session #2726

Merged
merged 1 commit into from
Sep 30, 2024

Conversation

ironAiken2
Copy link
Contributor

@ironAiken2 ironAiken2 commented Sep 30, 2024

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:

  • 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

Copy link

graphite-app bot commented Sep 30, 2024

Your org requires the Graphite merge queue for merging into main

Add 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.

Copy link
Contributor Author

@github-actions github-actions bot added the size:M 30~100 LoC label Sep 30, 2024
Copy link

github-actions bot commented Sep 30, 2024

Coverage report for ./react

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

@ironAiken2 ironAiken2 marked this pull request as ready for review September 30, 2024 08:08
@ironAiken2 ironAiken2 force-pushed the fix/model-launcher-modal-max-session-value branch from f66479e to cf140d3 Compare September 30, 2024 08:32
@ironAiken2 ironAiken2 marked this pull request as draft September 30, 2024 09:06
@ironAiken2 ironAiken2 force-pushed the fix/model-launcher-modal-max-session-value branch from cf140d3 to 5ff923f Compare September 30, 2024 09:23
@github-actions github-actions bot added area:ux UI / UX issue. area:i18n Localization size:L 100~500 LoC and removed size:M 30~100 LoC labels Sep 30, 2024
Copy link
Contributor Author

When max value is 0, the error message was showing "value between 0 and 0", so �I fixed that as well. @yomybaby

@ironAiken2 ironAiken2 marked this pull request as ready for review September 30, 2024 09:25
@ironAiken2 ironAiken2 force-pushed the fix/model-launcher-modal-max-session-value branch 2 times, most recently from 1a7b543 to e7800ef Compare September 30, 2024 10:27
@github-actions github-actions bot added size:M 30~100 LoC and removed size:L 100~500 LoC labels Sep 30, 2024
Copy link
Member

@yomybaby yomybaby left a 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.

Copy link

graphite-app bot commented Sep 30, 2024

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
@yomybaby yomybaby force-pushed the fix/model-launcher-modal-max-session-value branch from f2e7b26 to 25973e0 Compare September 30, 2024 12:25
@graphite-app graphite-app bot merged commit 25973e0 into main Sep 30, 2024
6 checks passed
@graphite-app graphite-app bot deleted the fix/model-launcher-modal-max-session-value branch September 30, 2024 12:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:i18n Localization area:ux UI / UX issue. size:M 30~100 LoC
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Change the model service creation desired routing count max value setting
2 participants