1 person reported

All time, since Aug 24.

Undici connect sockets never close

“When a socket is created by the application and handed to undici through the connect option, Bun 1.4.0 never closes the underlying TCP connection.”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/bun/issues/5721/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

TCP connection never closed for sockets passed to undici connect. Sockets handed to undici through the connect option, as in SOCKS5 proxies, report closed but the peer still sees them open, including when undici layers TLS over the socket.

Is this your bug?

File my report
Where
Node.js compatibility layer
Versions
1.4.0 to 1.4.1-canary.1
Platforms
macOS
How bad
Breaks a normal workflow.

Original reports2, newest first

  1. Bun 1.4.1-canary still leaks the TCP connection when undici layers TLS over a caller-supplied socket (follow-up to #40306)#40401
  2. Bun 1.4.0 leaks the TCP connection for sockets passed to undici via the connect option (regression from 1.3.14)#40306

Do you work on Bun?

Claim its RAP Sheet to see what your users report and answer them in one place.