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

报错了 #1

Open
nnocase opened this issue Mar 30, 2021 · 2 comments
Open

报错了 #1

nnocase opened this issue Mar 30, 2021 · 2 comments

Comments

@nnocase
Copy link

nnocase commented Mar 30, 2021

(node:2849) UnhandledPromiseRejectionWarning: FetchError: request to http://0.0.0.0:8891/segment failed, reason: connect ECONNREFUSED 0.0.0.0:8891
at ClientRequest. (/Users/xgf/code/AR-lab/client/node_modules/node-fetch/lib/index.js:1461:11)
at ClientRequest.emit (events.js:315:20)
at Socket.socketErrorListener (_http_client.js:469:9)
at Socket.emit (events.js:315:20)
at emitErrorNT (internal/streams/destroy.js:106:8)
at emitErrorCloseNT (internal/streams/destroy.js:74:3)
at processTicksAndRejections (internal/process/task_queues.js:80:21)
(node:2849) 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: 3)

@shadowcz007
Copy link
Owner

(node:2849) UnhandledPromiseRejectionWarning: FetchError: request to http://0.0.0.0:8891/segment failed, reason: connect ECONNREFUSED 0.0.0.0:8891
at ClientRequest. (/Users/xgf/code/AR-lab/client/node_modules/node-fetch/lib/index.js:1461:11)
at ClientRequest.emit (events.js:315:20)
at Socket.socketErrorListener (_http_client.js:469:9)
at Socket.emit (events.js:315:20)
at emitErrorNT (internal/streams/destroy.js:106:8)
at emitErrorCloseNT (internal/streams/destroy.js:74:3)
at processTicksAndRejections (internal/process/task_queues.js:80:21)
(node:2849) 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: 3)

service里的python服务需要开启

@nnocase
Copy link
Author

nnocase commented Mar 30, 2021

OK,thanks

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