Socket reused after error Debugging Lab

Socket reused after errorNetwork & ConnectivityHardPreparing workspaceAutosaved

00:00

Incident Dossier

Socket reused after error

Mid-response errors do not put the connection in a usable state — bytes remain in the receive buffer. The pool returns the socket to the idle list anyway, and the next caller reads those leftover bytes as if they were the new response. The bug only surfaces when an upstream error happens to coincide with another request on the same keep-alive.

Initial failing signalErrored socket with buffered bytes is reusedExpected an errored socket with buffered data is closed and not handed back · received the pool returns the same socket for the next acquire

Progress

1Reproduce the bugRun checks

2Edit the fixOpen

3Pass checksOpen

4Submit fixOpen

Reproduction Steps

Run npm test.
Inspect the failing assertion about an errored socket being returned for reuse.
Trace what reportError does to the socket and what release puts back on the pool.
Mark the socket closed and drain its buffer on error; skip closed sockets on acquire.

Focus Mode

Start

src/socket-pool.js

Likely area

src/socket-pool.js

Progressive hints

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

TopicNetwork & Connectivity

DifficultyHard

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