xAI

Verified interview challenge

Transactional store bug hunt

Find state-management bugs in a key-value store with nested transactions.

Unlock with Full Access

The challenge

The store supports reads, writes, deletes and nested begin, commit and abort operations. Different store instances must remain independent, and reads must reflect the correct pending or committed state. Review the class for failures that expose the wrong values or move changes across transaction boundaries incorrectly.

What you'll practise

  • Nested transaction state

    Trace the movement of changes when inner transactions commit or abort.

  • Read semantics

    Distinguish pending writes, deleted keys and stored values under the stated contract.

  • Instance isolation

    Check that operations on one store do not change another store's data.

Your code-review workspacePreview
Transactional store classCode included in the full challenge
Your review

Explain where state becomes incorrect and how you would fix it.

The code, instructions and feedback are included with Full Access.
Nested Transaction Store Bug Hunt | breakinto.ai