Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix expected response when there's a socket error #3597

Merged
merged 1 commit into from
Jan 29, 2021

Conversation

zxfrank
Copy link
Contributor

@zxfrank zxfrank commented Jan 29, 2021

In the case of a network issue, there's an error but no response, so no statusCode, This fixes it

Fixes #3594

In the case of a network issue, there's an error but no response, so no statusCode, This fixes it

Fixes less#3594
@matthew-dean
Copy link
Member

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

uncaughtException: Cannot read property 'statusCode' of undefined
2 participants