-
Notifications
You must be signed in to change notification settings - Fork 185
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
Minor accelerator fixes #1764
Minor accelerator fixes #1764
Conversation
4c72bbd
to
d0a261d
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.
e.response?.body?.message || e.message, | ||
); | ||
throw `A ${e.statusCode} error occurred when trying to create gpu migration configmap: ${ | ||
e.response?.body?.message || e?.response?.statusMessage |
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.
For example you are using or here
d0a261d
to
00e91b0
Compare
@lucferbux I migrated everything that was using || to use ?? |
@@ -47,7 +47,7 @@ const ServingRuntimeDetails: React.FC<ServingRuntimeDetailsProps> = ({ obj }) => | |||
<DescriptionListGroup> | |||
<DescriptionListTerm>Accelerator</DescriptionListTerm> | |||
<DescriptionListDescription> | |||
{accelerator.accelerator?.spec.displayName || 'unknown'} | |||
{accelerator.accelerator?.spec.displayName || 'None'} |
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.
Would this cause a problem with existing Model Servers?
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.
for exisitng model servers, the useAcceleratorState still gets called and we evaluate what accelerator they are using. In this flow exisitng serving runtimes would wither fall into the useExisiting
state or the Nvidia GPU
state. It wont be linked to a profile, but it would be uses the fake profile (soft migration or whatever we call it)
@@ -108,7 +108,7 @@ const NotebookServerDetails: React.FC = () => { | |||
<DescriptionListGroup> | |||
<DescriptionListTerm>Accelerator</DescriptionListTerm> | |||
<DescriptionListDescription> | |||
{accelerator.accelerator?.spec.displayName || 'unknown'} | |||
{accelerator.accelerator?.spec.displayName || 'None'} |
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.
Same here -- if the value is 0 -- none makes sense... if the value > 0 -- this is odd.
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.
we should have an unknown
and a none
so three cases
accelerator
is defined: use displayName
accelerator
is undefined
AND useExisting
is true
: use "Unknown"
accelerator
is undefined
AND useExisting
is false
: use "None"
making image/servingruntime naming dynamic fix count going back to 0 prevent 0 count and ux style fix removed usage of unknown when not needed remove double array usage improved backend logging fix logging undefined error make ?? consistent fixed "||" and fixed unknown / none details
00e91b0
to
a92ab5b
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.
@Gkrumbach07 please update your screenshots
/hold
Remove the hold when you have done so -- it'll be easier for Yan to read next week.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andrewballantyne The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
closes: #1765
Description
Minor UX and bug fixes found by testers
How Has This Been Tested?
Test Impact
no tests are made for this feature yet. These will be created once the feature has gone through development
Request review criteria:
Self checklist (all need to be checked):
If you have UI changes:
There are UI changes, but they are not changes in the UX, just small bugs. I will still tag UX, however there is not much action needed.
@yannnz
After the PR is posted & before it merges:
main