lenamonj opened a new pull request, #813:
URL: https://github.com/apache/commons-compress/pull/813

   `BlockLZ4CompressorOutputStream` threw `IndexOutOfBoundsException` from 
`rewriteLastPairs` when closed with nothing written: the method reads the first 
of the pairs it collected, and an empty stream has none. COMPRESS-650 fixed a 
different trigger of the same exception in 1.25.0; the empty stream still fails 
on master.
   
   The stream now emits the single zero token the LZ4 block format uses for 
empty input, which `BlockLZ4CompressorInputStream` decodes to zero bytes. 
Writing no bytes at all is not an option, since the input stream rejects a 
zero-length block as a premature end of stream.
   
   Test: `testEmptyInput`, red on master and green with the change. Default 
Maven goal green.
   
   - [x] Read the [contribution guidelines](CONTRIBUTING.md) for this project.
   - [x] Read the [ASF Generative Tooling 
Guidance](https://www.apache.org/legal/generative-tooling.html) if you use 
Artificial Intelligence (AI).
   - [x] I used AI to create any part of, or all of, this pull request. Which 
AI tool was used to create this pull request, and to what extent did it 
contribute? Claude (Anthropic) found the defect and drafted the fix and test; I 
reviewed them, reproduced the failure on a fresh clone of master, and ran the 
default Maven goal.
   - [x] Run a successful build using the default 
[Maven](https://maven.apache.org/) goal with `mvn`; that's `mvn` on the command 
line by itself.
   - [x] Write unit tests that match behavioral changes, where the tests fail 
if the changes to the runtime are not applied. This may not always be possible, 
but it is a best practice.
   - [x] Write a pull request description that is detailed enough to understand 
what the pull request does, how, and why.
   - [x] Each commit in the pull request should have a meaningful subject line 
and body. Note that a maintainer may squash commits during the merge process.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to