Erro de rejeição about foxbit_bot HOT 4 OPEN

Up +1. Mesmo problema.

from foxbit_bot.

e as vezes quando roda corretamente dá esse erro:

C:\Users\Caixa\Documents\teste\Foxbit_Bot\node_modules\blinktrade\lib\wsTranspor
t.js:165
throw new Error('Error: ' + data.Detail + ' ' + data.Description);
^

Error: Error: 16 messages in the last second Too many messages per second
at BlinkTradeWS.onMessage (C:\Users\Caixa\Documents\teste\Foxbit_Bot\node_mo
dules\blinktrade\lib\wsTransport.js:165:15)
at WebSocket.onMessage (C:\Users\Caixa\Documents\teste\Foxbit_Bot\node_modul
es\ws\lib\EventTarget.js:103:16)
at emitTwo (events.js:106:13)
at WebSocket.emit (events.js:191:7)
at Receiver._receiver.onmessage (C:\Users\Caixa\Documents\teste\Foxbit_Bot\n
ode_modules\ws\lib\WebSocket.js:146:54)
at Receiver.dataMessage (C:\Users\Caixa\Documents\teste\Foxbit_Bot\node_modu
les\ws\lib\Receiver.js:389:14)
at Receiver.getData (C:\Users\Caixa\Documents\teste\Foxbit_Bot\node_modules
ws\lib\Receiver.js:330:12)
at Receiver.startLoop (C:\Users\Caixa\Documents\teste\Foxbit_Bot\node_module
s\ws\lib\Receiver.js:165:16)
at Receiver.add (C:\Users\Caixa\Documents\teste\Foxbit_Bot\node_modules\ws\l
ib\Receiver.js:139:10)
at TLSSocket._ultron.on (C:\Users\Caixa\Documents\teste\Foxbit_Bot\node_modu
les\ws\lib\WebSocket.js:142:22)

npm ERR! Windows_NT 6.1.7601
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\
node_modules\npm\bin\npm-cli.js" "start"
npm ERR! node v6.11.2
npm ERR! npm v3.10.10
npm ERR! code ELIFECYCLE
npm ERR! [email protected] start: node index.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script 'node index.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the foxbitbot package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node index.js
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs foxbitbot
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls foxbitbot
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:
npm ERR! C:\Users\Caixa\Documents\teste\Foxbit_Bot\npm-debug.log

C:\Users\Caixa\Documents\teste\Foxbit_Bot>

from foxbit_bot.

Mesmo Problema!

`/run/media/msc/7A6C0E556C0E0D17/foxbitBot/node_modules/blinktrade/lib/wsTransport.js:165
throw new Error('Error: ' + data.Detail + ' ' + data.Description);
^

Error: Error: 16 messages in the last second Too many messages per second
at BlinkTradeWS.onMessage (/run/media/msc/7A6C0E556C0E0D17/foxbitBot/node_modules/blinktrade/lib/wsTransport.js:165:15)
at WebSocket.onMessage (/run/media/msc/7A6C0E556C0E0D17/foxbitBot/node_modules/ws/lib/EventTarget.js:103:16)
at WebSocket.emit (events.js:159:13)
at Receiver._receiver.onmessage (/run/media/msc/7A6C0E556C0E0D17/foxbitBot/node_modules/ws/lib/WebSocket.js:146:54)
at Receiver.dataMessage (/run/media/msc/7A6C0E556C0E0D17/foxbitBot/node_modules/ws/lib/Receiver.js:389:14)
at Receiver.getData (/run/media/msc/7A6C0E556C0E0D17/foxbitBot/node_modules/ws/lib/Receiver.js:330:12)
at Receiver.startLoop (/run/media/msc/7A6C0E556C0E0D17/foxbitBot/node_modules/ws/lib/Receiver.js:165:16)
at Receiver.add (/run/media/msc/7A6C0E556C0E0D17/foxbitBot/node_modules/ws/lib/Receiver.js:139:10)
at TLSSocket._ultron.on (/run/media/msc/7A6C0E556C0E0D17/foxbitBot/node_modules/ws/lib/WebSocket.js:142:22)
at TLSSocket.emit (events.js:159:13)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start: node index.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /home/msc/.npm/_logs/2017-12-22T13_08_59_942Z-debug.log`

from foxbit_bot.

Olá... tive esse problema.. e outros que já foram reportados aqui..
resolvi fazendo assim:

atualizei o node e npm
removi o node_modules
removi o cache do npm
depois só dar um npm install
e quando for rodar o index.js.. use este comando:
NODE_ENV=production node index.js (este evita o problema q reportaram de erro LyfeCicle)

from foxbit_bot.