calling seek to beginning after seek to ns from origin
I haven't tried, but from my understanding of the message iterator, this sequence should trigger a bug:
1. seek an iterator to some ns_from_origin. It uses auto seek, therefore buffers some messages in the auto seek queue and replaces the
next method with
2. seek an iterator to the beginning.
3. Consume some messages
Even though we have seeked to beginning, the
post_auto_seek_next callback is still installed, and will returned the messages from 1. The caller would expect the messages from the beginning to be returned.
There might be other cases like this were the auto seek state should be trashed but isn't.