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

Fee monitor "Internal error" should be more specific #128

Open
HoOngEe opened this issue Oct 2, 2019 · 2 comments
Open

Fee monitor "Internal error" should be more specific #128

HoOngEe opened this issue Oct 2, 2019 · 2 comments

Comments

@HoOngEe
Copy link
Contributor

HoOngEe commented Oct 2, 2019

Current some error messages only send "Internal error" but it should be more specific.

@HoOngEe
Copy link
Contributor Author

HoOngEe commented Oct 2, 2019

The console error message on mainnet was like

{ error: { code: -32603, message: 'Internal error' } }
(node:9130) UnhandledPromiseRejectionWarning: #<Object>
(node:9130) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async functi
on without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:9130) [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.

@foriequal0
Copy link
Contributor

It might be an issue of internal libraries such as jayson. eslint hasn't raised any warning about floating promises.

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