TryBugHunt
goOff-by-oneMedium

Price lookup fails on a one-item list

BugFind the bug and fix the code

What it should do

findPrice(sorted, target) uses binary search on an ascending list of prices and returns the index of target, or -1 if it is not there. findPrice([1, 3, 5, 7, 9], 9) returns 4.

What happens instead

findPrice([4], 4) returns -1, and findPrice([1, 3, 5, 7, 9], 9) also returns -1.

package main

func findPrice(sorted []int, target int) int {
    lo, hi := 0, len(sorted)-1
    for lo < hi {
        mid := (lo + hi) / 2
        if sorted[mid] == target {
            return mid
        } else if sorted[mid] < target {
            lo = mid + 1
        } else {
            hi = mid - 1
        }
    }
    return -1
}

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 Go 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)

Here hi is the last valid index, so the search range is inclusive on both ends, and a range with lo equal to hi still holds one candidate. The condition lo < hi stops the loop exactly when one item is left, so that item is never checked. A single-item list is the clearest case: lo and hi are both 0 and the loop never runs. With an inclusive hi the loop must be lo <= hi; with hi = len (exclusive) you would use lo < hi and set hi = mid. Pick one style and keep all three parts consistent.

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/39a23c79-a150-4ae6-b704-570eab02c72d" title="Debugging challenge: Price lookup fails on a one-item list" 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/39a23c79-a150-4ae6-b704-570eab02c72d">TryBugHunt</a></p>