2 people reported
All time, since Aug 21.
fetch ignores IPv4-first DNS order
“~2% of fresh processes fail with TimeoutError: The operation timed out.”
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/5783/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
fetch ignores IPv4-first DNS result order settings. fetch dials IPv6 first on dual-stack hostnames even with dns.setDefaultResultOrder("ipv4first") or --dns-result-order set.
Is this your bug?
File my report- Where
- fetch API
- Error text
TimeoutError: The operation timed out- Versions
- 1.3.14 to 1.4.0
- Platforms
- Linux
- How bad
- Breaks a normal workflow.