Incident Dossier

TTL refreshed on every read

Cached session data is never expiring. The cache's read path rewrites the entry's expiry on every read, so a frequently-accessed entry effectively lives forever and stale data accumulates in the cache.

Initial failing signalCache entries never expire while they are being readExpected behavior: After the original TTL elapses, get(key) returns undefined · actual behavior: get(key) keeps returning the value because the read path refreshes the expiry on every call

Progress

1Reproduce the bugRun checks

2Edit the fixOpen

3Pass checksOpen

4Submit fixOpen

Reproduction Steps

Run npm test.
Notice that even after the original TTL elapses, the entry keeps returning a value.
Inspect the body of get in src/session.js.
Identify the line that rewrites the entry's expiry after a successful read.
Remove the read-time refresh so the original TTL — set at put time — is the only thing that decides when the entry expires.

Focus Mode

Start

src/session.js

Likely area

src/session.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. time20 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