RockteMQ-AI commented on issue #1408: URL: https://github.com/apache/rocketmq-clients/issues/1408#issuecomment-6290418381
**Issue Evaluation** Category: `type/bug` | Status: **Confirmed** The reported issue has been verified against the current codebase. **Root Cause:** Two compounding issues: 1. `LitePushConsumer::start` passes a telemetry command sender to `PushConsumer::start_with_telemetry`, but that method ignores the argument (`_telemetry_command_tx`) and creates its own channel. The lite handler's sender is dropped immediately, causing the handler to exit. 2. Startup does not wait for server-pushed lite settings, and quota `0` is treated as "unlimited" instead of "no quota granted yet". **Impact:** `LitePushConsumer` in the Rust client completely ignores server-side lite subscription quota. Applications can subscribe to unlimited lite topics, violating the quota granted by the server. The `NotifyUnsubscribeLiteCommand` is also never handled, so the client retains lite topics even after server notification to drop them. **Severity:** high — The lite subscription feature is non-functional in the Rust client. The Java client is not affected. **Scope:** `rust/src/push_consumer.rs` — `start_with_telemetry` method and `LitePushConsumer` telemetry handler. An automated fix proposal will be generated. Reply `/approve` to proceed with PR generation. --- *Automated evaluation 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]
