-
Notifications
You must be signed in to change notification settings - Fork 178
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
Add model redeploying status #3513
Add model redeploying status #3513
Conversation
@kaedward Would you please take a quick peek at this? I think it looks OK, but you might have a different suggestion for the popover message. |
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.
The jira issue mentions this:
When activeModelState is in a pending state we will show the spinner without a tooltip.
Seems to me the fallback message right now is always going to be Unknown
?
(targetModelState === InferenceServiceModelState.LOADING || | ||
targetModelState === InferenceServiceModelState.PENDING) | ||
) { | ||
return 'Redeploying'; |
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.
@emilys314 did you get a response yet on suggestion of the new text? If not, we can always do a followup to update the text if everything else is good to go with the PR.
Should add unit tests for this util function.
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.
No updates on the wording, i believe Katie is out until next week
Sure I'll add tests
Yeah so the active vs target states don't seem to be well documented anywhere, but here are some tests from kserve
I don't think During initial deployment it would have The popover text will be hidden if the function returns "", it can do that now because it looks at activeModelState which becomes that commonly. But targetModelState is more up to date so this PR would make it happen less. However there does seem merit to return an emptry string sometimes so I can make a small update by changing |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3513 +/- ##
==========================================
+ Coverage 85.24% 85.54% +0.30%
==========================================
Files 1356 1342 -14
Lines 31075 31003 -72
Branches 8660 8663 +3
==========================================
+ Hits 26490 26523 +33
+ Misses 4585 4480 -105
... and 110 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
/lgtm |
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.
Not tested, but the code looks good - thanks Emily!
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alexcreasy 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 https://issues.redhat.com/browse/RHOAIENG-3409
Description
Makes the status a spinner after editing a model, popover message says "Redeploying".
Basically the status functions will prioritize looking at the target state, since that is more indicative of what is going on.
I'm not 100% on what the correct message is to display. But the special return case could be removed and then it would default to the state of the target i.e. "Loading".
How Has This Been Tested?
Test Impact
Jest unit tests could be added to the utils functions, but there aren't any so i didn't add any.
Request review criteria:
Self checklist (all need to be checked):
If you have UI changes:
@vconzola
After the PR is posted & before it merges:
main