Fix typo in directory name *Documentation* #560
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Reported-by: Thomas Kreitler <kreitler@molgen.mpg.de>
|
Not tested on theinternet |
pmenzel
added a commit
that referenced
this pull request
Feb 26, 2019
[Release notes][1]: > This is maintenance release, mainly triggered by issue #560. > > #560 is a data corruption that can only occur in v1.8.2, at level 9 > (only), for some "large enough" data blocks (> 64 KB), featuring a > fairly specific data pattern, improbable enough that multiple cpu > running various fuzzers non-stop during a period of several weeks where > not able to find it. Big thanks to @Pashugan for finding and sharing a > reproducible sample. > > Due to this fix, v1.8.3 is a recommended update. > > A few other minor features were already merged, and are therefore > bundled in this release too. > > Should lz4 prove too slow, it's now possible to invoke --fast=# command, > by @jennifermliu . This is equivalent to the acceleration parameter in > the API, in which user forfeit some compression ratio for the benefit of > better speed. > > The verbose CLI has been fixed, and now displays the real amount of time > spent compressing (instead of cpu time). It also shows a new indicator, > cpu load %, so that users can determine if the limiting factor was cpu > or I/O bandwidth. > > Finally, an existing function, LZ4_decompress_safe_partial(), has been > enhanced to make it possible to decompress only the beginning of an LZ4 > block, up to a specified number of bytes. Partial decoding can be useful > to save CPU time and memory, when the objective is to extract a limited > portion from a larger block. [1]: https://github.com/lz4/lz4/releases/tag/v1.8.3
Sign in
to join this conversation on GitHub.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
After over a year of maturation this patch looks like it can be merged and it will blow up our branch graph nicely and make us look as we have real complicated branch concepts which the average user can't understand.