Chained encoder does not produce the same result as the lz4 cli when chaining is enabled about k4os.compression.lz4 HOT 4 OPEN

Is output compatible?
Can it compressed with one and decompress with the other?
If yes, then this might interesting but low priority.

I wrote chaining code myself (just from spec), so it might behave a little bit differently.
Also, it can use x86 or x64 encoder (which do produce different results), so this is another thing to keep in mind.

So, my question is, regardless being different - is it compatible?

from k4os.compression.lz4.

Yes, they seem compatible. At lease from the set of files that I have tested. The lz4 cli seem to be able to decompress the encoded files.

I found this when I was implementing #14. The implementation is here:
https://gist.github.com/rmja/98dc7e0576c933faa0a75629b46af71c

For this I created a bunch of different random files for testing and found the issue that way.

from k4os.compression.lz4.

What about sizes?

from k4os.compression.lz4.

They are not the same size. It seems as if this library produces a 1 byte smaller file in the tests that I have made. This is a diff from the last block:

The highlighted bytes are the block header. This library produces a length of 0x00001F65 bytes and the cli produces 0x00001F66 bytes.

The following is the diff within the block:

It is somewhere in the middle of the block.

from k4os.compression.lz4.