Aias00 opened a new issue, #835: URL: https://github.com/apache/rocketmq-dashboard/issues/835
### What happened? InMemoryAuditRepository sorts audit records by timestamp descending, but the comparator returns 0 whenever either side has a null timestamp. That means a record without timestamp can keep its current position relative to newer timestamped records, so the audit log order becomes dependent on ConcurrentHashMap iteration order instead of the expected newest-first order. ### Expected behavior Audit records with timestamps should be ordered by timestamp descending. Records without timestamps should be placed after timestamped records with deterministic behavior. ### Why this matters This affects the Studio operations audit view under BASE-01 login and permission auditing. Audit logs should be predictable when mixed data or partially populated records exist. ### Candidate fix Use a null-safe timestamp comparator and add repository coverage for mixed timestamp/null timestamp records. -- 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]
