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

Deployments fail on 0.34.0 #100

Closed
mrkurt opened this issue Jul 2, 2018 · 1 comment
Closed

Deployments fail on 0.34.0 #100

mrkurt opened this issue Jul 2, 2018 · 1 comment

Comments

@mrkurt
Copy link
Member

mrkurt commented Jul 2, 2018

This seems to be different depending on user/app, but deploys frequently crash l with errors like this:

(node:70690) UnhandledPromiseRejectionWarning: Error: socket hang up
   at createHangUpError (_http_client.js:331:15)
   at TLSSocket.socketOnEnd (_http_client.js:423:23)
   at emitNone (events.js:111:20)
   at TLSSocket.emit (events.js:208:7)
   at endReadableNT (_stream_readable.js:1064:12)
   at _combinedTickCallback (internal/process/next_tick.js:138:11)
   at process._tickCallback (internal/process/next_tick.js:180:9)
(node:70690) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:70690) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

The bundles aren't exceptionally big, and after installing 0.34.0-5 it works just fine.

@mrkurt mrkurt added the bug label Jul 2, 2018
@mrkurt
Copy link
Member Author

mrkurt commented Jul 11, 2018

Fixed in 0.35.0

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

No branches or pull requests

2 participants