MM Error - .AppleDouble and UnhandledPromiseRejectionWarning

lavolp3

@bolish
OK that didn’t help.
MMM-Logging at least gave us the file putting the error out but not file from which it originated.

But isn’t Linux a beautiful wild monsterous creature?
Try this command

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

in the MagicMirror directory.

“find” looks for all files in the 3rd party module directories (all files with depth of 2 directories maximum, we don’t want to have all the numerous node module files included), then it executes (“-exec”) a grep function searching the files for the “Promise” function.
“2>/dev/null” is there to put all error output (there’s a lot) away from the standard output

This will give you all 3rd party module files including the promise function. Then we can limit it to a few modules.

With these you can do the “deactivate and look for errors” workflow and find out the one responsible

bolish

@lavolp3
this is the result I have :

./js/main.js
./js/module.js
./clientonly/index.js

Seems to be linked to the core system itself only and not to any particular module?
I’ve already made a git pull for MM itself but it’s already up to date.

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