nsweeting opened a new issue, #3178:
URL: https://github.com/apache/kvrocks/issues/3178

   ### Search before asking
   
   - [x] I had searched in the 
[issues](https://github.com/apache/kvrocks/issues) and found no similar issues.
   
   
   ### Version
   
   We are seeing the issue with version 2.13.0 (also apparent in 2.10.1).
   
   
   ### Minimal reproduce step
   
   ```
   127.0.0.1:6666> XGROUP CREATE test test-group $ MKSTREAM
   OK
   127.0.0.1:6666> XADD test * id foo
   "1758038326450-0"
   127.0.0.1:6666> XLEN test
   (integer) 1
   127.0.0.1:6666> XREADGROUP GROUP test-group test-consumer COUNT 10 BLOCK 
1000 STREAMS test >
   1) 1) "test"
      2) 1) 1) "1758038326450-0"
            2) 1) "id"
               2) "foo"
   127.0.0.1:6666> XPENDING test test-group IDLE 30000 - + 10 test-consumer
   1) 1) "1758038326450-0"
      2) "test-consumer"
      3) (integer) 0
      4) (integer) 0
   127.0.0.1:6666> XPENDING test test-group IDLE 30000 - + 10 test-consumer
   1) 1) "1758038326450-0"
      2) "test-consumer"
      3) (integer) 0
      4) (integer) 0
   127.0.0.1:6666> XPENDING test test-group IDLE 30000 - + 10 test-consumer
   1) 1) "1758038326450-0"
      2) "test-consumer"
      3) (integer) 0
      4) (integer) 0
   ```
   
   
   ### What did you expect to see?
   
   The XPENDING command should return the correct idle time plus delivered 
count for a given message. You can see the correct behaviour when executed on 
redis.
   
   ```
   127.0.0.1:6379> XPENDING test test-group IDLE 30000 - + 10 test-consumer
   1) 1) "1758038123094-0"
      2) "test-consumer"
      3) (integer) 36973
      4) (integer) 1
   ```
   
   ### What did you see instead?
   
   The XPENDING command always returns 0 for both idle time and read count.
   
   ### Anything Else?
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [ ] I'm willing to submit a PR!


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

Reply via email to