MM Error - .AppleDouble and UnhandledPromiseRejectionWarning

lavolp3

@bolish Sorry my bad. You need to do it in the modules folder. Then maxdepth 2 leads to the folder itself and all 3rd party folders.
Sorry again!

bolish

@lavolp3
!!! it’s not your fault, it’s shame on me!!!

Anyway, I just did it…Result is zero…Nothing…

pi@MagicPi:~/MagicMirror/modules $ find . -maxdepth 2 -exec grep -nwl  Promise 2>/dev/null {} +
pi@MagicPi:~/MagicMirror/modules $

So…disable them one by one is the next analysis step??

lavolp3

@bolish First, try another one

find . -maxdepth 2 -exec grep -nwl  .then 2>/dev/null {} +

Promises are not always processed by a Promise function, but I also by calling something and then calling .then().
Actually I know these bastards for two or three days now, so I’m far from being an expert

bolish

@lavolp3
thx

Here is the result

pi@MagicPi:~/MagicMirror/modules $ find . -maxdepth 2 -exec grep -nwl  .then 2>/dev/null {} +
./MMM-Remote-Control/node_helper.js
./MMM-Remote-Control/installer.sh
./MMM-BackgroundSlideshowInfo/README.md
./MMM-NotificationTrigger/README.md
pi@MagicPi:~/MagicMirror/modules $

So… Remote Control I believe…
I will try to disable it and see what happens.

bolish

I confirm…
No error message anymore after disabling MMM-RemoteControl.

Wao…and now?? Do you have a clue about next step or should I raise an issue into MMM-ControlRemote git?

lavolp3

@bolish That’s odd. Something doesn’t add up, sorry. I think a “then” is searched as well. But try these modules.
If not successfull you’d need to go with disabling one module after another

lavolp3

@bolish Well, great!! BUt oddly, I dont have this… and I have the module as well.
Do you have Jopyth’s original version installed? Or a fork?

bolish

@lavolp3
I have the original version from Jopyth.
S***, I hoped it would have been easier to figure out!!

I just Git Pulled… Was already up to date

lavolp3

@bolish OK I can confirm your errors. Had it disabled. By enabling the unhaldled promises come up.
Raise an issue. I’ll have a look at the code

bolish

Don’t you think it can be linked to the .appledouble thing. Remember that :

2019-02-15T22:45:59  Launching application. (/home/pi/MagicMirror/js/electron.js:82 App.)
2019-02-15T22:45:59  ERROR! Could not find main module js file for .AppleDouble (/home/pi/MagicMirror/modules/MMM-Remote-Control/node_helper.js:258 Class.loadModuleDefaultConfig)
2019-02-15T22:46:03  (node:6793) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): TypeError: Cannot read property 'refs' of undefined (/home/pi/MagicMirror/internal/process/warning.js:18 writeOut)
2019-02-15T22:46:03  (node:6793) [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. (/home/pi/MagicMirror/internal/process/warning.js:18 writeOut)
2019-02-15T22:46:03  (node:6793) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): TypeError: Cannot read property 'refs' of undefined (/home/pi/MagicMirror/internal/process/warning.js:18 writeOut)
2019-02-15T22:46:03  (node:6793) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 3): TypeError: Cannot read property 'refs' of undefined (/home/pi/MagicMirror/internal/process/warning.js:18 writeOut)
2019-02-15T22:46:03  (node:6793) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 4): TypeError: Cannot read property 'refs' of undefined (/home/pi/MagicMirror/internal/process/warning.js:18 writeOut)
2019-02-15T22:46:04  (node:6793) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 5): TypeError: Cannot read property 'refs' of undefined (/home/pi/MagicMirror/internal/process/warning.js:18 writeOut)
2019-02-15T22:46:08  MMM-Logging updated config received, reloading console (/home/pi/MagicMirror/modules/MMM-Logging/node_helper.js:30 Class.socketNotificationReceived)

Because the .appledouble error is refering to Remote Control also.

So…you just have the same issue now but never noticed it before?