Closed jurekl closed 9 months ago
mikekonan
commented
2 years ago Thanks for the report.
It will be really good if you will provide the results of the GET klines request. You can find the path in proxy logs enabling verbose 1.
It will be like /kucoin/api/v1/market/candles?symbol=LPT-USDT&type=5min&startAt=1642382225&endAt=1642532225 so you need to curl to proxy, and kucoin API to compare the results.
jurekl
commented
2 years ago Hey Mike, I'll try, of course, but a bit later. I supplemented the info with the proxy and golang versions, because I am trying to build the proxy myself, on my VPS.
As it happens in life, it can be hellishly difficult to find a possible error / defect, because I have been using your proxy from the beginning and only yesterday I discovered such a glaring case as the rejection of 95% coins due to their age. The age of 4 days for 95 coins seems rather unlikely. When I get the data you mention, I will paste it right here!
jurekl
commented
2 years ago I ran two commands:
curl -o response-kucoin.txt 'https://openapi-v2.kucoin.com/api/v1/market/candles?symbol=LPT-USDT&type=5min&startAt=1642382225&endAt=1642532225'and the next one
curl -o response-proxy.txt 'https://localhost:9000/api/v1/market/candles?symbol=LPT-USDT&type=5min&startAt=1642382225&endAt=1642532225'Comparing the contents of the two files containing the klines showed that they are identical.
This test of mine is probably of little value, as it would have to be checked online, on the current data, with more or less up-to-date unix timestamp
I downloaded the release https://github.com/mikekonan/exchange-proxy/releases/download/v1.2.1/exchange-proxy_1.2.1_linux_arm64.tar.gz and installed it instead of my own build. I will test this variant for some time ...
mikekonan
commented
2 years ago Q: Comparing the contents of the two files containing the klines showed that they are identical. A: You have to call the request for pair that was filtered by age/volatility filter. And I guess that timeframe will be like 1d, for sure you can match the correct request log time.
mikekonan
commented
2 years ago jurekl
commented
2 years ago Sorry Mike, this link https://github.com/mikekonan/exchange-proxy/releases/tag/untagged-5ed2f32e1b9b19addfab
takes me to 404
mikekonan
commented
2 years ago mikekonan
commented
2 years ago There are no fixes for these issues, but more fresh version
jurekl
commented
2 years ago But this is the version (1.2.6) that I have been using for several days (January 14th, I think).
commit 3f96b22542fd9dcb8656f4d1717f7e6e34d015be (HEAD -> main, tag: v1.2.6, origin/main, origin/HEAD)
Author: Mikalai Konan <mikalai.konan@icloud.com>
Date: Fri Jan 14 15:23:58 2022 +0300
suikula
commented
2 years ago Hello, Im having same problems with the latest version (v1.2.6).
2022-02-09 07:28:13,811 - AgeFilter - INFO - Removed ADA/USDT from whitelist, because age 5 is less than 14 days 2022-02-09 07:28:13,812 - AgeFilter - INFO - Removed ALGO/USDT from whitelist, because age 5 is less than 14 days 2022-02-09 07:28:13,819 - AgeFilter - INFO - Removed AVAX/USDT from whitelist, because age 5 is less than 14 days 2022-02-09 07:28:13,820 - AgeFilter - INFO - Removed AXS/USDT from whitelist, because age 5 is less than 14 days 2022-02-09 07:28:13,820 - AgeFilter - INFO - Removed BTT/USDT from whitelist, because age 5 is less than 14 days 2022-02-09 07:28:13,820 - AgeFilter - INFO - Removed COTI/USDT from whitelist, because age 5 is less than 14 days 2022-02-09 07:28:13,820 - AgeFilter - INFO - Removed CRV/USDT from whitelist, because age 5 is less than 14 days 2022-02-09 07:28:13,821 - AgeFilter - INFO - Removed DOGE/USDT from whitelist, because age 5 is less than 14 days 2022-02-09 07:28:13,821 - AgeFilter - INFO - Removed DOT/USDT from whitelist, because age 5 is less than 14 days 2022-02-09 07:28:13,821 - AgeFilter - INFO - Removed ENJ/USDT from whitelist, because age 5 is less than 14 days
$ go version go version go1.17.3 linux/arm64
VanessaE
commented
1 year ago I have this problem also. It's been a year since the last comment or commit... is this project still being maintained?
mikekonan
commented
1 year ago Greetings! First and foremost, I must mention that I am unable to devote significant time and attention to maintaining the project. The challenges are the inadequacy and instability of the kucoin WebSocket API and the inefficient performance of the lazy initiation approach with freqtrade. An easy and stupid solution would be to implement a health check that enables docker to restart the proxy as required. On the other hand, the optimal solution would involve the distribution of workers that listen to kucoin WebSocket, albeit at the cost of making deployment hard and challenging for the average user.
Hi Mike, Unfortunately, it is still not good. I have in the configuration, among others:
I just noticed in FreqUI that my whiltelist is only 5 pairs. A quick check in the FT log and we see such wonders:
In any case, out of the expected 100 * / USDT pairs, 95 pairs were dropped, which is obvious nonsense, if only because all these 95 pairs were 4 days old.
The glitch mentioned reappears very irregularly, for a while everything seems to be working fine, then there is a case of clearing the whitelist to zero, or a fraction of what it should contain.
After launching my FT for Kucoin without a proxy, it works rather poorly / sluggishly for me, but at least I have an expected list. After starting FT without a proxy, I have in my log:
It turns out that pairs that were previously supposed to be 4 days old are now "correct", validated
I've seen signals with similar behavior using your proxy for a long time. I would be very glad if you could look at this problem again ...
Best wishes :-)
P.S. I build the proxy myself on my VPS with
from version: