Lena
Lena
Thanks for reporting @sam31415 . It's a hard one in terms of reproduction, we will continue investigating.
@Ericxgao , just to make sure I understand you correctly: you reach the rate limit due to the downloaded benchmark data or because you are trading many coins live in...
Thanks for the feedback @salihkilic , we will check this. Regarding the declaration of the history function, it is located at the Cython `_protocol.pyx` file, which in turn calls the...
@salihkilic , as mentioned, Bitfinex has a very low rate limit, meaning it can be challenging to perform many requests to this exchange each frame. When trying to assess the...
@kooomix, the rate limit is exchange specific and can vary between different API calls. To have a sense of the rate limit of the exchange you are using you can...
Thanks @avolution for bringing this up. We will look at it.
Hi @eranhirs , Does the issue occur after trying to ingest again using `catalyst ingest-exchange -x binance -f minute -i omg_btc`? If so, on what dates you are running your...
@sam31415 and @eranhirs , Perhaps the first ingestion of the data was corrupted. If you don’t have too much data ingested already, I would try to workaround this by clearing...
Hi @AndrejLischishin , What mode are you referring to?
Thanks @Thomas214 for opening this!