Florian Sabani
Florian Sabani
https://api.exchange.bullish.com/docs/api/rest/trading-api/v2/#overview--exchange-time 😄 🙏🏼
Do you have any idea what we could do to overcome it? I'll have to do extra work later if another bug gets fixed on the latest version, at least...
@ko0f I've personally updated to Node20 and I got the error vanish
I thinks sometimes it's fine to get connection errors from the proxy server, e.g. "RequestTimeout" for example. Is there any way within CCXT to catch those requests and retry them...
I see, for my use case, I'd like to find a "general way" to test this behaviour for all exchanges. Consequently, is there no way (even a work-around) to verify...
Please 🙏🏻
That would be very useful indeed. I would like the NAT instance to have some external IPs within an "IP list" (allow-list). Perhaps the "eip_id" directive in the configuration file...
Thank you Andrew for the update. Do you think it is somehow possible to achieve the same result with the current version of fck-nat? Maybe by spinning up `5 different...
https://github.com/nuxt/nuxt/issues/13488#issue-1549563113 I'm also having this error on @auth/core 0.17.0
Awesome job man. Are those limits HTTP calls or actual number of records returned for example: `get_user_tweets[tweet_type="Replies"] 50 ` Means 50 tweets fetched every 15 min, or 50 get_user_tweet calls...