[BUG] Incorrect handling of read receipts across multiple conversations in batch consumer #3441
Description
OpenIM Server Version
3.8.3
Operating System and CPU Architecture
Linux (AMD)
Deployment Method
Source Code Deployment
Bug Description and Steps to Reproduce
The current implementation of doSetReadSeq assumes that all messages in a batch belong to the same conversation. However, in practice, a single batch may contain read receipt messages (ContentType == HasReadReceipt) for multiple different conversationIDs.
This causes incorrect behavior when persisting read sequences (HasReadSeq) to the database: only the last conversation in the batch is processed, and all others are ignored.
Screenshots Link
No response