Incident Dossier

Tenant prefix skipped on read

Two tenants read the same resource by the same key. Whichever tenant wrote last wins; the other tenant sees its data silently overridden.

Initial failing signalBoth tenants read the same cached valueExpected behavior: each tenant sees its own cached value · actual behavior: both tenants see whichever was written last

Progress

1Reproduce the bugRun checks

2Edit the fixOpen

3Pass checksOpen

4Submit fixOpen

Reproduction Steps

Run npm test.
Compare the key built by `set` to the key built by `get`.
Identify the prefix one uses and the other drops.
Align the read key with the write key.

Focus Mode

Start

src/cache.js

Likely area

src/cache.js

Challenge Coach

Hints reveal broad direction first, then narrow toward the suspect path without showing hidden tests or exact solution code.

TopicCaching & Performance

DifficultyMedium

Est. time18 min

Workspacepreparing

Explorer

Loading files

Evidence Map

Failing signal loaded from challenge API
Workspace files loaded from workspace API
Results rendered only after API run/submit

Autosaved

workspace

Outputread-onlyready$ prepare workspace

Preparing workspace