3 people reported
All time, since Jul 25.
Bun.write hangs on fetch Response
“Bun.write(path, new Response(streamFromFetch)) never completes.”
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/5288/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
Bun.write never resolves when writing a fetch Response. Write promise never settles and file is never written; seen with new Response(stream) and when Response is GC'd mid-download.
Is this your bug?
File my report- Where
- Bun.write API
- Versions
- 1.3.11 to 1.4.0
- Platforms
- macOS
- How bad
- Breaks a normal workflow. Most reports say it used to work. Some reports say it blocks them completely.
Not quite your bug?
- writeFile leaves stale trailing bytes2 people
- Pending reads exit process early1 person
- Test process never exits2 people
Original reports3, newest first
- Bun.write(path, new Response(stream)) hangs forever at 100% CPU and never creates the file#43429
- Bun.write(path, response) never resolves when the fetch Response is GC'd mid-download; fetch finalizer ignores the pending write waiter#40278
- Writing Response to disk hangs indefinitely (1.4 regression)#35854