Incident Dossier

Memoization keyed on object identity

The search endpoint is recomputing results on every request even when the query parameters are logically identical. Two callers issuing equivalent queries hit the cache only when they happen to share the same query object reference.

Initial failing signalCache miss for logically identical queriesExpected behavior: memoizedSearch({filter:'shirt',limit:5,offset:0}) called twice runs runSearch once · actual behavior: every call runs runSearch again because the Map key is the query object itself

Progress

1Reproduce the bugRun checks

2Edit the fixOpen

3Pass checksOpen

4Submit fixOpen

Reproduction Steps

Run npm test.
Notice that two callers issuing logically identical queries produce two cache entries.
Inspect memoizedSearch in src/search.js.
Identify what the cache uses as the key.
Switch to a canonical, value-based key derived from the query's properties.

Focus Mode

Start

src/search.js

Likely area

src/search.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