This repository has been archived by the owner on Feb 15, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2k
Property 'exchange_id' undefined #981
Labels
Comments
Please fix it.
|
On the latest master, I do not get this error.
|
This was referenced Mar 29, 2021
# for free
to subscribe to this conversation on GitHub.
Already have an account?
#.
Anyone else who gets the following errors after a fresh install using the latest master branch? This did work on a previous version (using the same conf.js). The used exchange/product is GDAX.LTC-BTC -->
osmc@osmc:~/zenbot_new$ zenbot balance
/home/osmc/zenbot_new/lib/engine.js:17
s.exchange = get('exchanges.' + so.selector.exchange_id)
TypeError: Cannot read property 'exchange_id' of undefined
at /home/osmc/zenbot_new/lib/engine.js:17:49
at Command. (/home/osmc/zenbot_new/commands/balance.js:33:39)
at Command.listener (/home/osmc/zenbot_new/node_modules/commander/index.js:315:8)
at Command.emit (events.js:159:13)
at Command.parseArgs (/home/osmc/zenbot_new/node_modules/commander/index.js:653:12)
at Command.parse (/home/osmc/zenbot_new/node_modules/commander/index.js:475:21)
at /home/osmc/zenbot_new/zenbot.js:39:11
at /home/osmc/zenbot_new/boot.js:24:7
at f (/home/osmc/zenbot_new/node_modules/once/once.js:25:25)
at Glob. (/home/osmc/zenbot_new/node_modules/glob/glob.js:151:7)
at Glob.emit (events.js:159:13)
at Glob._finish (/home/osmc/zenbot_new/node_modules/glob/glob.js:197:8)
at done (/home/osmc/zenbot_new/node_modules/glob/glob.js:182:14)
at Glob.processGlobStar2 (/home/osmc/zenbot_new/node_modules/glob/glob.js:637:12)
at /home/osmc/zenbot_new/node_modules/glob/glob.js:626:10
at RES (/home/osmc/zenbot_new/node_modules/inflight/inflight.js:31:16)
at f (/home/osmc/zenbot_new/node_modules/once/once.js:25:25)
at lstatcb (/home/osmc/zenbot_new/node_modules/glob/glob.js:519:7)
at RES (/home/osmc/zenbot_new/node_modules/inflight/inflight.js:31:16)
at f (/home/osmc/zenbot_new/node_modules/once/once.js:25:25)
at FSReqWrap.oncomplete (fs.js:167:5)
The text was updated successfully, but these errors were encountered: