Platform: Raspbian 12

Node Version: 18.19.0

MagicMirror Version: 2.27

Description:
I am seeing the following errors in my logs, though I’m not necessarily seeing any problems on my display (at least not regularly).

0|mm       | 024-05-16 14:10:44.296] [ERROR] 2024-05-16T14:10:44 <error> (node:26446) 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: 97) (/home/username/MagicMirror/node:internal/process/warning:60 writeOut) 
0|mm       | [2024-05-16 14:11:12.283] [ERROR] 2024-05-16T14:11:12 <error> (node:26446) UnhandledPromiseRejectionWarning: TypeError: fetch failed
0|mm       |     at Object.fetch (node:internal/deps/undici/undici:12293:11)
0|mm       |  (/home/username/MagicMirror/node:internal/process/warning:60 writeOut) 
0|mm       | [2024-05-16 14:11:12.291] [ERROR] 2024-05-16T14:11:12 <error> (node:26446) 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: 119) (/home/username/MagicMirror/node:internal/process/warning:60 writeOut) 
0|mm       | /home/username/MagicMirror/node_modules/electron/dist/electron exited with signal SIGINT
0|mm       | [2024-05-16 14:12:49.844] [ERROR] 2024-05-16T14:12:49 <error> (node:28645) UnhandledPromiseRejectionWarning: TypeError: fetch failed
0|mm       |     at Object.fetch (node:internal/deps/undici/undici:12293:11)
0|mm       | 
0|mm       | (Use `electron --trace-warnings ...` to show where the warning was created) (/home/username/MagicMirror/node:internal/process/warning:60 writeOut) 
0|mm       | [2024-05-16 14:12:49.851] [ERROR] 2024-05-16T14:12:49 <error> (node:28645) 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: 52) (/home/username/MagicMirror/node:internal/process/warning:60 writeOut) 
0|mm       | [2024-05-16 14:13:09.544] [ERROR] 2024-05-16T14:13:09 <error> (node:28645) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added to [TLSSocket]. Use emitter.setMaxListeners() to increase limit (/home/username/MagicMirror/node:internal/process/warning:60 writeOut)

It seems to come up most often when I load the MMM-Pinfo module in my config, though I have seen it at other times as well. The problem is that I don’t see enough information in these logs to find a source myself.

Steps to Reproduce: Load MM, usually with MMM-Pinfo module enabled.

If anyone has any ideas, that would be great.

pinfo doesn’t use fetch…

Sadly, best way is to comment out, or disabled:true
each module til you find the culprit