PR title: "Fix off-by-one in PaginatedView.next_page" PR size: 18 LoC across 2 files (Django app) Author: senior backend engineer, has 200+ commits to this repo Diff (excerpt):
# pagination.py
- start = (page - 1) * page_size
- end = page * page_size
- return items[start:end]
+ start = (page - 1) * page_size
+ end = min(page * page_size, len(items))
+ return items[start:end]Summary: "Fixes off-by-one in PaginatedView.next_page that could skip
the last item when len(items) % page_size == 1. Patch correctly clamps
end to len(items). The original test missed this boundary case."
Inline comments (1):
pagination.py:47: "Consider adding a unit test for the boundary conditionlen(items) == page_size + 1to lock this in."
Suggested reviewer: @django-pagination-codeowner
Total comments: 2 (1 summary + 1 inline)
Bot did fine. Author merged after adding the suggested test. The "unit test" suggestion was a real value-add — author confirmed they hadn't thought of that edge case.
One mild surprise: bot's summary specifically called out which edge case the test would cover. That's better than the average human review comment.