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

   ## Summary
   - add a guarded lifecycle executor SPI for Broker, NameServer, and Proxy 
operations
   - dispatch validated lifecycle requests through a configured 
deployment-owned executable
   - return typed lifecycle dispatch results to backend controllers and 
frontend services
   - document lifecycle adapter configuration and keep execution disabled by 
default
   
   Fixes #4311
   
   ## Verification
   - `cd server && env 
JAVA_HOME=/Users/aias/Library/Java/JavaVirtualMachines/openjdk-21.0.2/Contents/Home
 
PATH=/Users/aias/Library/Java/JavaVirtualMachines/openjdk-21.0.2/Contents/Home/bin:/opt/homebrew/bin:/usr/bin:/bin
 mvn -B -ntp 
-Dtest=ProcessLifecycleOperationExecutorTest,DefaultLifecycleProcessRunnerTest,ClusterServiceTest,ClusterControllerTest,NameServerControllerTest,ProxyControllerTest
 test` -> 113 tests, 0 failures, 0 errors
   - `cd web && npm test -- --run src/api/cluster.test.ts 
src/services/clusterService.test.ts` -> 2 files, 24 tests passed
   - `cd web && npm run build` -> passed
   - `cd web && npm run lint` -> exit 0, 10 existing warnings in unrelated files
   - `git diff --cached --check` -> passed
   
   ## Full-suite note
   - `cd server && env 
JAVA_HOME=/Users/aias/Library/Java/JavaVirtualMachines/openjdk-21.0.2/Contents/Home
 
PATH=/Users/aias/Library/Java/JavaVirtualMachines/openjdk-21.0.2/Contents/Home/bin:/opt/homebrew/bin:/usr/bin:/bin
 mvn -B -ntp test` currently fails in this local environment with 1 failure and 
2 errors caused by shared MySQL/dev schema state. The same three tests fail on 
a clean temporary worktree at `origin/rocketmq-studio` 
(`StudioApplicationTest`, `AuthServiceBootstrapIntegrationTest`, 
`QueryHistoryServiceIntegrationTest`), so this is not introduced by this branch.


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