unbridled-41 opened a new issue, #5992: URL: https://github.com/apache/rocketmq-dashboard/issues/5992
### 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 The rule dialog's 主体 Select is fed by the same state as the paged Users tab (`pageAclUsers` with the current page and the Users-tab keyword). The field is required and has no free-text mode, so only the ≤20 users of the loaded page can be submitted - further narrowed by whatever was typed into the Users search box (a keyword matching nothing leaves zero options). On a deployment with more than one page of ACL users, a rule cannot be created for any principal outside that page. The same page-scoped state also answers the admin badge, so an admin on page 2 never gets one. ### Steps to Reproduce 1. Have more than 20 ACL users. 2. Add a rule and open 主体: only the first page's users are listed; type a keyword into the Users tab and the list shrinks further. ### What Did You Expect to See? Every user of the instance. ### What Did You See Instead? The loaded page only. ### Impact A core write path on the ACL page is unusable beyond the first page of users. ### Acceptance Criteria The picker (and the admin badge) read the complete directory, the edited rule's principal stays selectable, and a regression test pins it. **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]
