unbridled-41 opened a new issue, #5996: URL: https://github.com/apache/rocketmq-dashboard/issues/5996
### Studio Version branch: `rocketmq-studio` @ `7e7aa344` ### Runtime Environment Frontend tests: `cd web && npx vitest run src/pages/instance/__tests__/AclPage.test.tsx`. ### Describe the Bug Both ACL inventories are server-paginated (page/pageSize with a server total), but eleven columns still carry antd in-memory sorters, so a header click reorders the loaded page only while the column's arrow claims the whole result set is sorted (with 40 rules, clicking 主体 sorts page 1 alphabetically and page 2 stays newest-first). The endpoints have no sort parameter, so the sorters promise something the page cannot deliver; the project is removing the same pattern from the other server-paginated tables (DLQ/message, #5335/#5295). ### Steps to Reproduce 1. Have more than one page of rules. 2. Click 主体: only the current page is reordered. ### What Did You Expect to See? No sorting affordance on a paged table with no server-side sort. ### What Did You See Instead? A sorted-looking column over an unsorted result set. ### Impact Operators draw wrong conclusions (e.g. "the newest rules are X") from a partial order. ### Acceptance Criteria The paged rule and user tables expose no in-memory sorters, with a regression test. **Corresponding PR:** #ISSUEPR# -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
