-
Notifications
You must be signed in to change notification settings - Fork 3.9k
Crash when Trading with kraken #535
Comments
Thanks will check it out. Does this happen a lot? |
Hello ! Same here,
Another case : 2017-01-05 00:42:32 (DEBUG): getting balance & fee from kraken
|
Same here, seems to be a problem when trying to sell and you have nothing to sell so value is empty i may have ofund something in Trader.prototype.addOrder if(_.isEmpty(data)) |
Hey Mike, yes this happens every 2nd - 3rd real time trade.. |
I just experienced exactly the same error after real trading in Kraken for about 5 hours:
|
Same errors here....
|
@jebbgrenham I am working on a reimplementation of the trader as we speak (that also supports the UI), that will def fix this as well. Though it's a lot of work, progress can be followed here: #737 |
@askmike thanks for the huge amounts of work. I tried the new kraken exchange code as I was getting the exception on every run with kraken. This is the new problem with this new code
|
Sorry ignore previous message - did not have sufficient privileges on API keys |
Actually I'm still having problems with Kraken. Despite full privileges this has happened twice now on the live trader on 2 different days. Have not had any successful trades recently. On holiday currently so will try and give more debug info when I'm back, however because of a lack of exception handling, I would never be notified of such an occurrence which is actually another issue in its own right. This is the new exchange controller. |
Hi, I've exactly the same issues as described above. Does this mean you cannot trade on Kraken live until the new UI is released? has someone figured out a workaround maybe? |
@jwijmans this should be fixed in an upcoming release. I just now pushed this fix to the develop branch: https://github.com/askmike/gekko/tree/develop Can you download that one and try again? |
Good morning,
this error message is almost happening every attempt gekko makes a trade.
The text was updated successfully, but these errors were encountered: