search

svrooij / node-sonos-ts

:speaker: Sonos control library, use this library in your own appliction.
https://sonos-ts.svrooij.io/
MIT License
84 stars 18 forks source link

UnhandledPromiseRejectionWarning - in case the sonos player is not available #82

Closed hklages closed 3 years ago

hklages commented 3 years ago 
(node:23976) UnhandledPromiseRejectionWarning: FetchError: request to http://192.168.178.37:1400/MediaRenderer/AVTransport/Event failed, reason: connect EHOSTUNREACH 192.168.178.37:1400
    at ClientRequest.<anonymous> (C:\Users\hekla\Development\node-red-contrib-sonos-events\node_modules\node-fetch\lib\index.js:1461:11)
    at ClientRequest.emit (events.js:315:20)
    at ClientRequest.EventEmitter.emit (domain.js:486:12)
    at Socket.socketErrorListener (_http_client.js:469:9)
    at Socket.emit (events.js:315:20)
    at Socket.EventEmitter.emit (domain.js:486:12)
    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)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:23976) 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:23976) [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.
svrooij commented 3 years ago

Related to #81

github-actions[bot] commented 3 years ago

:tada: This issue has been resolved in version 2.2.0-beta.5 :tada:

The release is available on:

Your semantic-release bot :package::rocket:

hklages commented 3 years ago

Thanks again :-)

svrooij commented 3 years ago

I would like to keep the issue open until it is auto closed by the release to production. That way everybody not using the beta still see what issues exists (and are maybe already fixed in a beta).

hklages commented 3 years ago

Understand.

github-actions[bot] commented 3 years ago

:tada: This issue has been resolved in version 2.2.0 :tada:

The release is available on:

Your semantic-release bot :package::rocket: