1 person reported

All time, since Sep 17.

Stream end(cb) and write(cb) fire before backlog is flushed

“In Bun, the http.ServerResponse.end(cb) callback fires before the response has been flushed while the client is backpressured.”

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/4860/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

Quiet. No reports in the last two weeks, down from 2 a week at the late-September peak.

Under backpressure, callbacks fire immediately while data is still buffered, unlike Node; affects http.ServerResponse, TLSSocket and child.stdin.

Is this your bug?

Where: Node stream APIs
Versions: 1.4.2
Platforms: Linux
How bad: Breaks a normal workflow.

Original reports3, newest first

Sep 23, 2026child.stdin.end(cb) fires before the pipe backlog is flushed#43875
Sep 23, 2026TLSSocket.end(cb)/write(cb) fire before the wrapped stream's backlog is flushed#43874
Sep 17, 2026http.ServerResponse.end(cb)/write(cb) fire before the response is flushed#43155

Do you work on Bun?

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