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

(node:7596) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: Something took too long to do. #13706

Closed
DBlaNQ opened this issue Jun 15, 2017 · 2 comments
Labels
question Issues that look for answers.

Comments

@DBlaNQ
Copy link

DBlaNQ commented Jun 15, 2017

Windows 7 64bit

Node.js: 8.1.1v

Error: (node:7596) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: Something took too long to do.

Is this a bug cuz i reinstalled the whole node.js and it still doesen't fix

@jasnell
Copy link
Member

jasnell commented Jun 15, 2017

The UnhandledPromiseRejectionWarning is intentional. It occurs when a Promise instance is rejected without having a catch handle attached to it. In this case, some part of the code you are using is not catching the Promise rejection, causing core to emit this warning. To identify which code is causing this to occur, try launching Node.js with the --trace-warnings command line flag. That will cause the stack trace to be printed that identifies which bit of code is causing the warning to be emitted.

Closing as this is not a bug in Node.js itself.

@jasnell jasnell closed this as completed Jun 15, 2017
@Fishrock123
Copy link
Contributor

See also: the 'unhandledRejection' and process 'warning' docs.

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

No branches or pull requests

3 participants