Fetch data appears from the future

[cimm]

I am trying to get gekko running but can't get past the initial database building.

I start gekko and it runs for a few hours or even a day before it crashes with the following error:

FATAL: Fetch data appears from the future, don't know how to process

The node process hangs after this and I have to manually restart it. A few hours later it runs into the same problem.

I never got past this point and have no idea how to get around this. I have gekko configured to use Kraken.

I am thinking Kraken might send trades with a date that is a few seconds ahead of my system clock or there might be some timezone mix up here?

[askmike]

Looking into this. I was running a gekko on every exchange until my host decided to shutdown my server. Currently rerunning a gekko on Kraken to identify it.

I think the issue has to do with the extremely low volume. The part of Gekko that deals with storing data (flat file currently) has a lot of nasty limitations when the fetch timespan becomes to big (spans multiple UTC days). Rewriting that is high on my list!

[askmike]

I experienced the same:

https://gist.github.com/askmike/9092398#file-log2

It appears this will happen when the fetch only has trades for a new UTC day. As soon as I have time to refactor the candle manager I'll fix this!

[roever-rl]

Just want to report that i get the same error, every night.

[askmike]

I will fix this soon, but not for now I've paused kraken support (meaning that since the latest update Gekko won't work on kraken anymore because of this).

[Camille92]

Hi,

I just wanted to say that there is a stupid but effective way to bypass the problem by manually creating a very very small order (eg. €0.01) at midnight UTC on the market you are watching.
This can be done with the custom start option.

[r1979]

Hi Mike! Thanks your work so far! Any news/developments on the Kraken side?

[donttrustem]

Hi Mike,
Is there any update on this issue?

Thanks

[albuckley]

bump

+1 year...

[n4ru]

+1

[niklasrichardson]

+1 bump!

[beinbruch]

+1. Any news?

[askmike]

fixed in 0.2.