The GitHub Actions job "CI" on rocketmq-dashboard.git/fix/deploy-readme-proxy-claim has failed. Run started by GitHub user unbridled-41 (triggered by unbridled-41).
Head commit for run: 745c39e068128ffbb2a61e036277be7c5ee3422b / unbridled-41 <[email protected]> docs(deploy): the demo producer and consumer do not go through the proxy The directory listing tells the reader that both bundled load generators connect via `proxy:8080`: ├── TraceProducer.java # 1 TPS 发送（带 Key），enableMsgTrace=true，经 proxy:8080 接入 └── TraceConsumer.java # Push 消费，enableMsgTrace=true，经 proxy:8080 接入 They are plain clients pointed at the NameServer: // deploy/rocketmq/clients/TraceProducer.java:7 String namesrv = System.getenv().getOrDefault("NAMESRV_ADDR", "nameserver:9876"); producer.setNamesrvAddr(namesrv); and `docker-compose.yml` passes `NAMESRV_ADDR: rmq-nameserver:9876` to both, i.e. nothing in the bundled traffic exercises the proxy. Its own comments say so ("直连 NameServer"), the skill documentation agrees, and no client reads a proxy or gRPC endpoint. A reader searching for proxy traffic in the demo therefore looks for something that does not exist. Verification: `grep -n "NAMESRV_ADDR\|setNamesrvAddr" deploy/rocketmq/clients/*.java deploy/rocketmq/docker-compose.yml` shows the NameServer address on every client and container; `grep -rn "proxy\|8080" deploy/rocketmq/clients/` returns nothing. Report URL: https://github.com/apache/rocketmq-dashboard/actions/runs/37990926918 With regards, GitHub Actions via GitBox
