You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 16, 2020. It is now read-only.
Hi,
I have an older version of gekko running, just watching some markets. It works fine on BTCe. Yesterday I pulled the latest stable branch into a new directory and tried to set it up.
When running node gekko I get the following error:
nohup: ignoring input
/Software/gekko/core/util.js:92
return `Gekko version: v${util.getVersion()}`
^
SyntaxError: Unexpected token ILLEGAL
at exports.runInThisContext (vm.js:73:16)
at Module._compile (module.js:443:25)
at Object.Module._extensions..js (module.js:478:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)
at Module.require (module.js:365:17)
at require (module.js:384:17)
at Object.<anonymous> (/Software/gekko/gekko.js:18:12)
at Module._compile (module.js:460:26)
at Object.Module._extensions..js (module.js:478:10)
Is this some version issue? Should I purge the old files (currently still running, in a separate directory)?
Thanks!
The text was updated successfully, but these errors were encountered:
Your node is too old most likely. What is the output of the following command?
node -v
EDIT: So there is a check to see if you node is recent enough, but in this case Node was unable to even parse the file that has the check. I am closing this for now as I am sure that it has to do with your node version (I would recommend downloading the 4.4.5 LTS version).
Hi,
I have an older version of gekko running, just watching some markets. It works fine on BTCe. Yesterday I pulled the latest stable branch into a new directory and tried to set it up.
When running
node gekko
I get the following error:Is this some version issue? Should I purge the old files (currently still running, in a separate directory)?
Thanks!
The text was updated successfully, but these errors were encountered: