TryBugHunt
cppScope errorHard

Stock status never reports items running out

BugFind the bug and fix the code

What it should do

stockStatus(quantities) returns "sold out" when every quantity is 0, "partly out" when only some are 0, and "in stock" otherwise. Example: stockStatus({5, 0, 2}) → "partly out"

What happens instead

stockStatus({5, 0, 2}) returns "in stock".

#include <string>
#include <vector>

std::string stockStatus(std::vector<int> quantities) {
    std::string status = "in stock";
    int total = 0;
    for (int q : quantities) {
        total += q;
        if (q == 0) {
            std::string status = "partly out";
        }
    }
    if (total == 0) status = "sold out";
    return status;
}

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 scope and closure bugs pattern

A variable shadowed in an inner block, or a reference to something that has gone out of scope.

What you'll practise

A hard C++ debugging exercise about scope and closure bugs: a variable shadowed in an inner block, or a reference to something that has gone out of scope.

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)

What went wrong: std::string status = "partly out"; inside the if creates a second variable called status that lives only inside those braces. It is set and then destroyed straight away, and the outer status keeps "in stock". The "sold out" line works because it assigns to the outer variable.

The fix: Drop the type so the line assigns to the existing variable: status = "partly out";

Remember: Copying a line like std::string status = ... into a nested block makes a new, hidden variable. When an assignment seems to be ignored, check whether it starts with a type name.

The pattern behind it: scope and closure bugs.

More scope and closure bugs to practise

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/04d21773-3dad-418a-82a2-f7ad19702610" title="Debugging challenge: Stock status never reports items running out" 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/04d21773-3dad-418a-82a2-f7ad19702610">TryBugHunt</a></p>