Cache key delimiter collision Debugging Lab

Cache key delimiter collisionCaching & PerformanceEasyPreparing workspaceAutosaved

00:00

Incident Dossier

Cache key delimiter collision

Two tenants with overlapping identifiers see each other's cached values because the cache key concatenates without a separator.

Initial failing signalTwo distinct keys reduce to the same stringExpected first cached value still present · received first cached value was overwritten

Progress

1Reproduce the bugRun checks

2Edit the fixOpen

3Pass checksOpen

4Submit fixOpen

Reproduction Steps

Run npm test.
Inspect how the cache key is built from its parts.
Find a pair of inputs that reduce to the same string when concatenated.
Add a separator that cannot be produced by either part alone.

Focus Mode

Start

src/cache.js

Likely area

src/cache.js

Progressive hints

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

TopicCaching & Performance

DifficultyEasy

Est. time12 min

Workspacecreating

Explorer

Preparing workspace 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$ workspace boot

Workspace booting...