ppkarwasz opened a new pull request, #779:
URL: https://github.com/apache/commons-io/pull/779

   > [!NOTE]
   > This PR depends on the fixes proposed in #778. It should not be marked as 
ready for review until that PR has been approved or rejected.
   
   `BoundedInputStream.available()` previously returned the underlying stream’s 
availability without applying the configured read limit. It now caps the 
reported value by the remaining bytes allowed by the bound.
   
   Additional changes:
   
   * Removed the `onMaxLength` call from `available()`, since `available()` 
does not consume data and cannot exceed the maximum count.
   * Reworked the `testAvailableAfterClose` and `testReadAfterClose` tests:
   
     * Old versions relied too heavily on `CharSequenceInputStream`’s specific 
behavior.
     * New parameterized tests cover all three typical cases of the underlying 
stream after close: no-op, return special value, or throw an exception.
   * Added a dedicated unit test for the corrected `available()` behavior.
   
   Before you push a pull request, review this list:
   
   - [x] I used AI to improve unit tests and documentation.
   - [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