question-mark
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.

'socket hang up' happens when to install

See original GitHub issue

I’m submitting a…


[X] Bug report  
[ ] Feature request
[ ] Documentation issue or request

In package


[ ] @ng-toolkit/init
[X] @ng-toolkit/serverless
[ ] @ng-toolkit/universal
[ ] @ng-toolkit/pwa
[ ] @ng-toolkit/firebug

Current behavior

When ng add @ng-toolkit/serverless I got an error

Error: socket hang up at createHangUpError (_http_client.js:323:15) at TLSSocket.socketOnEnd (_http_client.js:426:23) at TLSSocket.emit (events.js:187:15) at TLSSocket.EventEmitter.emit (domain.js:441:20) at endReadableNT (_stream_readable.js:1094:12) at process._tickCallback (internal/process/next_tick.js:63:19) Emitted ‘error’ event at: at TLSSocket.socketOnEnd (_http_client.js:426:9) at TLSSocket.emit (events.js:187:15) [… lines matching original stack trace …] at process._tickCallback (internal/process/next_tick.js:63:19) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 (node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.4: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“linux”,“arch”:“x64”})

npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! serverless@1.26.1 postinstall: node ./scripts/postinstall.js npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the serverless@1.26.1 postinstall script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in: npm ERR! /home/um/.npm/_logs/2019-01-09T22_46_00_121Z-debug.log

Expected behavior

Install is completed.

Minimal reproduction of the problem with instructions

Example repository

What is the motivation / use case for changing the behavior?

Environment


Angular CLI: 7.2.1
Node: 10.14.2
OS: linux x64
Angular: 7.2.0
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.12.1
@angular-devkit/build-angular     0.12.1
@angular-devkit/build-optimizer   0.12.1
@angular-devkit/build-webpack     0.12.1
@angular-devkit/core              7.2.1
@angular-devkit/schematics        7.2.1
@angular/cli                      7.2.1
@ngtools/webpack                  7.2.1
@schematics/angular               7.2.1
@schematics/update                0.12.1
rxjs                              6.3.3
typescript                        3.2.2
webpack                           4.23.1

Others:

Issue Analytics

  • State:open
  • Created 5 years ago
  • Reactions:2
  • Comments:8

github_iconTop GitHub Comments

2reactions
SouengKimmengcommented, Jan 19, 2019

+1

1reaction
fluxconn-derickcommented, Jan 24, 2019

+1 ng add @ng-toolkit/serverless --provider aws

following walk through from https://www.youtube.com/watch?v=N-6LtzJezsk

I get

spawn-sync@1.0.15 postinstall D:.. …\node_modules\spawn-sync node postinstall

serverless@1.26.1 postinstall D:.. …\node_modules\serverless node ./scripts/postinstall.js

events.js:167 throw er; // Unhandled ‘error’ event ^

Error: socket hang up at createHangUpError (_http_client.js:323:15) at TLSSocket.socketOnEnd (_http_client.js:426:23) at TLSSocket.emit (events.js:187:15) at TLSSocket.EventEmitter.emit (domain.js:441:20) at endReadableNT (_stream_readable.js:1094:12) at process._tickCallback (internal/process/next_tick.js:63:19) Emitted ‘error’ event at: at TLSSocket.socketOnEnd (_http_client.js:426:9) at TLSSocket.emit (events.js:187:15) [… lines matching original stack trace …] at process._tickCallback (internal/process/next_tick.js:63:19) npm WARN @ng-toolkit/pwa@1.1.50 requires a peer of @angular/common@~7.0.0 but none is installed. You must install peer dependencies yourself. npm WARN @ng-toolkit/pwa@1.1.50 requires a peer of @angular/core@~7.0.0 but none is installed. You must install peer dependencies yourself. npm WARN @ng-toolkit/pwa@1.1.50 requires a peer of @angular/service-worker@~7.0.0 but none is installed. You must install peer dependencies yourself. npm WARN @ng-toolkit/universal@1.1.50 requires a peer of @angular/common@~7.0.0 but none is installed. You must install peer dependencies yourself. npm WARN @ng-toolkit/universal@1.1.50 requires a peer of @angular/core@~7.0.0 but none is installed. You must install peer dependencies yourself. npm WARN The package ts-loader is included as both a dev and production dependency. npm WARN The package webpack-cli is included as both a dev and production dependency. npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.7 (node_modules\fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.7: wanted {“os”:“darwin”,“arch”:“any”} (current: {“os”:“win32”,“arch”:“x64”})

npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! serverless@1.26.1 postinstall: node ./scripts/postinstall.js npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the serverless@1.26.1 postinstall script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

Running on …

Angular CLI: 7.2.3 Node: 10.15.0 OS: win32 x64 Angular: 7.2.2 … animations, common, compiler, compiler-cli, core, forms … http, language-service, platform-browser … platform-browser-dynamic, platform-server, router

Package Version

@angular-devkit/architect 0.12.3 @angular-devkit/build-angular 0.12.3 @angular-devkit/build-optimizer 0.12.3 @angular-devkit/build-webpack 0.12.3 @angular-devkit/core 7.2.3 @angular-devkit/schematics 7.2.3 @angular/cli 7.2.3 @ngtools/webpack 7.2.3 @schematics/angular 7.2.3 @schematics/update 0.12.3 rxjs 6.3.3 typescript 3.2.4 webpack 4.28.4

Read more comments on GitHub >

github_iconTop Results From Across the Web

NodeJS - What does "socket hang up" actually mean?
It means that socket does not send connection end event within the timeout period. If you are getting the request for cheerio via...
Read more >
NodeJS - What does socket hang up actually mean - Edureka
When a socket hang up is thrown, one of two things happens: When you're a customer, When you send a request to a...
Read more >
502 Bad Gateway - Socket hang up | Apigee Edge
The error code [socket hang up][ECONNRESET] indicates that the target server has closed the connection with Edge Microgateway. This can be searched in...
Read more >
Hang in There! (A solution to socket hang up) - Medium
I was just trying to do a simple POST request in Postman with these parameters: There should be no reason why it should...
Read more >
Socket hang up problems - Google Groups
to an ExpressJS server, that did not add keep-alive by default (as it ... The socket hang up seems to happen on 0.5pre...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found