btlqql opened a new issue, #2256: URL: https://github.com/apache/rocketmq-dashboard/issues/2256
## Problem The instance-scoped Apache ACL 2.0 reader assumes that `listAcl` and every nested policy object are non-null. A broker returning a null top-level list or a response containing one null policy, policy group, entry, action, or source IP triggers an exception. The per-broker catch then discards every valid policy from that broker and marks the whole broker read as failed. ## Expected behavior Remote ACL reads should isolate malformed optional rows while preserving valid data: - a null policy list is treated as an empty successful response; - null policy, group, and entry rows are skipped; - null values inside actions and source IP lists are skipped; - valid sibling policies remain visible and the broker is not incorrectly reported as failed. ## Proposed scope Harden the Apache ACL read boundary and its REST conversion model, with focused tests for a null response and mixed valid/null nested rows. I searched current and historical issues and pull requests for null/partial Apache ACL broker responses and nested ACL policy rows. Earlier work handled null action/source-IP collections and established the read endpoint, but no existing issue or PR covers null response rows at these levels. The three target files also have no collision with any open `rocketmq-studio` PR. -- 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]
