TryBugHunt
javaOff-by-oneMedium

Version 1.2.0.0 shortens to just 1

BugFind the bug and fix the code

What it should do

normalizeVersion(version) removes trailing ".0" parts from a version string, so normalizeVersion("1.2.0.0") returns "1.2" and "2.5.1" stays "2.5.1".

What happens instead

normalizeVersion("1.2.0.0") returns "1" instead of "1.2", and normalizeVersion("3.0") returns an empty string.

public class Main {
    static String normalizeVersion(String version) {
        String[] parts = version.split("[.]");
        int end = parts.length - 1;
        while (end > 0 && parts[end].equals("0")) {
            end--;
        }
        StringBuilder sb = new StringBuilder();
        for (int i = 0; i < end; i++) {
            if (i > 0) {
                sb.append(".");
            }
            sb.append(parts[i]);
        }
        return sb.toString();
    }
}

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

A medium 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)

The first loop finds end, the index of the last part to keep. That makes end an inclusive bound: parts[end] belongs in the result. The second loop then treats it as exclusive with i < end, so it always drops the last part it was supposed to keep. Even a version with no zeros, like 2.5.1, loses its last number. When one piece of code computes an index and another uses it, the meaning of that index (the last item, or one past the last item) has to be the same in both places. Naming it lastKept or keepCount makes the choice explicit.

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

More off-by-one errors to practise

Related errors

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/455bfeb3-7167-45d0-8564-2e7c0678c47e" title="Debugging challenge: Version 1.2.0.0 shortens to just 1" 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/455bfeb3-7167-45d0-8564-2e7c0678c47e">TryBugHunt</a></p>