Fix: Return empty list when range exceeds collection size #752
+22
−0
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When using range notation in API pagination (e.g.,
tree=jobs[name]{11000,12000}), if the fromIndex exceeds the actual collection size,Range.apply()previously causedList.subList()to throwIllegalArgumentException: fromIndex > toIndex.This fix adds a bounds check before calling
subList(min, s.size()). Whenmin >= s.size(), the method now returns an empty list instead of throwing.This allows Jenkins API clients to paginate beyond the end of a collection and receive an empty result, which is the expected behavior when iterating through pages of data.
Testing done
Submitter checklist