Skip to content
This repository has been archived by the owner on Jan 19, 2024. It is now read-only.

Difficulty running node demo in Windows 10 #21

Open
LoisRP opened this issue Mar 5, 2020 · 0 comments
Open

Difficulty running node demo in Windows 10 #21

LoisRP opened this issue Mar 5, 2020 · 0 comments

Comments

@LoisRP
Copy link
Contributor

LoisRP commented Mar 5, 2020

Running
node src/index.js
(after an "npm i" install) produces these errors:

Retrieving balance for XVnJMYQFqA8EAijpKh5EdjEY5JqyxykMKKSbrUX8uchF6U8..
(node:11216) UnhandledPromiseRejectionWarning: Error: 12 UNIMPLEMENTED:
at Object.exports.createStatusError (C:\Users\Lois\Documents\GitHub\xsdk\Xpring-SDK-Demo\node\node_modules\grpc\src\common.js:91:15)
at Object.onReceiveStatus (C:\Users\Lois\Documents\GitHub\xsdk\Xpring-SDK-Demo\node\node_modules\grpc\src\client_interceptors.js:1209:28)
at InterceptingListener._callNext (C:\Users\Lois\Documents\GitHub\xsdk\Xpring-SDK-Demo\node\node_modules\grpc\src\client_interceptors.js:568:42)
at InterceptingListener.onReceiveStatus (C:\Users\Lois\Documents\GitHub\xsdk\Xpring-SDK-Demo\node\node_modules\grpc\src\client_interceptors.js:618:8)
at callback (C:\Users\Lois\Documents\GitHub\xsdk\Xpring-SDK-Demo\node\node_modules\grpc\src\client_interceptors.js:847:24)
(node:11216) 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(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:11216)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant