-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
querying instant exchange orders triggers the rate limit #193
Comments
i noticed this while reviewing #177 |
We can utilize an exchange rate cache and WebSocket connection(if available) like in #177. But to keep the scope small, this can be implemented in another PR. |
Another PR, is fine, but it should follow immediately after #177 It should be better for 177, to leave out exchange rate query for the cex pages, i think that would be better, rather that introducing a regression into the codebase. |
Uhmm, can you shed more light on this? |
It seems the centralized exchange pages were modified to work with the websockets? And that's what causing the cex apis to reach reate limit |
Oh, now I understand. Yes, the page is refreshed and since caches are not yet implemented for CEX we end up with multiple requests. I've increased the notification interval in #177. |
still getting this as of today
|
we seem to be query the cex api's too frequently
The text was updated successfully, but these errors were encountered: