carloea2 opened a new issue, #8223: URL: https://github.com/apache/texera/issues/8223
### Current behavior The queue replaces the key lookup when the same subqueue is registered twice, but its priority group still contains the original queue. New messages then increase the total count while becoming unreachable to consumers. Before: duplicate key -> lookup points to an orphan queue -> total count includes an unreachable message After: duplicate key -> existing queue is preserved -> all messages remain selectable ### Steps to reproduce On current `main`, register a subqueue, enqueue one message, register the same key again, and enqueue a second message. The first message can be read, but `peek()` then returns `None` while the reported total size remains 1. Observed on `70c21145887920528d7d5540e3fb790b43e8b759`: ```text first_registration=None duplicate_returned_old=True reported_total=2 reported_key=1 first_get=first after_first_total=1 peek_after_first=None ``` ### Expected behavior Registering an existing key should preserve and return the registered queue so previously and subsequently enqueued messages remain reachable. -- 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]
