URL
No response
Issue Description
The usage has increased and the caching is not covering this usage increase with a single free API token.
The error message is also not helpful. It says Stats not found, but, their not found because it returns a 429, too many requests.
Solution:
Additionally, a mechanism needs to be added to allow users to securely add additional API keys to the pool, while also being able to determine if a key has been invalidated or deleted and automatically removed it from the pool. This wont happen in this update, but eventually...
Updates
Both fixes are live in 0.0.36. Currently there are 2 API keys loaded, which should be enough for now. The fix is currently very simple, it cycles through each key in round-robbin style.
That being said, there is not yet a method to invalidate keys, so I can only use known good keys, otherwise it would have intermittent failures.
URL
No response
Issue Description
The usage has increased and the caching is not covering this usage increase with a single free API token.
The error message is also not helpful. It says Stats not found, but, their not found because it returns a 429, too many requests.
Solution:
Additionally, a mechanism needs to be added to allow users to securely add additional API keys to the pool, while also being able to determine if a key has been invalidated or deleted and automatically removed it from the pool. This wont happen in this update, but eventually...
Updates
Both fixes are live in 0.0.36. Currently there are 2 API keys loaded, which should be enough for now. The fix is currently very simple, it cycles through each key in round-robbin style.
That being said, there is not yet a method to invalidate keys, so I can only use known good keys, otherwise it would have intermittent failures.