Clickin opened a new pull request, #836: URL: https://github.com/apache/commons-compress/pull/836
JIRA: https://issues.apache.org/jira/browse/COMPRESS-645 `TarArchiveInputStream.getNextEntry()` returns `null` for non-TAR input shorter than one record, so it looks like an empty archive. A gzipped TAR holding one small file is only 113 bytes. A partial record after a valid entry is dropped the same way. Non-TAR input of 512 bytes or more already fails while parsing the header, and `TarFile` already throws `EOFException` for short input. `readRecord()` now throws `EOFException` when a read returns some bytes but fewer than a record, unless the EOF marker has already been read. The message follows the other "Truncated TAR archive" messages in the class. Zero-byte input is still an empty archive, an archive without an EOF marker still reads, and padding or garbage after the EOF record is still ignored. There is no format detection and no change to checksum handling. `TarArchiveInputStreamTest` covers the rejected and the unchanged cases. Without the change, three cases fail: 1-byte input, 511-byte input, and a partial record after an entry. The default `mvn` build passes on JDK 17, and `TarArchiveInputStreamTest` passes on JDK 8. - [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? OpenAI GPT-6 Astra wrote the change and the tests; Claude Opus 5.5 reviewed them and wrote this description. The commit carries `Generated-by` and `Assisted-By` trailers. - [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. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
