You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@rocketmq.apache.org by "Aias00 (via GitHub)" <gi...@apache.org> on 2026/08/03 09:11:56 UTC

[I] [Bug] Audit log ordering is unstable when records have missing timestamps [rocketmq-dashboard]

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

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


Re: [I] [Bug] Audit log ordering is unstable when records have missing timestamps [rocketmq-dashboard]

Posted by "lizhimins (via GitHub)" <gi...@apache.org>.
lizhimins commented on issue #835:
URL: https://github.com/apache/rocketmq-dashboard/issues/835#issuecomment-5177585329

   Superseded by #955 (merged into rocketmq-studio as 002449b): audit records are persisted to MySQL and ordered via SQL ORDER BY operated_at DESC, so the null-timestamp ordering scenario no longer exists.


-- 
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] Audit log ordering is unstable when records have missing timestamps [rocketmq-dashboard]

Posted by "lizhimins (via GitHub)" <gi...@apache.org>.
lizhimins closed issue #835: [Bug] Audit log ordering is unstable when records have missing timestamps
URL: https://github.com/apache/rocketmq-dashboard/issues/835


-- 
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