X-LightYear opened a new issue, #7243: URL: https://github.com/apache/rocketmq-dashboard/issues/7243
## Problem `rmqctl/scripts/build-windows.ps1` uses `bin\\rmqctl.exe` as its default output, but a clean checkout does not contain the `bin` directory. ## Reproduction 1. Check out the `rocketmq-studio` development trunk on Windows. 2. From `rmqctl`, run `powershell -File scripts/build-windows.ps1`. ## Expected behavior The native Windows build creates its default output directory and produces `bin\\rmqctl.exe`. ## Actual behavior The script reaches `go build -o bin\\rmqctl.exe main.go` without creating `bin`, so Go cannot create the output file and the build fails on a fresh checkout. ## Root cause The script creates neither the parent directory of the user-supplied `-Output` path nor the default `bin` directory before invoking `go build`. ## Fix scope Create the output parent directory when it is non-empty, and keep a Linux-runnable script contract test that guards this ordering. ## Regression evidence The fix is based on the clean-checkout default path and protects the script contract with `rmqctl/scripts/build_script_test.go`. The local environment does not have Go installed, so the executable build test could not be run locally. Discovery baseline: `127c47b06a268cc74224d5f34c56ec7c36ac0d55` -- 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]
