MM Error - .AppleDouble and UnhandledPromiseRejectionWarning

lavolp3

@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.

bolish

@lavolp3
Thanks for explanation.

I’ve just raised it on Git on an existing issue log.

lavolp3

The issue is already raised
https://github.com/Jopyth/MMM-Remote-Control/issues/87

And 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.”

bolish

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)

bolish

@lavolp3
OK, I will try the fix

lavolp3

@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.

bolish

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!!!

lavolp3

@bolish said in MM Error - .AppleDouble and UnhandledPromiseRejectionWarning:

and will be very close to use it in real life!!!

I haven’t really been for two years. Lol.

bolish

@lavolp3 :-)
Let’s see what will happen to mine then!! But to be honest, I’m also afraid that this is the kind of things which is never really “finished”…
Who cares…As soon as we enjoy??
(the issue then becomes the quantity of unfinished things…)