Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Timeout error handling

See original GitHub issue

Read Timeouts section of documentation. After glancing the related code here as well as here and here, I was left with a few questions.

Are README suggestions still correct? Looks more like ETIMEDOUT error is exclusively connection-related, and ESOCKETTIMEDOUT read-related.
Should client-side code also be checking for ESOCKETTIMEDOUT and ECONNRESET?
Could you change the Error messages to something useful to user?

For 3, the errno-based names are already included as error.code. As such, could error.message be made more human readable [e.g., ETIMEDOUT-> new Error("server took too long to connect")]?

Issue Analytics

State:
Created 6 years ago
Comments:7

Top GitHub Comments

9reactions

plroebuckcommented, Mar 10, 2019

So it’s been a year now – still not even an acknowledgement this was even read by a maintainer…

0reactions

stale[bot]commented, Mar 9, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.