[I] [Bug] rmq.group.update accepts delaySeconds, reports success, and stores nothing [rocketmq-dashboard]

["iloveeyjafjalla (via GitHub)" <gi...@apache.org>]

iloveeyjafjalla opened a new issue, #7014:
URL: https://github.com/apache/rocketmq-dashboard/issues/7014

   ## Summary
   
   `rmq.group.update` accepts `delaySeconds` (schema `type: integer, minimum: 0`) and reports the mutation as executed, but **no layer applies or stores it**: the broker's `SubscriptionGroupConfig` has no delay field, `RocketMQAdminClientImpl.updateConsumerGroup` forwards only the retry limit, and `persistConsumerGroup` writes no delay column. A caller (human or MCP client) believes the delay changed; the next read still reports the measured value.
   
   ## Why
   
   - Input: `server/src/main/resources/tool-catalog/tools/group.yaml` (`rmq.group.update` input declares `delaySeconds`).
   - Mapping: `GroupInput.toConsumerGroupVO()` / `mergeWith()` copy it into the VO (`.../contract/group/GroupInput.java:33-48`).
   - Provider: `RocketMQAdminClientImpl.updateConsumerGroup` sets only `retryMaxTimes` on each broker's config (`:686-731`) and `persistConsumerGroup` stores `consumeType`/`messageModel`/`maxRetry` only (`:896-919`).
   - The console agrees that it is not writable: it renders the delay read-only from live stats and never submits it.
   
   ## Impact
   
   A successful tool call (`EXECUTED`) states that a field was changed when it cannot be; the value is silently discarded. The same field is reported (read-only) by `rmq.group.detail`, so the plan/read pair looks consistent while the broker was never touched.
   
   ## Reproduction
   
   `ToolCatalogTest` → `rejectsDelaySecondsOnGroupUpdateBecauseNothingAppliesItTest` sends `{"instanceId": "instance-a", "groupName": "orders", "delaySeconds": 60}`:
   
   ```
   Expecting code to raise a throwable.   (the schema accepts it today)
   ```
   
   ## Expected
   
   The update tool does not advertise a field it cannot write; a call that tries to set it is rejected by the same schema validation every tool call passes through, and the measured delay stays available through `rmq.group.detail`.
   


-- 
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: commits-unsubscribe@rocketmq.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] [Bug] rmq.group.update accepts delaySeconds, reports success, and stores nothing [rocketmq-dashboard]

["github-actions[bot] (via GitHub) via commits" <co...@rocketmq.apache.org>]

github-actions[bot] commented on issue #7014:
URL: https://github.com/apache/rocketmq-dashboard/issues/7014#issuecomment-6536298091

   This issue has been automatically closed because there has been no activity for 7 days. If you believe this issue is still relevant, please reopen it with updated information.


-- 
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: commits-unsubscribe@rocketmq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] [Bug] rmq.group.update accepts delaySeconds, reports success, and stores nothing [rocketmq-dashboard]

["github-actions[bot] (via GitHub) via commits" <co...@rocketmq.apache.org>]

github-actions[bot] closed issue #7014: [Bug] rmq.group.update accepts delaySeconds, reports success, and stores nothing
URL: https://github.com/apache/rocketmq-dashboard/issues/7014


-- 
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: commits-unsubscribe@rocketmq.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org