You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now, pagination states do not take into account the current filtered type rows, which causes the table renders incorrectly if there are less filtered rows than previously (currentPage index will be out of bound).
How To Reproduce
Step 1: Go to Events tab and select Event Types (might need to enter credentials).
Step 2: Click on > on pagination to go to higher indexed page (perhaps page 4-5).
Step 3: Enter CPU Usage on top-left filter. This is a valid name of an available event type.
Step 4: See the bug - No row is shown, pagination shows incorrect state as in below screenshot.
What Is Expected
A single row with event type name CPU Usage and pagination shows 1 of 1 as in the screenshot below.
What Actually Happened
No row is shown, pagination shows incorrect state as in below screenshot.
The text was updated successfully, but these errors were encountered:
Related to #595
Right now, pagination states do not take into account the current filtered type rows, which causes the table renders incorrectly if there are less filtered rows than previously (currentPage index will be out of bound).
How To Reproduce
Step 1: Go to Events tab and select Event Types (might need to enter credentials).
Step 2: Click on
>
on pagination to go to higher indexed page (perhaps page 4-5).Step 3: Enter
CPU Usage
on top-left filter. This is a valid name of an available event type.Step 4: See the bug - No row is shown, pagination shows incorrect state as in below screenshot.
What Is Expected
A single row with event type name
CPU Usage
and pagination shows1 of 1
as in the screenshot below.What Actually Happened
No row is shown, pagination shows incorrect state as in below screenshot.
The text was updated successfully, but these errors were encountered: