MMM-Bring errors, not working

secdude

Hi folks,

anyone recently seen this error with MMM-Bring?

[2020-09-24 13:11:39.995] [ERROR]  (node:1166) UnhandledPromiseRejectionWarning: Error: Request failed with status code 404
    at createError (/home/pi/mm_prod/MagicMirror/modules/MMM-Bring/node_modules/axios/lib/core/createError.js:16:15)
    at settle (/home/pi/mm_prod/MagicMirror/modules/MMM-Bring/node_modules/axios/lib/core/settle.js:17:12)
    at IncomingMessage.handleStreamEnd (/home/pi/mm_prod/MagicMirror/modules/MMM-Bring/node_modules/axios/lib/adapters/http.js:237:11)
    at IncomingMessage.emit (events.js:205:15)
    at endReadableNT (_stream_readable.js:1154:12)
    at processTicksAndRejections (internal/process/task_queues.js:84:9)
[2020-09-24 13:11:39.997] [ERROR]  (node:1166) UnhandledPromiseRejectionWarning: Error: Request failed with status code 404
    at createError (/home/pi/mm_prod/MagicMirror/modules/MMM-Bring/node_modules/axios/lib/core/createError.js:16:15)
    at settle (/home/pi/mm_prod/MagicMirror/modules/MMM-Bring/node_modules/axios/lib/core/settle.js:17:12)
    at IncomingMessage.handleStreamEnd (/home/pi/mm_prod/MagicMirror/modules/MMM-Bring/node_modules/axios/lib/adapters/http.js:237:11)
    at IncomingMessage.emit (events.js:205:15)
    at endReadableNT (_stream_readable.js:1154:12)
    at processTicksAndRejections (internal/process/task_queues.js:84:9)
[2020-09-24 13:11:40.000] [ERROR]  (node:1166) 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(). (rejection id: 4)
[2020-09-24 13:11:40.002] [ERROR]  (node:1166) 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(). (rejection id: 4)

Thanks & regards,

secdude

secdude

Solution: This is what it looks like if you provide a non-existing list name…

lavolp3

@secdude ok thanks for clarifying.
Still this promise rejection should be handled.
I would send an issue on github.
Unhandled promise rejections are not nice and rather easy to avoid.