RockteMQ-AI commented on issue #4608: URL: https://github.com/apache/rocketmq-dashboard/issues/4608#issuecomment-5751307515
**Issue Evaluation** Category: | Status: **Confirmed** The reported issue has been verified against the current codebase. **Root Cause:** In (line 143), the audit result is hardcoded as in the call, regardless of the actual returned by the broker. When the consume fails (, , , ), the audit timeline still shows . Additionally, when the provider throws (e.g., target client offline), the exception propagates before the audit record is written, so the failed attempt is silently lost. **Impact:** Operation audit timeline gives false-positive results for direct message consumption, undermining audit reliability. **Severity:** medium — affects audit correctness, not message delivery itself. **Related:** PR #4607 by the issue author provides a fix. --- *Automated evaluation by github-manager* -- 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]
