You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As #24835 illustrates, recent versions of Deno have got unfriendly error messages on fetch errors.
Although this issue itself will be resolved by #24910, it would be even better if the error message could have other bits of information. In particular, TCP/IP level info i.e. src/dest addr and port might be helpful for debugging.
Proposed message format
When TCP/IP info is available
When fetch fails after TCP connection is established, the error message will look like:
TypeError: error sending request from 127.0.0.1:50472 for http://localhost:4444/ (127.0.0.1:4444): client error (SendRequest): connection error: Connection reset by peer (os error 54)
This contains 127.0.0.1:50472 as a source node and 127.0.0.1:4444 as a destination node.
When unavailable
When fetch fails before TCP connection is established, the error message will be like:
TypeError: error sending request for url (https://nonexistent.deno.land/): client error (Connect): dns error: failed to lookup address information: nodename nor servname provided, or not known: failed to lookup address information: nodename nor servname provided, or not known
Note this does not have TCP/IP level connection info.
The text was updated successfully, but these errors were encountered:
As #24835 illustrates, recent versions of Deno have got unfriendly error messages on
fetch
errors.Although this issue itself will be resolved by #24910, it would be even better if the error message could have other bits of information. In particular, TCP/IP level info i.e. src/dest addr and port might be helpful for debugging.
Proposed message format
When TCP/IP info is available
When
fetch
fails after TCP connection is established, the error message will look like:This contains
127.0.0.1:50472
as a source node and127.0.0.1:4444
as a destination node.When unavailable
When
fetch
fails before TCP connection is established, the error message will be like:Note this does not have TCP/IP level connection info.
The text was updated successfully, but these errors were encountered: