Wang1rrr opened a new issue, #6972: URL: https://github.com/apache/rocketmq-dashboard/issues/6972
### Description The offset-message topology guard compares the decoded broker endpoint with advertised endpoints as raw strings. Java expands the IPv6 address decoded from a message ID, while NameServer topology may advertise the same address in compressed, bracketed, or uppercase notation. The guard rejects these legitimate messages even though the address bytes and port match a broker in the selected topology. ### Reproduction Create an offset message ID for `2001:db8::1` port 10911 and advertise `2001:db8::1:10911` (or `[2001:db8::1]:10911`) in the mocked cluster's broker addresses. `BrokerTopologyGuards.isWithinKnownBrokerTopology` returns false because the decoded endpoint is `2001:db8:0:0:0:0:0:1:10911`. ### Expected behavior Equivalent IPv6 literal spellings should match the known broker endpoint. Different addresses and ports must remain rejected; hostnames should not trigger additional DNS resolution. ### Version `rocketmq-studio` at c34535db0819d02f68e50a856cb3d2614f0dc5dd. I plan a focused literal-normalization fix with positive and negative topology regression cases. -- 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]
