Sylvain
Sylvain
@walec51 , i thought it was enabled by default. ` if (exSpec.getResilience() != null) { exSpec.getResilience().setRateLimiterEnabled(true); exSpec.getResilience().setRetryEnabled(true); } ` That's right ?
I've tried with resilience, same result : ` org.knowm.xchange.binance.dto.BinanceException: Too much request weight used; current limit is 1200 request weight per 1 MINUTE. Please use the websocket for live updates...
Same error here.
Hello, still no updates on this ?
Hello, ok well, i will setup a reverse proxy as a workaround. Thanks
Hello @fangfufu, it would be a good feature. Are you still planning to implement it on a near future ? Have a good day.
Hello, Unfortunately, the server contains private documents, so I cannot share it. The server is running Ubuntu 23.04, Kernel 6.2.0-39-generic. However, I can test the issue on an Arch or...
Hello, i have just tested the last master version with your commits ``` unique: 614, opcode: READ (15), nodeid: 3, insize: 80, pid: 1184337 read[140658435329408] 131072 bytes from 4571136 flags:...
Retested : Fatal:../src/cache.c:565:Cache_free: could not destroy w_lock: 16, Device or resource busy! I confirm all logs originate from httpdirfs (tested with the -d parameter). When reading a file, I observe...
More logs : Error req_size != recv, req_size: 8388608, recv: 8388608 is suspicious. Also : Thread 69f2b6c0 read cache Thread 5bfff6c0 try to free cache ? ``` Debug:../src/cache.c:1100:Cache_read: thread 69f2b6c0:...