Aias00 opened a new pull request, #4503:
URL: https://github.com/apache/rocketmq-dashboard/pull/4503

   ### Which Issue(s) This PR Fixes
   
   - Fixes #4502
   
   ### Brief Description
   
   - Normalize client-diagnostics NameServer addresses with the same parser 
used by registry writes.
   - Require an exact registered endpoint before invoking the client provider 
or admin-client cache.
   - Return 404 for unknown endpoints while preserving existing cluster/type 
filters and the Clients-page API contract.
   - Add regression coverage for normalized registered endpoints and 
fail-closed unknown endpoints.
   
   ### How Did You Test This Change?
   
   - `cd server && mvn -B -ntp 
-Dtest=ClientControllerTest,ClientServiceTest,NameserverRegistryServiceTest,RocketMQClientProviderTest,MqAdminExtFactoryTest
 test` — 69 tests passed; Checkstyle 0 violations.
   - `cd server && mvn -B -ntp -Dsurefire.rerunFailingTestsCount=2 test` 
against a fresh isolated MySQL 8 schema — 2416 tests passed; Checkstyle 0 
violations. The temporary schema was removed after verification.
   - `cd server && mvn -B -ntp -DskipTests package` — passed.
   - `git diff HEAD^ --check` — passed.
   - Independent read-only review — 0 findings.
   
   ### Checklist
   
   - [x] One coherent change; unrelated modifications are not bundled in
   - [x] Commit subject follows Conventional Commits (`feat:` / `fix:` / 
`refactor:` / `chore:` / `docs:` / `perf:`)
   - [x] Tests added or updated for non-trivial changes, test methods named 
`...Test`
   - [x] New UI text has both Chinese and English entries under `web/src/i18n/` 
(no UI change)
   - [x] Architecture constraints stay green (`mvn test` runs the ArchUnit 
checks)
   - [x] New source files carry the ASF license header (no new source files)
   - [x] Documentation touched where behaviour changed (no documentation change 
required)


-- 
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