@CurlyQ12391 this is probably due to the bug i introduced in 2.20. it chops off the collection of old+new events at maxEntries
looks like u have lots of old events ( I see crap from 2017 in my list of old)
anyhow. fix coming in 2.21 (on Saturday), or make maxEntries bigger in the short term
365 events broadcast and none showing means there are all old. we don’t display old.
@bugsounet you could have sent him a private message
I have edited them
@richland007 said in git pull error:
The following untracked working tree files would be overwritten by merge:
package-lock.json
untracked means its not in the repo just erase it
-lock files are rebuilt on npm install
@Turtle while looking at the MM screen
ctrl-r will reload
ctrl-q will quit
ctrl-m will minimize
all same as on Windows for full screen apps
@ZeroCool see the topics in my signature below, they will help.
a module is
{
module:
position:
config:{
...
}
},
notice the trailing comma.
missing trailing commas are fatal, too.many is not
@bicolorbore586 it would block updates.
but you could save your changes,
copy file,
git checkout xxx.js
then update
then check if there are any impacts
and re-apply them after update
you could also fork the repo, and run that.
update and submit or back to module author
maybe they would take it as a change… I didn’t look at last update date to see if module is still actively maintained ( modified just last month)
@mattkab correct those are the ical format urls.
public and secret.
the embed url is located above them
@jturczak just fyi. every post from users with less than 2 reputation are reviewed before being posted on the forum. this stops all the spam we get.
@MisterT u have to edit the image and rotate it
@MisterT ah, the xrandr under the covers…
glad u found it. thanks for the feedback
@kavasakki restart the docker container? or reboot
@shizzlesticks I’ve seen some recurrent events in the ics that don’t work, but move the yearly to the end of the rule, and all is well. not our code. .
haven’t come up with a solid cure yet
@lmac well you ran it in the wrong place… oops
do this
cd ~/MagicMirror
rm -rf node_modules
rm package-lock.json
npm install
then for whatever module was causing problem
cd ~/MagicMirror/modules/modulename
do the same last 3 steps as above
AND THEN
npm install request --save
@aldisachen currently the clock will only use the system time.
in the update coming April 1, you can specify the tinezone as an option.
so then u could do two clock instances
@sangroma yes. that is one of the new es6 idioms. ?., the chaining operator
see 
on
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Optional_chaining
chrome needs version 80, u have only v 72
@redink said in Every time I run an update, something breaks. This time is no exception:
lectron failed to install correctly, please delete node_modules/electron and try installing again
sadly it happens
delete the folder as suggested and do
cd ~/MagicMirror
npm install electron@22.0.0
how did u upgrade? manual git pull or my upgrade script?
what hardware are you on?
uname -a
and lsb_release -a
will give us info
little look at your output again
2 info using npm@6.14.4
3 info using node@v10.15.2
you are way downlevel…
if u had used my script, I would have upgraded node and npm for you .
see https://github.com/sdetweil/MagicMirror_scripts
I try to help avoid the fatal upgrades that you experience
note
latest MM won’t run on raspi os stretch or earlier, so one has to upgrade sd card too.
@RobertM yes. your browser needs to be at version 80 or above for the JavaScript we use