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.

Sign up for GitHub

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

Jump to bottom

uncaughtException: Cannot read property 'statusCode' of undefined #3594

Closed
Ockejanssen opened this issue Jan 26, 2021 · 1 comment · Fixed by #3597
Closed

uncaughtException: Cannot read property 'statusCode' of undefined #3594

Ockejanssen opened this issue Jan 26, 2021 · 1 comment · Fixed by #3597

Comments

@Ockejanssen
Copy link

TypeError: Cannot read property 'statusCode' of undefined
at node_modules//less/lib/less-node/url-file-manager.js:33:40
at done (node_modules/needle/lib/needle.js:468:14)
zxfrank added a commit to zxfrank/less.js that referenced this issue Jan 29, 2021
@zxfrank
Fix expected response when there's a socket error
7dc1da2 
In the case of a network issue, there's an error but no response, so no statusCode, This fixes it

Fixes less#3594
@zxfrank zxfrank mentioned this issue Jan 29, 2021
Merged
@zxfrank
Copy link
Contributor

zxfrank commented Jan 29, 2021 •
edited

I logged my error

LessError: resource 'https://fonts.googleapis.com/css?family=Roboto%20Slab' gave this Error:
    Error: socket hang up

I'm fixing it right now, status in #3597

matthew-dean pushed a commit that referenced this issue Jan 29, 2021
@zxfrank
Fix expected response when there's a socket error (#3597)
63c1827 
In the case of a network issue, there's an error but no response, so no statusCode, This fixes it

Fixes #3594
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix expected response when there's a socket error zxfrank/less.js
2 participants
@zxfrank @Ockejanssen