rootvector2 opened a new pull request, #741: URL: https://github.com/apache/commons-collections/pull/741
`LinkedSubList.subList` validated the requested range against the parent list after adding the sublist offset rather than against the sublist itself, so a nested `subList` call with a negative `fromIndex` or a `toIndex` past the sublist size returned a writable view over parent elements outside the range (found by comparing nested sublist behavior with `java.util.LinkedList`, which throws `IndexOutOfBoundsException`); the fix range-checks against the sublist size before applying the offset, in both `AbstractLinkedList` and the `AbstractLinkedListJava21` copy, with a shared regression test in `AbstractListTest`. - [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 Code was used to help locate the defect and draft the fix and test; the change was reviewed and verified locally. - [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]
