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

Server-side Pagination: Sorting: Cluster Dash: Newly created resource populates at bottom of list; sort order preference ignored #11498

Open
Tracked by #8527
yonasberhe23 opened this issue Jul 19, 2024 · 4 comments
Assignees
Labels
area/performance area/server-side-pagination kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this size/0.5 Size Estimate 0.5 status/backport-candidate
Milestone

Comments

@yonasberhe23
Copy link
Contributor

Setup

  • Rancher version: v2.9-head
  • Rancher UI Extensions:
  • Browser type & version:

Describe the bug
Newly created resource populates at the bottom of the resource list (config maps, secrets) when server-side pag is enabled; sorting preference is ignored.

To Reproduce

  1. go to Global settings > feature flags > enable ui-sql-cache
  2. go to Global settings > performance > enable `Server-sdie Pagination'
  3. go to cluster dash
  4. click ConfigMaps in side nav
  5. notice secrets list is sorted by name by default
  6. create config map
  7. notice newly created secret is not sorted correctly

Result
sort order is preference is ignored.

Expected Result
sort order is not ignored.

Screenshots
https://github.com/user-attachments/assets/c6df7482-1225-43bc-889e-7bb239633ed5

Additional context

@github-actions github-actions bot added the QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this label Jul 19, 2024
@richard-cox
Copy link
Member

Changes to the collection should result in a re-pagination request, though this area is in flux (handling updates to existing lists)

@richard-cox richard-cox added this to the v2.10.0 milestone Jul 22, 2024
@richard-cox
Copy link
Member

/backport v2.9.next1

@gaktive
Copy link
Member

gaktive commented Nov 1, 2024

/backport v2.10.1

@richard-cox richard-cox added the size/0.5 Size Estimate 0.5 label Nov 8, 2024
@codyrancher codyrancher self-assigned this Dec 16, 2024
codyrancher added a commit to codyrancher/dashboard that referenced this issue Dec 16, 2024
Fixes rancher#11498

We weren't forcing an update of the cached page resource which meant the newly creating item wasn't necessarily showing up or wasn't showing up in the correct order.
codyrancher added a commit to codyrancher/dashboard that referenced this issue Jan 7, 2025
Fixes rancher#11498

We weren't forcing an update of the cached page resource which meant the newly creating item wasn't necessarily showing up or wasn't showing up in the correct order.
codyrancher added a commit to codyrancher/dashboard that referenced this issue Jan 7, 2025
Fixes rancher#11498

We weren't forcing an update of the cached page resource which meant the newly creating item wasn't necessarily showing up or wasn't showing up in the correct order.
@codyrancher
Copy link
Contributor

My PR is no longer necessary. It looks like @richard-cox's pr1 or pr2 has resolved this issue in master.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/performance area/server-side-pagination kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this size/0.5 Size Estimate 0.5 status/backport-candidate
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants