Read the statement by Michael Teeuw here.
MM Error - .AppleDouble and UnhandledPromiseRejectionWarning
-
@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 commandfind . -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 outputThis 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
-
@lavolp3
this is the result I have :./js/main.js ./js/module.js ./clientonly/index.jsSeems 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. -
@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! -
@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??
-
@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 -
@lavolp3
thxHere 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. -
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?
-
@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 -
@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? -
@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
-
@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 -
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?
-
@bolish No.
Unhandled promise rejections are code stuff that can be overcome quite easily.Think of it like this.
You ask your program to do something outside (e.g. request data from somewhere else.
When it doesn’t work the “promise” of delivering something is rejected.
When this rejection is unhandled (the program isnt told what to do) you get this error -
@bolish said in MM Error - .AppleDouble and UnhandledPromiseRejectionWarning:
So…you just have the same issue now but never noticed it before?
May have been updated in the past. Don’t know.
-
@lavolp3
Thanks for explanation.I’ve just raised it on Git on an existing issue log.
-
The issue is already raised
https://github.com/Jopyth/MMM-Remote-Control/issues/87And the solution si down below:
“It’s this line:
var baseUrl = result[0].refs.fetch;for some modules it looks like simple-git fails. Adding a try catch block for it in my PR.” -
Just to be sure. I didn’t noticed any real effect of this issue.
I was mainly trying to solve it before I’m experiencing stability issues with MMM-GroveGestures and wanted to be sure that this “promise” thing is not the root cause before raising the MMM-GroveGestures issue.Do you think that it is now clear that my MMM-GroveGestures issue and this one are not linked (meaning I can look at the GroveGesture issue in parallel)
-
@lavolp3
OK, I will try the fix -
@bolish This error/notice is solely within the Remote-Control module and not related to any other module. It does not influence your mirror performance at all.
If you can ignore it (which I couldnt), you might as well do. -
OK, thanks for your support in that!
Now let’s move to the next issue…MMM-GroveGestures…(I will open a second post for that).
After those one are fixed, my MM will be nearly perfect and will be very close to use it in real life!!!
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login