zmuxuny opened a new issue, #6749: URL: https://github.com/apache/rocketmq-dashboard/issues/6749
### 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 rocketmq-studio a92c23144408cdf5729707050e9ecd9b75f1bad0, rmqctl ### Runtime Environment Linux, Go1.27.1. Deterministic CLI configuration-generation test with temporary working directories. No live endpoint or external agent invoked. ### Connected RocketMQ Cluster Not required: generated executable path is wrong before any server connection. ### Build Toolchain Go1.27.1, GOMAXPROCS=2, go test -p1 ./cmd ### Describe the Bug mcp config documents --command as the executable path but emits explicit relative paths unchanged. A desktop MCP client launched from another directory interprets ./rmqctl or bin/rmqctl relative to its own directory, so the generated configuration cannot start the selected local executable. ### Steps to Reproduce 1. From a directory containing a local rmqctl binary, generate: rmqctl mcp config --command ./rmqctl --instance-id example. 2. Use the generated command from a different working directory, as an external client may do. 3. Resolve the command: it now points under the client directory rather than the generation directory. ### What Did You Expect to See? Bind an explicitly supplied executable path to the generation directory, while leaving a bare command such as rmqctl to normal PATH lookup. Absolute paths should remain unchanged. ### What Did You See Instead? The snippet command stays ./rmqctl. Three deterministic red cases (./rmqctl, a relative path containing spaces, ../rmqctl) resolve to the wrong location after changing working directory. ### Additional Context Source rmqctl/cmd/mcp.go newMCPConfigCommand. Searched all-state issues/PRs for rmqctl relative command, executable path, mcp config command path. #6452/#6460 normalizes only the separate --config file argument; #5915/#5916 concerns a missing instance argument. Neither binds the executable selected by --command. The proposed fix reads no credential/config contents and does not launch any process. ### Are You Willing to Submit a Pull Request? - [x] Yes, I am willing to submit a pull request. -- 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]
