123123213weqw opened a new pull request, #7343: URL: https://github.com/apache/rocketmq-dashboard/pull/7343
Fixes #7283. `MetadataService.consumerGroupConfigurations` filtered the provider results with the raw caller-supplied name while the provider search internally trims via `normalizeFilter` — so a padded name (`" my-group "`, which the `rmq.group.detail` schema accepts with only `minLength: 1`) found the group in the search but failed the exact-match filter, raising **404 for an existing group**. A blank name likewise produced 404 instead of the 400 every sibling read path throws. It was the only name-based path not normalizing through `requireName` first. The method now normalizes with `requireName(name, "consumer group name")` before searching and matching — the exact fix the issue proposes — so a padded name resolves the same group as the trimmed one, and a blank name is rejected with 400 before any provider resolution. Three regression tests: a padded name exact-matches within provider search results (including a similarly-named sibling that must not leak in, and asserting the provider receives the trimmed search), a blank name rejects with 400 with no provider interaction, and the 404 message reports the normalized name. Suite 64/64. -- 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]
