Resolve "blissdata: slicing of counter stream falls into IndexNoMoreThereError"
requested to merge 4389-blissdata-slicing-of-counter-stream-falls-into-indexnomorethereerror into master
Closes #4389 (closed)
When failing to read a stream index, blissdata was then checking the stream length to see whether that index was not published yet or already discarded.
Because both operations were not atomic, the length could increase in between and lead to incorrect conclusion -> IndexNoMoreThereError instead of IndexNotYetThereError
Edited by Lucas Felix