Bun DNSException from Bun.dns.lookup Lacks Stack Property
- Investigating(current)
- Trending(upcoming)
- Workaround available(upcoming)
- Resolved(upcoming)
Executive summary
Errors thrown from DNS resolution in Bun (via Bun.dns.lookup, node:dns, or net.connect) lack a stack property, unlike standard errors in Bun and Node.js. This affects developers attempting to trace DNS resolution failures such as EAI_AGAIN.
No verified workaround yet
None of the linked reports describe a mitigation. Follow this incident to hear when one appears.
Official fixUnder active investigation. No report has identified a root cause yet.
Evidence
1 report · 1 GitHubShow
- [1]GitHub First reportDNSException from Bun.dns.lookup / node:dns / net.connect has no stack property(opens GitHub issue in a new tab)
What happens Errors from DNS resolution have no stack property, unlike other errors in Bun and unlike Node's DNS errors. import dns from 'node:dns/promises' console.log(typeof new Error('x').stack) // "string" try { await Bun.dns.lookup('db-host.invalid') } catch (e) { console.log(typeof e.stack, e.name, e.code) // "undefined" "DNSException" ... } try { await dns.lookup('db-host.invalid') } catch (e) { console.log(typeof e.stack, e.name, e.code) // "undefined" "DNSException" "EAI_AGAIN" } The…
by swsd2544 0upvotes 0comments
Timeline
- First report on GitHub issue
DNSException from Bun.dns.lookup / node:dns / net.connect has no stack property
Source