unbridled-41 opened a new issue, #5998:
URL: https://github.com/apache/rocketmq-dashboard/issues/5998

   ### Studio Version
   branch: `rocketmq-studio` @ `7e7aa344`
   ### Runtime Environment
   Frontend tests: `cd web && npx vitest run 
src/services/messageService.test.ts`.
   ### Describe the Bug
   The mock filters DLQ groups with the raw term (`groupName.includes(search)`) 
while the endpoint trims it (`DLQService: search.trim()`) and compares 
case-insensitively (`RocketMQDLQProvider: 
groupName.toLowerCase().contains(...)`). In mock mode - the default for the 
shipped demo config - searching `ORDER` or a padded ` order ` returns nothing 
although the same search works in production; the sibling mocks (topics, 
groups, ACL rules) already lower-case their filters.
   ### Steps to Reproduce
   `listDLQGroups('instance-1','ORDER',1,20)` in mock mode: `{items: [], total: 
0}`; the same terms return `cg-order-processor` against the server.
   ### What Did You Expect to See?
   The same matches the endpoint returns.
   ### What Did You See Instead?
   An empty list.
   ### Impact
   The DLQ page cannot be exercised against its own fixture data in mock mode.
   ### Acceptance Criteria
   The mock normalises the term the way the endpoint does, 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]

Reply via email to