TryBugHunt
javaOff-by-oneEasy

Latest scores list crashes when asked for the last two

BugFind the bug and fix the code

What it should do

lastScores(scores, k) returns the k most recent scores (the end of the list) in their original order, so lastScores([50, 60, 70, 80], 2) returns [70, 80].

What happens instead

lastScores([50, 60, 70, 80], 2) throws java.lang.IndexOutOfBoundsException: Index 4 out of bounds for length 4.

import java.util.*;

public class Main {
    static List<Integer> lastScores(List<Integer> scores, int k) {
        List<Integer> result = new ArrayList<>();
        for (int i = scores.size() - k; i <= scores.size(); i++) {
            result.add(scores.get(i));
        }
        return result;
    }
}

Test a custom input to verify an edge case (e.g. empty lists, negative numbers, duplicates).

⏱️0:00
Hints
🏆 0 hints = Flawless Solve
Think & Test Cooldown
2:00 remaining

Take a moment to read the bug symptom and trace the code with Run & Check before unlocking Hint 1.

Hint 2
Unlocks after Hint 1
Hint 3
Unlocks after Hint 2

This bug belongs to the off-by-one errors pattern

The loop that runs one time too many, the slice that drops the last item, the index that starts in the wrong place.

What you'll practise

An easy Java debugging exercise about off-by-one errors: the loop that runs one time too many, the slice that drops the last item, the index that starts in the wrong place.

The checks your fix must pass

Signs of this kind of bug

Spoiler: why this bug happens(try it first; the hints get warmer one at a time)

A list of size n has valid indexes 0 to n - 1. The loop condition i <= scores.size() lets i reach n itself, and scores.get(n) is one step past the last element, so ArrayList throws IndexOutOfBoundsException on the final pass. The start index, size - k, is correct; only the stopping condition is wrong. When a loop walks up to the end of a list or array, the condition is almost always i < size, not i <=. If the exception message says "Index N out of bounds for length N", the index equals the length, which is the classic sign of an inclusive upper bound that should be exclusive.

The pattern behind it: off-by-one errors.

More off-by-one errors to practise

Seen this error in your own code?

Embed this challenge on your site

Paste this into any web page or blog post. Visitors fix the bug right there, in their browser.

<iframe src="https://trybughunt.com/embed/2be71441-575e-49a9-825d-6b074ab54cf9" title="Debugging challenge: Latest scores list crashes when asked for the last two" width="100%" height="580" loading="lazy" style="border:1px solid #d4d4d8;border-radius:12px;max-width:760px"></iframe>
<p style="font-size:14px">Debugging challenge from <a href="https://trybughunt.com/challenges/2be71441-575e-49a9-825d-6b074ab54cf9">TryBugHunt</a></p>