The log that ate the request

Large uploads cause latency and memory spikes before the request handler begins, even though storage and downstream processing remain healthy.

Initial failing signallog line grows with upload bodyExpected behavior: Request logs contain bounded metadata without the upload body. · actual behavior: The log contains more than 100000 bytes from the upload body.

Progress

1Reproduce the bugRun checks

2Edit the fixOpen

3Pass checksOpen

4Submit fixOpen

Reproduction Steps

Run npm test.
Compare allocations and log size for small and large requests.
Trace what the request logger materializes before the handler runs.
Keep useful diagnostics while bounding work by request size.

Focus Mode

Start

src/requestLog.js

Likely area

src/requestLog.js

Challenge Coach

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

TopicPerformance & Observability

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