MagicMirror Forum
    • Recent
    • Tags
    • Unsolved
    • Solved
    • MagicMirror² Repository
    • Documentation
    • 3rd-Party-Modules
    • Donate
    • Discord
    • Register
    • Login
    1. Home
    2. drfukc
    3. Posts
    A New Chapter for MagicMirror: The Community Takes the Lead
    Read the statement by Michael Teeuw here.
    D
    Offline
    • Profile
    • Following 0
    • Followers 0
    • Topics 6
    • Posts 22
    • Groups 0

    Posts

    Recent Best Controversial
    • RE: RMV module issue (no live data)

      @sdetweil
      I am unsure if we are talking about the same thing.
      I understand you are referring to this file:

      /home/pi/MagicMirror/config/config.js
      

      I see the issue in this file:

      /home/pi/MagicMirror/modules/MMM-RMV/MMM-RMV.js
      

      To get it to work, both files need to be edited in the current version.

      posted in Troubleshooting
      D
      drfukc
    • RE: RMV module issue (no live data)

      @all
      now I found the issue and created a Github pullrequest for the RMV module:

      In addition to the regular config file, RMV ships by default with another file:
      /home/pi/MagicMirror/modules/MMM-RMV/MMM-RMV.js

      In this file you will find below variables that are prefilled with data that will in most cases not work for the average user:

      stationId: '', // update required here
      fDestination1: '', // update required here
      fDestination2: '', // update required here
      

      These variables need updates.
      After a successful update, the RMV module does work nicely even with buses :-)

      posted in Troubleshooting
      D
      drfukc
    • RE: Calendar issue with 2.7.1

      @sdetweil
      Thanks a lot, - this helped :-) , it is so much easier if things are done right straight from the beginning :-D

      In addition I also found the root cause for above reported “EADDRINUSE” error.
      Simple again: I have enabled MagicMirror autostart in /home/pi/MagicMirror/installers/mm.sh, but don’t see it since I use a Remote Desktop connection (RDP) that gives me a different X-Window in comparison to the native Raspberry desktop.
      Now launching Magic Mirror a second time on a different desktop and the same port causes the issue.
      Since I disabled MM autostart Magic Mirror boots up without these errors.
      Maybe I should get back from XRDP and switch to the preinstalled VNC to avoid having multiple desktops.

      Again, thanks a lot for your support :-)

      posted in Bug Hunt
      D
      drfukc
    • RE: Calendar issue with 2.7.1

      Thanks for your advise. After launching the mirror I do a pm2 list with the following result:

      pi@raspberrypi:~/MagicMirror $ pm2 list
      +-------------------------------------------------------+
      ¦ Name        ¦ id ¦ mode ¦ status ¦ ? ¦ cpu ¦ memory   ¦
      +-------------+----+------+--------+---+-----+----------¦
      ¦ MagicMirror ¦ 0  ¦ fork ¦ online ¦ 0 ¦ 0%  ¦ 2.5 MB   ¦
      +-------------------------------------------------------+
       Use `pm2 show <id|name>` to get more details about an app
      

      With this information I stop the MagicMirror by the following command: pm2 stop 0

      pi@raspberrypi:~ $ pm2 stop 0
      [PM2] Applying action stopProcessId on app [0](ids: 0)
      [PM2] [MagicMirror](0) ?
      +------------------------------------------------------+
      ¦ Name        ¦ id ¦ mode ¦ status  ¦ ? ¦ cpu ¦ memory ¦
      +-------------+----+------+---------+---+-----+--------¦
      ¦ MagicMirror ¦ 0  ¦ fork ¦ stopped ¦ 0 ¦ 0%  ¦ 0 B    ¦
      +------------------------------------------------------+
      Use `pm2 show <id|name>` to get more details about an app
      
      

      By surprise the running MagicMirror survives and I kill the Electron instance with kill
      After the MagicMirror instance is terminated I relaunch MagicMirror again with npm start &
      The funny thing is that the naughty EADDRINUSE message is gone by now, but the calendar is still not working:

      pi@raspberrypi:~/MagicMirror $ npm start &
      [2] 1279
      [1]   Fertig                  npm start
      pi@raspberrypi:~/MagicMirror $ 
      > magicmirror@2.7.1 start /home/pi/MagicMirror
      > sh run-start.sh
      
      Starting MagicMirror: v2.7.1
      Loading config ...
      Loading module helpers ...
      No helper found for module: alert.
      Initializing new module helper ...
      Module helper loaded: updatenotification
      No helper found for module: clock.
      Initializing new module helper ...
      Module helper loaded: calendar
      Initializing new module helper ...
      Module helper loaded: newsfeed
      All module helpers loaded.
      Starting server on port 8081 ... 
      Server started ...
      Connecting socket for: updatenotification
      Connecting socket for: calendar
      Starting node helper for: calendar
      Connecting socket for: newsfeed
      Starting module: newsfeed
      Sockets connected & modules started ...
      Launching application.
      Create new calendar fetcher for url: http://www.calendarlabs.com/templates/ical/US-Holidays.ics - Interval: 300000
      Create new news fetcher for url: http://www.tagesschau.de/xml/rss2 - Interval: 300000
      

      OK, as said above I have relaunched the mirror by npm start & and try to evaluate what is going on with pm2 list:

      pi@raspberrypi:~ $ pm2 list
      +------------------------------------------------------+
      ¦ Name        ¦ id ¦ mode ¦ status  ¦ ? ¦ cpu ¦ memory ¦
      +-------------+----+------+---------+---+-----+--------¦
      ¦ MagicMirror ¦ 0  ¦ fork ¦ stopped ¦ 0 ¦ 0%  ¦ 0 B    ¦
      +------------------------------------------------------+
       Use `pm2 show <id|name>` to get more details about an app
      

      It’s funny, pm2 list tells me that the Mirror has stopped, while it is still running, but I still do not recieve any Calendar updates.
      What is wrong here?

      posted in Bug Hunt
      D
      drfukc
    • RE: Calendar issue with 2.7.1

      @sdetweil
      Thanks for your comment.
      First I changed the port as recommended in mm/config/config.js to 8081 and gave it a reboot.
      After reboot and logon I checked the network connections by sudo netstat -lnptu:

      pi@raspberrypi:~ $ sudo netstat -lnptu
      Aktive Internetverbindungen (Nur Server)
      Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
      tcp        0      0 127.0.0.1:8081          0.0.0.0:*               LISTEN      836/electron.js     
      tcp6       0      0 :::21                   :::*                    LISTEN      418/vsftpd          
      tcp6       0      0 ::1:3350                :::*                    LISTEN      446/xrdp-sesman     
      tcp6       0      0 :::3389                 :::*                    LISTEN      461/xrdp            
      udp        0      0 0.0.0.0:5353            0.0.0.0:*                           318/avahi-daemon: r 
      udp        0      0 0.0.0.0:68              0.0.0.0:*                           348/dhcpcd          
      udp        0      0 0.0.0.0:47216           0.0.0.0:*                           318/avahi-daemon: r 
      udp6       0      0 :::5353                 :::*                                318/avahi-daemon: r 
      udp6       0      0 :::34261                :::*                                318/avahi-daemon: r 
      

      I am surprised to see Electron already listening on port 8081, though I have not started the MagicMirror.
      In the next step I launch Magic Mirror by calling: npm start &

      Unfortunately I see again a EADDRINUSE message (port 8081):

      Server started ...
      Connecting socket for: updatenotification
      Connecting socket for: calendar
      Starting node helper for: calendar
      Connecting socket for: newsfeed
      Starting module: newsfeed
      Sockets connected & modules started ...
      Whoops! There was an uncaught exception...
      { Error: listen EADDRINUSE 127.0.0.1:8081
          at Server.setupListenHandle [as _listen2] (net.js:1330:14)
          at listenInCluster (net.js:1378:12)
          at GetAddrInfoReqWrap.doListen [as callback] (net.js:1492:7)
          at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:55:10)
        errno: 'EADDRINUSE',
        code: 'EADDRINUSE',
        syscall: 'listen',
        address: '127.0.0.1',
        port: 8081 }
      MagicMirror will not quit, but it might be a good idea to check why this happened. Maybe no internet connection?
      If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues
      Launching application.
      

      While the mirror is running I execute again sudo netstat -lnptu and get:

      pi@raspberrypi:~/MagicMirror $ sudo netstat -lnptu
      Aktive Internetverbindungen (Nur Server)
      Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name    
      tcp        0      0 127.0.0.1:8081          0.0.0.0:*               LISTEN      888/electron.js     
      tcp6       0      0 :::21                   :::*                    LISTEN      435/vsftpd          
      tcp6       0      0 ::1:3350                :::*                    LISTEN      450/xrdp-sesman     
      tcp6       0      0 :::3389                 :::*                    LISTEN      465/xrdp            
      udp        0      0 0.0.0.0:42644           0.0.0.0:*                           318/avahi-daemon: r 
      udp        0      0 0.0.0.0:5353            0.0.0.0:*                           318/avahi-daemon: r 
      udp        0      0 0.0.0.0:68              0.0.0.0:*                           354/dhcpcd          
      udp6       0      0 :::42148                :::*                                318/avahi-daemon: r 
      udp6       0      0 :::5353                 :::*                                318/avahi-daemon: r 
      

      This is strange. The launch of the mirror npm start & tells me a multiple use of the port 8080 or 8081 (whatever it set in config.js) but netstat -lnptu does not know anything about a duplicate use.

      As advised I also added below line right after if (event.type === “VEVENT”) { in ftp://192.168.178.36/home/pi/MagicMirror/modules/default/calendar/calendarfetcher.js

      console.log("have event title="+event.summary);
      

      Unfortunately the console outcome again is: “EADDRINUSE”

      Initializing new module helper ...
      Module helper loaded: calendar
      Initializing new module helper ...
      Module helper loaded: newsfeed
      All module helpers loaded.
      Starting server on port 8081 ... 
      Server started ...
      Connecting socket for: updatenotification
      Connecting socket for: calendar
      Starting node helper for: calendar
      Connecting socket for: newsfeed
      Starting module: newsfeed
      Sockets connected & modules started ...
      Whoops! There was an uncaught exception...
      { Error: listen EADDRINUSE 127.0.0.1:8081
          at Server.setupListenHandle [as _listen2] (net.js:1330:14)
          at listenInCluster (net.js:1378:12)
          at GetAddrInfoReqWrap.doListen [as callback] (net.js:1492:7)
          at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:55:10)
        errno: 'EADDRINUSE',
        code: 'EADDRINUSE',
        syscall: 'listen',
        address: '127.0.0.1',
        port: 8081 }
      MagicMirror will not quit, but it might be a good idea to check why this happened. Maybe no internet connection?
      If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues
      Launching application.
      

      I feel a little bit lost … … …

      posted in Bug Hunt
      D
      drfukc
    • RE: Calendar issue with 2.7.1

      @sdetweil

      Hi Sam,
      the calendar entry I use for testing is the standard URL:

      url: "webcal://www.calendarlabs.com/templates/ical/US-Holidays.ics"
      

      As advised by you I searched up-and-down my calendarfetcher.js in:
      /home/pi/MagicMirror/modules/default/calendar/calendarfetcher.js

      I can find the following string: if (event.type === “VEVENT”) {
      But I cannot even find substring to uncomment such like this: console.log("have or event title or
      Hence there seems to be nothing to uncomment

      I rather believe my issue has something to do with to many Electron instances that kill several moduls.
      Maybe you have an idea for this:

      1. I boot up my raspberry 3b
      2. Execute ‘ps -a’ to check the running processes
      3. ‘ps -a’ returns ‘ps’ as the only running processes
      4. launching the mirror: ‘npm start &’
      5. the console tells me uncaught exception since EADDRINUSE is already in use:

      magicmirror@2.7.1 start /home/pi/MagicMirror
      sh run-start.sh

      Starting MagicMirror: v2.7.1
      Loading config ...
      Loading module helpers ...
      No helper found for module: alert.
      Initializing new module helper ...
      Module helper loaded: updatenotification
      No helper found for module: clock.
      Initializing new module helper ...
      Module helper loaded: calendar
      Initializing new module helper ...
      Module helper loaded: newsfeed
      All module helpers loaded.
      Starting server on port 8080 ... 
      Server started ...
      Connecting socket for: updatenotification
      Connecting socket for: calendar
      Starting node helper for: calendar
      Connecting socket for: newsfeed
      Starting module: newsfeed
      Sockets connected & modules started ...
      Whoops! There was an uncaught exception...
      { Error: listen EADDRINUSE 127.0.0.1:8080
          at Server.setupListenHandle [as _listen2] (net.js:1330:14)
          at listenInCluster (net.js:1378:12)
          at GetAddrInfoReqWrap.doListen [as callback] (net.js:1492:7)
          at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:55:10)
        errno: 'EADDRINUSE',
        code: 'EADDRINUSE',
        syscall: 'listen',
        address: '127.0.0.1',
        port: 8080 }
      MagicMirror will not quit, but it might be a good idea to check why this happened. Maybe no internet connection?
      If you think this really is an issue, please open an issue on GitHub: https://github.com/MichMich/MagicMirror/issues
      
      1. Now I recheck my running processes and see *four instances of Electron. According to another thread it looks like I run two instances of MagicMirror in parallel, that have a conflict with each other and causing this EADDRINUSE message:
      PID TTY          TIME CMD
       1176 pts/0    00:00:01 npm
       1187 pts/0    00:00:00 sh
       1188 pts/0    00:00:00 sh
       1189 pts/0    00:00:00 node
       1196 pts/0    00:00:30 electron
       1198 pts/0    00:00:00 electron
       1236 pts/0    00:00:00 electron
       1238 pts/0    00:00:15 electron
       1305 pts/1    00:00:00 ps
      
      1. Checking PM2 by ‘pm2 list’ gives me only one instance:
      pi@raspberrypi:~ $ pm2 list
      +-------------------------------------------------------+
      ¦ Name        ¦ id ¦ mode ¦ status ¦ ? ¦ cpu ¦ memory   ¦
      +-------------+----+------+--------+---+-----+----------¦
      ¦ MagicMirror ¦ 0  ¦ fork ¦ online ¦ 0 ¦ 0%  ¦ 2.5 MB   ¦
      +-------------------------------------------------------+
      
      1. For more details I try pm2 show 0
      pi@raspberrypi:~ $ pm2 show 0
       Describing process with id 0 - name MagicMirror 
      +--------------------------------------------------------------+
      ¦ status            ¦ online                                   ¦
      ¦ name              ¦ MagicMirror                              ¦
      ¦ version           ¦ 2.7.1                                    ¦
      ¦ restarts          ¦ 0                                        ¦
      ¦ uptime            ¦ 16m                                      ¦
      ¦ script path       ¦ /home/pi/MagicMirror/installers/mm.sh    ¦
      ¦ script args       ¦ N/A                                      ¦
      ¦ error log path    ¦ /home/pi/.pm2/logs/MagicMirror-error.log ¦
      ¦ out log path      ¦ /home/pi/.pm2/logs/MagicMirror-out.log   ¦
      ¦ pid path          ¦ /home/pi/.pm2/pids/MagicMirror-0.pid     ¦
      ¦ interpreter       ¦ bash                                     ¦
      ¦ interpreter args  ¦ N/A                                      ¦
      ¦ script id         ¦ 0                                        ¦
      ¦ exec cwd          ¦ /home/pi/MagicMirror                     ¦
      ¦ exec mode         ¦ fork_mode                                ¦
      ¦ node.js version   ¦ N/A                                      ¦
      ¦ node env          ¦ N/A                                      ¦
      ¦ watch & reload    ¦ ?                                        ¦
      ¦ unstable restarts ¦ 0                                        ¦
      ¦ created at        ¦ 2019-04-06T11:57:10.685Z                 ¦
      +--------------------------------------------------------------+
       Revision control metadata 
      +---------------------------------------------------------------------+
      ¦ revision control ¦ git                                              ¦
      ¦ remote url       ¦ https://github.com/MichMich/MagicMirror.git      ¦
      ¦ repository root  ¦ /home/pi/MagicMirror                             ¦
      ¦ last update      ¦ 2019-04-15T06:53:55.840Z                         ¦
      ¦ revision         ¦ b508a629e8a727358f1b88e3c7df842d14669ec4         ¦
      ¦ comment          ¦ Merge pull request #1632 from MichMich/fix-2.7.1 ¦
      ¦                  ¦                                                  ¦
      ¦                  ¦ Fix package.json version number.                 ¦
      ¦ branch           ¦ master                                           ¦
      +---------------------------------------------------------------------+
      

      Any ideas?

      posted in Bug Hunt
      D
      drfukc
    • RE: Calendar issue with 2.7.1

      Hi Dommer,
      Quite similar with me. I have a fresh Raspberry installation on my Pi-3B, the only additional packages installed are vsftpd (FTP-tool) and xrdp (RDP-server to allow Windows Remote Desktop Connections). On this fresh installation I have installed MagicMirror² and default Weather- and News app are working fine receiving live data.
      For some reason the calendar app does not work and I get the same error message for the calendar module as you in my log-file:

      ./home/pi/.pm2/logs/MagicMirror-error.log

      ATTENTION: default value of option force_s3tc_enable overridden by environment.
      TypeError: Cannot read property 'length' of undefined
          at eventDate (/home/pi/MagicMirror/modules/default/**calendar/calendarfetcher.js:69:25)
          at /home/pi/MagicMirror/modules/default/calendar/calendarfetcher.js:90:22
          at Request._callback (/home/pi/MagicMirror/modules/default/calendar/vendor/ical.js/node-ical.js:11:5)
          at Request.self.callback (/home/pi/MagicMirror/node_modules/request/request.js:185:22)
          at Request.emit (events.js:182:13)
          at Request.<anonymous> (/home/pi/MagicMirror/node_modules/request/request.js:1157:10)
          at Request.emit (events.js:182:13)
          at IncomingMessage.<anonymous> (/home/pi/MagicMirror/node_modules/request/request.js:1079:12)
          at Object.onceWrapper (events.js:273:13)
          at IncomingMessage.emit (events.js:187:15)
      

      I reinstalled from scratch on another SD-card with the same result.

      posted in Bug Hunt
      D
      drfukc
    • RE: Update to MagicMirror² v2.7.0 fails

      Hi Sam,
      thanks for your support, but unfortunately this takes me to the next issue when executing:

      pi@magicmirror:~ $ npm -v
      6.9.0
      
      pi@magicmirror:~/MagicMirror $ npm install -g npm
      npm WARN checkPermissions Missing write access to /usr/lib/node_modules
      npm ERR! path /usr/lib/node_modules
      npm ERR! code EACCES
      npm ERR! errno -13
      npm ERR! syscall access
      

      After, I changed permissions for /usr/lib/node_modules, but it simply took me to the next error.
      I think I will re-start from scratch.
      Cheers
      ukc

      posted in Tutorials
      D
      drfukc
    • RE: Update to MagicMirror² v2.7.0 fails

      @sdetweil
      partially it worked though the upgrade still terminates with this error message after running “sudo npm install” in the MM directory and all external modules that have a package.json file.
      However, all of these have prompted me that they are already up-to-date.

      These are my steps:

      pi@magicmirror:~/MagicMirror $ sudo npm install
      npm WARN deprecated time-grunt@2.0.0: Deprecated because Grunt is practically unmaintained. Move on to something better. This package will continue to work with Grunt v1, but it will not receive any updates.
      npm WARN tar ENOENT: no such file or directory, open '/home/pi/MagicMirror/node_modules/.staging/eslint-8983ee3d/LICENSE'
      npm WARN tar ENOENT: no such file or directory, open '/home/pi/MagicMirror/node_modules/.staging/eslint-8983ee3d/README.md'
      
      ... tons of similar WARNINGS in between ... and removed here for better removed for better readability
      
      npm WARN tar ENOENT: no such file or directory, open '/home/pi/MagicMirror/node_modules/.staging/lodash-9ecaa656/lastIndexOf.js'
      npm WARN tar ENOENT: no such file or directory, open '/home/pi/MagicMirror/node_modules/.staging/lodash-9ecaa656/LICENSE'
      npm WARN tar ENOENT: no such file or directory, open '/home/pi/MagicMirror/node_modules/.staging/lodash-9ecaa656/lodash.js'
      npm WARN acorn-jsx@5.0.1 requires a peer of acorn@^6.0.0 but none is installed. You must install peer dependencies yourself.
      npm WARN grunt-stylelint@0.10.1 requires a peer of stylelint@^9.0.0 but none is installed. You must install peer dependencies yourself.
      
      npm ERR! err.code.match is not a function
      
      npm ERR! A complete log of this run can be found in:
      npm ERR!     /root/.npm/_logs/2019-04-05T07_27_16_446Z-debug.log
      

      now I check “2019-04-05T07_27_16_446Z-debug.log” but unfortunately this does not help me either:

      842 silly saveTree ├── valid-url@1.0.9
      842 silly saveTree └─┬ walk@2.3.14
      842 silly saveTree   └── foreachasync@3.0.0
      843 warn acorn-jsx@5.0.1 requires a peer of acorn@^6.0.0 but none is installed. You must install peer dependencies yourself.
      844 warn grunt-stylelint@0.10.1 requires a peer of stylelint@^9.0.0 but none is installed. You must install peer dependencies yourself.
      845 verbose stack TypeError: err.code.match is not a function
      845 verbose stack     at BB.try.catch.err (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/with-tarball-stream.js:110:55)
      845 verbose stack     at tryCatcher (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/util.js:16:23)
      845 verbose stack     at Promise._settlePromiseFromHandler (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:512:31)
      845 verbose stack     at Promise._settlePromise (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:569:18)
      845 verbose stack     at Promise._settlePromise0 (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:614:10)
      845 verbose stack     at Promise._settlePromises (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:690:18)
      845 verbose stack     at _drainQueueStep (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:138:12)
      845 verbose stack     at _drainQueue (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:131:9)
      845 verbose stack     at Async._drainQueues (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:147:5)
      845 verbose stack     at Immediate.Async.drainQueues (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:17:14)
      845 verbose stack     at runCallback (timers.js:794:20)
      845 verbose stack     at tryOnImmediate (timers.js:752:5)
      845 verbose stack     at processImmediate [as _immediateCallback] (timers.js:729:5)
      846 verbose cwd /home/pi/MagicMirror
      847 verbose Linux 4.14.98-v7+
      848 verbose argv "/usr/bin/node" "/usr/local/bin/npm" "install"
      849 verbose node v8.11.1
      850 verbose npm  v6.9.0
      851 error err.code.match is not a function
      852 verbose exit [ 1, true ]
      

      When opening MagicMirror it looks like I have v2.7.0 installed, since the upgrading message has disappeared and things seem functional.

      However my feeling is that the upgrade is just in the middle of somewhere, though the mirror is working.

      Cheers
      ukc

      posted in Tutorials
      D
      drfukc
    • Update to MagicMirror² v2.7.0 fails

      Hi MagicMirror fans,
      I try to update my v2.6.0 installation to v2.7.0 with executing the following steps:

      1. sudo apt-get update
      2. sudo apt-get dist-upgrade
      3. reboot

      all steps above without errors, and now from inside the MagicMirror directory:

      1. git pull && npm install

      This throws me the following errors lines:

      Aktualisiere de57daa..b508a62
      error: Ihre lokalen Änderungen in den folgenden Dateien würden durch den Merge
      überschrieben werden:
      	package-lock.json
      	vendor/package-lock.json
      Bitte committen oder stashen Sie Ihre Änderungen, bevor sie mergen.
      
      Please, commit your changes or stash them before you can merge.
      
      Abbruch
      

      Looks like a simple git issue, but what are the recommended steps to solve this issue?
      How do I commit my changes?

      running this command?

      git commit -m
      

      Hope you can help :-)

      Cheers
      ukc

      posted in Tutorials
      D
      drfukc
    • 1 / 1