"error in roaringArray.readFrom: did not find expected serialCookie in header" about roaring HOT 4 CLOSED

Sorry but I am closing this issue as it is invalid.

You must show that your inputs follow the Roaring specification which explicitly documented:
https://github.com/RoaringBitmap/RoaringFormatSpec

As I wrote in the previous issue, badger use their own custom implementation: https://github.com/dgraph-io/sroar

That is fine but if you encounter format incompatibilities with standard Roaring bitmaps, then reach out to Dgraph.

We only support the roaring library and the standard Roaring format.

You can use customized implementations but we will not support it.

You can, of course, suggest pull requests to use with new functionality to accommodate your needs.

Of course, it is possible that we have bugs. If so, please provide analysis and test cases.

Your bug report should not involve serialized data by another library we do not support. If this other library was meant to produce standard Roaring bitmaps, then issue a bug report with them, using the specification.

If you have standard compliant inputs that we fail to deserialize properly, please demonstrate that your serialized data is compliant with our format and open a bug report with such data. Note that I consider such bugs unlikely.

from roaring.

Agreed. But the point is whatever values we are storing in the bitmap, we are storing the same in db as []byte and fetching the same []byte from memory and writing it back in the bitmap. If the values stored in the bitmap are valid, it should not give an error. @lemire

from roaring.

Then you should be able to reproduce the issue using a standard compliant input. Please make sure to document how it follows the standard. Provide reproducible code.

from roaring.

Let me elaborate...

If the values stored in the bitmap are valid

That's the critical part. You have to prove that it is the case. You have to see whether they are standard compliant. Most likely, they are not.

from roaring.