Null bypasses cache validation Debugging Lab

Null bypasses cache validationCaching & PerformanceHardPreparing

00:00

Incident Dossier

Null bypasses cache validation

The permissions helper silently returns a hardcoded default when the role is null or an empty string, ignoring anything that might already be cached for those keys. Admin tools cannot override the default through the normal cache path.

Initial failing signalCached entry under null/empty key is ignoredExpected getPermissions(null) returns the cached entry seeded for null · received getPermissions(null) returns the hardcoded FALLBACK_PERMISSIONS instead

Progress

1Reproduce the bugRun checks

2Edit the fixOpen

3Pass checksOpen

4Submit fixOpen

Reproduction Steps

Run npm test.
Notice that a cached entry seeded for null is ignored — the helper returns the hardcoded fallback instead.
Inspect getPermissions in src/permissions.js.
Find the short-circuit that bypasses the cache for any falsy role key.
Remove the short-circuit so null/empty-string keys consult the cache like any other key.

Focus Mode

Start

src/permissions.js

Likely area

src/permissions.js

Challenge Coach

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

TopicCaching & Performance

DifficultyHard

Est. time22 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