Frun1na opened a new issue, #4943: URL: https://github.com/apache/rocketmq-dashboard/issues/4943
### Before Creating the Bug Report - [x] I have searched the [open issues](https://github.com/apache/rocketmq-dashboard/issues) of this repository and believe that this is not a duplicate. - [x] This is a defect in RocketMQ Studio, not a usage question and not a defect in another Apache RocketMQ repository. - [x] I can reproduce this on the current `master` branch, or I have stated the exact version I am running below. ### Studio Version branch: `rocketmq-studio` git commit id: `1ef5d860` (upstream tip at the time of the report) deployed as: built from source ### Runtime Environment Verified by code tracing and unit tests on `rocketmq-studio` @ `1ef5d860` (vitest for `web/`, JUnit for `server/`), not against a specific browser or deployment. ### Connected RocketMQ Cluster Not cluster-specific: the defect lives in the code path and reproduces on any deployment where the trigger condition below holds. ### Describe the Bug Commit 1ef5d860 (#4855) changed `server/src/main/resources/tool-catalog/tools/proxy.yaml` but did not regenerate `rmqctl/internal/catalog/catalog_gen.go`. `make -C rmqctl ci` therefore fails at `catalog-verify` (`cataloggen: internal/catalog/catalog_gen.go is stale`) on the current tip. ### Steps to Reproduce ``` git checkout 1ef5d860 make -C rmqctl catalog-verify # cataloggen: internal/catalog/catalog_gen.go is stale; run make catalog-generate ``` ### What Did You Expect to See? `make -C rmqctl ci` is green on the tip. ### What Did You See Instead? The generated catalog still carries the old digest and `PROXY_DISCOVERY` for the two proxy tools. -- 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]
