Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: tukaani-project/xz-java
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v1.11
Choose a base ref
...
head repository: tukaani-project/xz-java
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v1.12
Choose a head ref
  • 7 commits
  • 10 files changed
  • 1 contributor

Commits on Nov 19, 2025

  1. CI: Add missing SPDX tags

    Larhzu committed Nov 19, 2025
    Configuration menu
    Copy the full SHA
    9a755ec View commit details
    Browse the repository at this point in the history
  2. SHA256SUMS: Add 1.11 files

    Larhzu committed Nov 19, 2025
    Configuration menu
    Copy the full SHA
    e52d9ad View commit details
    Browse the repository at this point in the history

Commits on Jan 17, 2026

  1. Fix ArrayCache usage with LZMAInputStream

    Add a missing initialization to LZDecoder's constructor. The same
    initialization is done in LZDecoder.reset(). LZMA2InputStream
    always calls it before decoding anything, thus this bug didn't break
    LZMA2 decoding. However, LZMAInputStream has no reason to call
    LZDecoder.reset(), and thus the missing initialization in the
    constructor meant that ArrayCache didn't work with LZMAInputStream.
    
    Fixes: c5569e4 ("Add ArrayCache support to LZMA and LZMA2 coders, part 1.")
    Fixes: #23
    Larhzu committed Jan 17, 2026
    Configuration menu
    Copy the full SHA
    12c75fd View commit details
    Browse the repository at this point in the history

Commits on Mar 1, 2026

  1. Fix ArrayIndexOutOfBoundsException in the LZMA/LZMA2 encoder

    The extra size constant from UnalignedLongLEMatchLengthFinder didn't take
    effect as intended. This could result in ArrayIndexOutOfBoundsException.
    Frequent calls to flush() increased the likelyhood of hitting the bug
    but it could be triggered without flushing too:
    
        ant clean jar
        head -c12853521 /dev/zero \
            | java -ea -jar build/jar/XZEncDemo.jar > /dev/null
    
    The bug is present in versions 1.10 and 1.11. If one cannot upgrade,
    one should set the property org.tukaani.xz.MatchLengthFinder=Basic
    which disables UnalignedLongLEMatchLengthFinder. Example:
    
        head -c12853521 /dev/zero \
            | java -Dorg.tukaani.xz.MatchLengthFinder=Basic \
                   -jar build/jar/XZEncDemo.jar > /dev/null
    
    Fixes: 9fd7bc0 ("Add MatchLength.EXTRA_SIZE and use it in LZEncoder")
    Fixes: #24
    Larhzu committed Mar 1, 2026
    Configuration menu
    Copy the full SHA
    ac1aeb1 View commit details
    Browse the repository at this point in the history
  2. Refactor EXTRA_SIZE to getExtraSize()

    It's simpler code.
    Larhzu committed Mar 1, 2026
    Configuration menu
    Copy the full SHA
    0ecee25 View commit details
    Browse the repository at this point in the history
  3. Update NEWS.md for 1.12

    Larhzu committed Mar 1, 2026
    Configuration menu
    Copy the full SHA
    3061152 View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    107a519 View commit details
    Browse the repository at this point in the history
Loading