Cannot read property 'Available' of undefined

[jimbogbt]

Any thoughts?

Running the Xmas build on Bittrex.
The Bittrex website is playing up a little and not loading pages so possibly an issue their end?
Was working fine last night.

C:\snapshot\Gunbot-master\node_modules\lodash\lodash.js:537
      if (iteratee(array[index], index, array) === false) {
          ^

TypeError: Cannot read property 'Available' of undefined
    at module.exports.parseBalance._.forEach (C:\snapshot\Gunbot-master\ctx\js\bittrex.js:0:0)
    at arrayEach (C:\snapshot\Gunbot-master\node_modules\lodash\lodash.js:537:11)
    at Function.forEach (C:\snapshot\Gunbot-master\node_modules\lodash\lodash.js:9359:14)
    at Bittrex.parseBalance (C:\snapshot\Gunbot-master\ctx\js\bittrex.js:0:0)
    at C:\snapshot\Gunbot-master\ctx\js\bittrex.js:0:0
    at Request._callback (C:\snapshot\Gunbot-master\node_modules\node-bittrex-api\node.bittrex.api.js:144:11)
    at Request.init.self.callback (C:\snapshot\Gunbot-master\node_modules\request\request.js:188:22)
    at emitTwo (events.js:125:13)
    at Request.emit (events.js:213:7)
    at Request. (C:\snapshot\Gunbot-master\node_modules\request\request.js:1171:10)
    at emitOne (events.js:115:13)
    at Request.emit (events.js:210:7)
    at IncomingMessage. (C:\snapshot\Gunbot-master\node_modules\request\request.js:1091:12)
    at Object.onceWrapper (events.js:312:19)
    at emitNone (events.js:110:20)
    at IncomingMessage.emit (events.js:207:7)
    at endReadableNT (_stream_readable.js:1045:12)
    at _combinedTickCallback (internal/process/next_tick.js:102:11)
    at process._tickCallback (internal/process/next_tick.js:161:9)
C:\snapshot\Gunbot-master\node_modules\lodash\lodash.js:537
      if (iteratee(array[index], index, array) === false) {
          ^

[sloaleks]

What are you talking about? Bittrex is working just fine.

[aknetman]

I was getting the same error on the Xmas build (7.0.2) and just upgraded to v8.0.3 thinking that would stop the error, but I am still getting the identical error.
I am trading on bittrex, running on a linux box.

here is copy-paste from my error log-

Code: [Select]

TypeError: Cannot read property 'Available' of undefined
    at module.exports.parseBalance._.forEach (/snapshot/Gunbot-master/ctx/js/bittrex.js:0:0)
    at arrayEach (/snapshot/Gunbot-master/node_modules/lodash/lodash.js:537:11)
    at Function.forEach (/snapshot/Gunbot-master/node_modules/lodash/lodash.js:9359:14)
    at Bittrex.parseBalance (/snapshot/Gunbot-master/ctx/js/bittrex.js:0:0)
    at /snapshot/Gunbot-master/ctx/js/bittrex.js:0:0
    at Request._callback (/snapshot/Gunbot-master/node_modules/node-bittrex-api/node.bittrex.api.js:144:11)
    at Request.init.self.callback (/snapshot/Gunbot-master/node_modules/request/request.js:186:22)
    at emitTwo (events.js:126:13)
    at Request.emit (events.js:214:7)
    at Request. (/snapshot/Gunbot-master/node_modules/request/request.js:1163:10)
    at emitOne (events.js:116:13)
    at Request.emit (events.js:211:7)
    at IncomingMessage. (/snapshot/Gunbot-master/node_modules/request/request.js:1085:12)
    at Object.onceWrapper (events.js:313:30)
    at emitNone (events.js:111:20)
    at IncomingMessage.emit (events.js:208:7)
    at endReadableNT (_stream_readable.js:1056:12)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)
/snapshot/Gunbot-master/node_modules/lodash/lodash.js:537
      if (iteratee(array[index], index, array) === false) {
          ^

[sarog]

Just stop the bot.
Remove all json files

Code: [Select]

rm *.json
And start the bot again.

[jbpeanut82]

I'm having the same issue on 8.0.3 fresh install, watchmode, 1 pair, emotionless.  As basic as it can get.  Any ideas?

[jbpeanut82]

Did some more digging and it seems like this issue was supposed to be resolved in 8.0.3 according to this:

https://github.com/GuntharDeNiro/BTCT/wiki/New-in-803

"Fix bittrex "available of undefined""

Several have reported the issue since 7.x. 

https://github.com/GuntharDeNiro/BTCT/issues/335

Should I downgrade?

Thanks.

[bobzilla]

Did some more digging and it seems like this issue was supposed to be resolved in 8.0.3 according to this:

https://github.com/GuntharDeNiro/BTCT/wiki/New-in-803

"Fix bittrex "available of undefined""

Several have reported the issue since 7.x. 

https://github.com/GuntharDeNiro/BTCT/issues/335

Should I downgrade?

Thanks.

I'm getting the same error on Xmas edition also.  Have you had any luck getting it to work?  I can run my bot for about 30 mins and then i start to get the errors. 

[jbpeanut82]

I have not, it just crashes constantly.     

[bobzilla]

Have you tried closing out the program and restarting?

[jbpeanut82]

Have you tried closing out the program and restarting?

Yes,  I have also tried running on Ubuntu and Windows.  Versions 8.0.3 and 7.0.2.  Simple clean install working in watch mode does it every time.  Crashes after running a few hours constantly. 

[bobzilla]

Damn..  So mine is similar.  Mine will work for 30mins to an hour.  It will go about 400+ rounds then start over.  I don't know why its starting over but when it does that seems to generate the error.   I don't ever remember the bot starting over? 

[sloaleks]

of course it does. read the wiki, it's a setting.

[mhcmining]

I have the same issue. I'm running 803 on a centos 7 box.  This is really aggrevating.  Another thing happening is the web interface will lock up. It did it both on Win10 64Bit and Centos 7.

[jimbogbt]

Figured out it's not a big issue just a small communication error obtaining info from Bittrex.
Each time you see it in your logs window is an instance of it happening (though with no timestamp which would help / ease the stress)
So if you only have 4 or 5 instances of it in the window but your bot has completed about 10,000 cycles, I wouldnt worry too much.....

[jbpeanut82]

Figured out it's not a big issue just a small communication error obtaining info from Bittrex.
Each time you see it in your logs window is an instance of it happening (though with no timestamp which would help / ease the stress)
So if you only have 4 or 5 instances of it in the window but your bot has completed about 10,000 cycles, I wouldnt worry too much.....

Except it occurs more and more often the longer the bot runs.  It's not just a log entry as the bot is crashing/restarting each time.