RockteMQ-AI commented on issue #1316: URL: https://github.com/apache/rocketmq-clients/issues/1316#issuecomment-5142227341
**Fix Spec Summary** A fix spec has been generated for this issue. **Proposed Fix:** Insert a call to `mustSyncSettingsToTargert(accessPointTarget)` at the top of `defaultClient.startUp()` (before the `initTopics` loop) in `golang/client.go`. This eagerly opens a telemetry session to the configured access point, ensuring the broker can push the initial `Settings` command and set `cli.inited = true` — even when no topics are pre-registered. **Change scope:** ~5 lines added to `defaultClient.startUp()` only. No public API changes. No behavioral change when topics ARE pre-registered (the telemetry session is idempotent). **Why this works:** The deadlock is caused by a circular dependency: telemetry stream requires topics → topics require telemetry → `inited` never becomes true. By opening the telemetry session eagerly against the access point, the circular dependency is broken. **Test plan:** Unit test `TestProducerStartWithNoTopics` + regression tests for existing behavior. Reply `/approve` to proceed with PR generation, `/revise <feedback>` to request changes, or `/reject` to decline. --- *Automated fix proposal by RockteMQ-AI* -- 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]
