Port Resolves From CWD Debugging Lab

Port Resolves From CWDConfig & EnvironmentEasyPreparing workspaceAutosaved

00:00

Incident Dossier

Port Resolves From CWD

A service reads its port and host from a JSON config shipped next to the source. When the same binary is launched from a different directory, the resolver looks in the wrong place, fails open, and serves on the built-in fallback — sometimes a port nothing else can route to.

Initial failing signalconfig.json shipped next to the module is ignored from another cwdExpected loadConfig() === { host: '0.0.0.0', port: 7070 } · received loadConfig() === { host: '127.0.0.1', port: 8080 }

Progress

1Reproduce the bugRun checks

2Edit the fixOpen

3Pass checksOpen

4Submit fixOpen

Reproduction Steps

Inspect the bundled config.json and the loader that reads it.
See how the loader names the file it reads.
Confirm the failure from a directory other than the repo root.
Make the smallest correction so the loader follows the module, not the shell.

Focus Mode

Start

src/loader.js

Likely area

src/loader.js

Progressive hints

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

TopicConfig & Environment

DifficultyEasy

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