-
Notifications
You must be signed in to change notification settings - Fork 332
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: [M3-7962] - Large Account Search Loading State #10351
fix: [M3-7962] - Large Account Search Loading State #10351
Conversation
|
f490b72
to
ce10d7f
Compare
alternative fix: #10352 |
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.
Fixes look good as far as I could test with large accounts locally. β
Need more eyes and testing on this if possible
areVolumesLoading || | ||
areKubernetesClustersLoading || | ||
areImagesLoading || | ||
areNodeBalancersLoading; |
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.
π’ yeah some refactoring will be needed soon
would a useQueries()
make sense for this file?
@@ -77,6 +77,8 @@ export const SearchLanding = (props: SearchLandingProps) => { | |||
|
|||
const isLargeAccount = useIsLargeAccount(); | |||
|
|||
const shouldFetchAllEntities = isLargeAccount === false; |
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.
Let's please add a comment as to exactly what this means (we're fetching paginated records here for large accounts, right?). May help for future refactoring/debugging
We will need a ticket and a changeset when this gets out of draft too |
2143926
to
46eaff4
Compare
The base branch was changed.
46eaff4
to
6242fdf
Compare
Coverage Report: β
|
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.
Tested with a LARGE_ACCOUNT_THRESHOLD
modified to 5. Observed the API search being correctly used for large accounts and the queries being used for small accounts. In both cases, the search renders results and does not get stuck in infinite loading state.
Edit: Though it looks like e2es got aborted before they finished.
"Large" Account Search Behavior | "Small" Account Search Behavior |
---|---|
Screen.Recording.2024-04-04.at.12.55.36.PM.mov |
Screen.Recording.2024-04-04.at.12.56.40.PM.mov |
@bnussman-akamai Correct me if I am wrong, but I think we want to test with an actual large account here because of the time it take to query and calculate 1500+ Linodes (therefore the time isLargeAccount remains |
Or set |
|
gotcha thanks for confirming π moving on π |
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.
Functional search for non-large accounts β
Functional search for large accounts (tested by reducing LARGE_ACCOUNT_THRESHOLD
to 5 locally and comparing functionality on this branch compared to develop
) β
Description π
The Bug π
enabled: false
now markisLoading
astrue
. It use to beisLoading
false
when a query was disabled.!isLargeAccount
inSearchLanding.tsx
. The queries will be enabled for a split second while we loadisLargeAccount
because!undefined
istrue
Target release date ποΈ
Please specify a release date to guarantee timely review of this PR. If exact date is not known, please approximate and update it as needed.
How to test π§ͺ
As an Author I have considered π€