[Bug] Reader.hasMessageAvailable return wrong value after seeking by timestamp with startMessageIdInclusive #23501
Closed
3 tasks done
Labels
type/bug
The PR fixed a bug or issue reported a bug
Search before asking
Read release policy
Version
master
Minimal reproduce step
reader.seek(System.currentTimeMillis());
reader.hasMessageAvailable()
What did you expect to see?
In the step 3,
reader.hasMessageAvailable()
should return false cause there has no message to readWhat did you see instead?
reader.hasMessageAvailable()
return trueAnything else?
No response
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: