Solved Error while trying to update MM, GA, EXT ec
-
Hi,
i didn’t use and update my MM for several months. And now I try to update it because a lot of module are not updated (MM, GA, EXTs, etc).
First, I tried to update the MM with the command :rpi@raspberrypi:~/MagicMirror $ git pull && npm run install-mm
astuce: Tirer sans spécifier comment réconcilier les branches divergentes
astuce: est découragé. Vous pouvez éliminer ce message en lançant une des
astuce: commandes suivantes avant votre prochain tirage :
astuce:
astuce: git config pull.rebase false # fusion (stratégie par défaut)
astuce: git config pull.rebase true # rebasage
astuce: git config pull.ff only # avance rapide seulement
astuce:
astuce: Vous pouvez remplacer “git config” par “git config --global” pour que
astuce: ce soit l’option par défaut pour tous les dépôts. Vous pouvez aussi
astuce: passer --rebase, --no-rebase ou --ff-only sur la ligne de commande pour
astuce: remplacer à l’invocation la valeur par défaut configurée.
Depuis https://github.com/MichMich/MagicMirror
f14e956…343e7de master -> origin/master- [nouvelle étiquette] v2.23.0 -> v2.23.0
- [nouvelle étiquette] v2.24.0 -> v2.24.0
- [nouvelle étiquette] v2.25.0 -> v2.25.0
Mise à jour f14e956…343e7de
error: Vos modifications locales aux fichiers suivants seraient écrasées par la fusion :
package-lock.json
package.json
Veuillez valider ou remiser vos modifications avant la fusion.
Abandon
So, I tried the command : git config pull.rebase false
rpi@raspberrypi:~/MagicMirror $ git config pull.rebase false
rpi@raspberrypi:~/MagicMirror $ git pull && npm run install-mm
Mise à jour f14e956…343e7de
error: Vos modifications locales aux fichiers suivants seraient écrasées par la fusion :
package-lock.json
package.json
Veuillez valider ou remiser vos modifications avant la fusion.
Abandonbut, I have always the error ! Can you please help me !
After, I will need to update GA and Exts.
Thanks,
Adel -
try
git reset --hard && git pull
-
@pitchx said in Error while trying to update MM, GA, EXT ec:
git reset --hard && git pull
I did it and here is the result :
HEAD est maintenant à f14e956 Create Thai Language file (#3028)
astuce: Tirer sans spécifier comment réconcilier les branches divergentes
astuce: est découragé. Vous pouvez éliminer ce message en lançant une des
astuce: commandes suivantes avant votre prochain tirage :
astuce:
astuce: git config pull.rebase false # fusion (stratégie par défaut)
astuce: git config pull.rebase true # rebasage
astuce: git config pull.ff only # avance rapide seulement
astuce:
astuce: Vous pouvez remplacer “git config” par “git config --global” pour que
astuce: ce soit l’option par défaut pour tous les dépôts. Vous pouvez aussi
astuce: passer --rebase, --no-rebase ou --ff-only sur la ligne de commande pour
astuce: remplacer à l’invocation la valeur par défaut configurée.
remote: Enumerating objects: 621, done.
remote: Counting objects: 100% (621/621), done.
remote: Compressing objects: 100% (261/261), done.
remote: Total 427 (delta 301), reused 260 (delta 148), pack-reused 0
Réception d’objets: 100% (427/427), 328.14 Kio | 3.13 Mio/s, fait.
Résolution des deltas: 100% (301/301), complété avec 146 objets locaux.
Depuis https://github.com/MichMich/MagicMirror
f14e956…343e7de master -> origin/master- [nouvelle étiquette] v2.25.0 -> v2.25.0
- [nouvelle étiquette] v2.23.0 -> v2.23.0
- [nouvelle étiquette] v2.24.0 -> v2.24.0
Mise à jour f14e956…343e7de
Fast-forward
.eslintrc.json | 13 ±
.gitattributes | 56 +
…
…
…
vendor/package-lock.json | 57 ±
vendor/package.json | 7 ±
205 files changed, 10611 insertions(+), 10805 deletions(-)
create mode 100644 .gitattributes
rename .github/{ISSUE_TEMPLATE.md => ISSUE_TEMPLATE/custom.md} (90%)
delete mode 100644 .github/workflows/enforce-changelog.yaml
create mode 100644 .github/workflows/enforce-pullrequest-rules.yaml
create mode 100644 .npmrc
create mode 100644 js/animateCSS.js
delete mode 100644 js/fetch.js
create mode 100644 modules/default/alert/translations/th.json
create mode 100644 modules/default/calendar/calendarfetcherutils.js
create mode 100644 modules/default/weather/providers/overrideWrapper.js
rename modules/default/weather/providers/{darksky.js => pirateweather.js} (76%)
create mode 100644 tests/configs/modules/calendar/show-duplicates-in-calendar.js
create mode 100644 tests/configs/modules/clock/clock_showDateAnalog.js
create mode 100644 tests/configs/modules/clock/clock_showSunMoon.js
create mode 100644 tests/configs/modules/compliments/compliments_animateCSS.js
create mode 100644 tests/configs/modules/compliments/compliments_animateCSS_fallbackToDefault.js
create mode 100644 tests/configs/modules/compliments/compliments_animateCSS_invertedAnimationName.js
create mode 100644 tests/configs/modules/weather/hourlyweather_default.js
create mode 100644 tests/configs/modules/weather/hourlyweather_options.js
create mode 100644 tests/configs/modules/weather/hourlyweather_showPrecipitation.js
create mode 100644 tests/configs/port_variable.env
create mode 100644 tests/configs/port_variable.js.template
create mode 100644 tests/e2e/animateCSS_spec.js
create mode 100644 tests/e2e/modules/weather_hourly_spec.js
create mode 100644 tests/e2e/serveronly_spec.js
create mode 100644 tests/e2e/template_spec.js
create mode 100644 tests/mocks/calendar_test_clone.ics
create mode 100644 tests/mocks/weather_current.json
create mode 100644 tests/mocks/weather_forecast.json
create mode 100644 tests/mocks/weather_hourly.json
delete mode 100644 tests/mocks/weather_test.js
delete mode 100644 tests/unit/functions/weather_object_spec.js
create mode 100644 tests/unit/helpers/global-setup.js
create mode 100644 tests/unit/modules/default/calendar/calendar_fetcher_utils_spec.js
rename tests/unit/{functions/calendar_spec.js => modules/default/calendar/calendar_utils_spec.js} (52%)
create mode 100644 tests/unit/modules/default/weather/weather_object_spec.js
create mode 100644 tests/unit/modules/default/weather/weather_utils_spec.js
rename tests/{configs => utils}/test_sequencer.js (66%)
create mode 100644 tests/utils/weather_mocker.js
rename th.json => translations/th.json (100%)
What should I do?
Thanks,
Adel -
@adel51 said in Error while trying to update MM, GA, EXT ec:
npm run install
-
Or maybe this can help
-
@bugsounet
Salut,
Purée ! je suis reparti d’une sauvegarde qui fonctionnait très bien afin de mettre à jour tous les modules vers leurs versions récentes. J ai donc copié ma sauvegarde sur la SD. En voulant tester mon miroir avant les MAJ , j ai l’erreur suivante quand j’essaie de questionner GA (jarvis) pour lui demander l’heure par exemple. Dois je corriger l erreur avant de tenter les MAJ des modules? Voici l heure :
[22.10.2023 23:48.26.500] [LOG] [DETECTOR] Starts listening. 1 Models
[22.10.2023 23:49.20.100] [LOG] [DETECTOR] Stops listening.
[22.10.2023 23:49.20.101] [LOG] [DETECTOR] Detected: jarvis from: Snowboy
[22.10.2023 23:49.20.858] [LOG] [GA:AS] CONVERSATION_ERROR: Error: 2 UNKNOWN: Getting metadata from plugin failed with error: invalid_grant
[22.10.2023 23:49.21.011] [LOG] [DETECTOR] Starts listening. 1 ModelsMerci d’avance,
Adel -
Hi,
before updating MM and GA, now I have this error after saying ‘Jarvis’ in the mic :MagicMirror: v2.22.0
[GA] MMM-GoogleAssistant Version: 4.2.2 rev: 230227…
[23.10.2023 13:00.36.705] [LOG] [DETECTOR] Stops listening.
[23.10.2023 13:00.36.706] [LOG] [DETECTOR] Detected: jarvis from: Snowboy
[23.10.2023 13:00.37.759] [LOG] [GA:AS] CONVERSATION_ERROR: Error: 2 UNKNOWN: Getting metadata from plugin failed with error: invalid_grant
[23.10.2023 13:00.37.965] [LOG] [DETECTOR] Starts listening. 1 ModelsHow to resolve it please?
@bugsounet !?
Adel -
- update to MM² v2.25
- update to GA v5.4.x
- @bugsounet said in Error while trying to update MM, GA, EXT ec:
Or maybe this can help
- Don’t open another issue for this problem
-
@bugsounet
I already tried but it didn’t work !I will try again.
First, I need to upgrade node version to v18.x
For that, should i execute each line alone one after one or , all the lines in one command in the terminal ?here are the lines :
sudo apt-get update && sudo apt-get install -y ca-certificates curl gnupg
curl -fsSL https://deb.nodesource.com/gpgkey/nodesource-repo.gpg.key | sudo gpg --dearmor -o /etc/apt/keyrings/nodesource.gpg
echo “deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_18.x nodistro main” | sudo tee /etc/apt/sources.list.d/nodesource.list
sudo apt-get update && sudo apt-get install nodejs -ythanks,
Adel -
@adel51
I used nvm to upgrade node version to 18.18.2here is the tutorial :
https://github.com/nvm-sh/nvm#troubleshooting-on-linux
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.5/install.sh | bash
then,
nvm install 18.18.2
And it works well!
Now, i need to upgrade MM. -
@adel51
the upgrade MagicMirror² to v2.25.x is ok !the upgrade of npm from 9.8.1 -> 10.2.1 is ok !
the upgrade of MMM-GoogleAssistant to v5.4.3 is ok !
the update of all MMM-GoogleAssistant components is NOT ok !!!
here is the error (log) :
rpi@raspberrypi:~/MagicMirror/modules/MMM-GoogleAssistant $ npm run refresh
MMM-GoogleAssistant@5.4.3 refresh
node installer/refresh.jsStart Refreshing and Updating MMM-GoogleAssistant, Gateway and EXTs
Skipped: ATO-MM1_TO_MM2
Found: EXT-Alert
⠴ Updating: EXT-Alert…
npm
ERR! Missing script: “clean”
npm ERR!
npm ERR! To see a list of scripts, run:
npm ERR!npm run
npm
ERR!
A complete log of this run can be found in: /home/rpi/.npm/_logs/2023-10-23T23_13_50_521Z-debug-0.log
Failed: Error Detected!
Result:
➤ Updated: 0/65
➤ Failed: 1/65
➤ Skipped: 1/65Please, how to resolve it?
thanks,
Adel -
Hello,
so, I decided to update Gateway, EXT-Detector and EXT-Alert : the updates are ok !I launched my magic mirror and I have the error (with GA i think) when I talk to 'Jarvis ':
[24.10.2023 12:09.19.767] [LOG] [DETECTOR] [RULES] Start listening. 1 Models
[24.10.2023 12:09.29.429] [LOG] [DETECTOR] [RULES] Stop listening.
[24.10.2023 12:09.29.429] [LOG] [DETECTOR] [RULES] Detected: jarvis from: Snowboy
[24.10.2023 12:09.31.310] [LOG] [GA] [ASSISTANT] CONVERSATION_ERROR: Error: 2 UNKNOWN: Getting metadata from plugin failed with error: invalid_grantPlease, @bugsounet help or any idea?
Thanks by advance.
Adel -
Just renew your token because it’s old
-
Hi,
that is what I thought yesterday. But when I generate another one, the file contains the same informations. So, I will try to do it, it will just change the date of the file. Am I right?
Tx @bugsounet -
npm run token
-
@bugsounet Ah OK sorry ! Now, it works !
-