Concurrency · interview question

A bug appears around semaphores, timeouts, and cancellation. What is the strongest first debugging move?

Multiple choiceMediumchapter-15-curatedpremiumconcurrencysemaphores-timeouts-and-cancellation

python

semaphore = asyncio.Semaphore(10)

async with semaphore:
    await asyncio.wait_for(fetch_order("ORD-1"), timeout=2.0)

Trace one concrete example, inspect the state transitions, and compare them to the intended rule before rewriting anything.Keep semaphores, timeouts, and cancellation implicit so the script stays short and hope the next engineer infers the rule.Delay clarity until production traffic reveals the edge case and then patch it under pressure.Solve the symptom with comments only and avoid changing the code shape around semaphores, timeouts, and cancellation.

Answer and explanation

Correct answer

A. Trace one concrete example, inspect the state transitions, and compare them to the intended rule before rewriting anything.

Why

That approach is reliable because it creates evidence. Unlimited concurrency often looks impressive in a demo and dangerous in production.

Test yourself on Concurrency

A free test with instant, explained results. No account needed.

Start free test

All Concurrency questions →

A bug appears around semaphores, timeouts, and cancellation. What is the strongest first debugging move?

Correct answer

Why

More Concurrency questions