-
Notifications
You must be signed in to change notification settings - Fork 2k
Time not updating on data fetches. Stops trading. #2404
Comments
Hi! This bug pretty much renders the bot useless - trading will not work and the graph won't render nor show info. The time stamp remains the same after executing a trade. I'm assuming the two problems are somehow linked. There is two pictures attached below illustrating the difference between an older version and the latest version on the branch. This is very frustrating as the bot will not work at all. I hope this can get resolved quickly. Thank you. |
(I'm not sure if this is directly related, so if it's not, I'll move it off to a new issue.) Since the #2425 fix, sims are -way- off on their profitability calc, and I think it has to do with time. Example: Started this run with $10k currency, finishing with 10,162 is NOT 675% profit. 2020-10-11 04:08:52 6.25370 BAND-USD +0.16% 65 59.08 ++ 6.2204 0.0026 -0.0202 59.0 sold 0.00999995 BAND 10051.99 USD-785.73%-753.60 Started this run with $10k currency, finishing with 10,051 is NOT a 785% loss. |
Another example, fresh from a darwin backtest. This is not right. { There's no way you have a 608% profit from 1 win 1 loss, trading BTC, over the last 5 days. |
No your exactly right - when I ran simulation the numbers were all over the place, often varying by thousands of dollars with a few trades. Also, when I ran the trade sim, I used the --days command, but often it wouldn't run for that exact amount of days.... I can't narrow down the problem exactly but there seems to be something wrong effecting the entire bot and its operations. |
Any love for this issue? All the bots that used to work, all hang, are completely unusable. |
System information
Describe the problem
Bug found:
When starting a trade (paper or live), most of the time, the bot starts properly, but after a while, this can be minutes or hours, the bot stops trading, and the graphs in the webinterface are not updated anymore. As it seems now, the root cause of the problem seems to be that the time is not updated properly and the system keeps retrieving the last retrieved dataset.
Logs included below.
Logs are from gdax, but it can also be reproduced on bitfinex.
Source code / Error logs
This error log contains multiple runs.
logs.log
The text was updated successfully, but these errors were encountered: