You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, this test is being partially ported from Node.js, where I did something similar a while ago. Node.js uses zlib. The hex resulting from that binary is this:
Both of these do appear to be valid, and both decompress fine with other tools.
Addendum: this is with the "default" quality setting (zlib level 6 or 7 (whichever it is), default flate2). Changing flate2 to "best" does not appear to make a difference.
The text was updated successfully, but these errors were encountered:
This might best be an issue for miniz-oxide? That's just a straight port of miniz though, so I'm not sure that much can be done. I'd recomend enabling the zlib backend if you get better results with that
Yeah this would likely be an issue with miniz_oxide, provided you are sure you are providing the same input data. The output ought to be very similar, especially for a short input like this. Difference between default and max compression levels wont come into play when compressing a small file like this.
Hi there, I'm using flate2 with the default backend (apparently miniz_oxide) via the
async_compression
crate.I have a "file" like this (in a test):
flate2 appears to compress that to the following (hex dump from binary):
However, this test is being partially ported from Node.js, where I did something similar a while ago. Node.js uses zlib. The hex resulting from that binary is this:
The zlib one here is quite a bit smaller.
Both of these do appear to be valid, and both decompress fine with other tools.
Addendum: this is with the "default" quality setting (zlib level 6 or 7 (whichever it is), default flate2). Changing flate2 to
"best"
does not appear to make a difference.The text was updated successfully, but these errors were encountered: