You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the daily request limit is exceeded, the client should throw an exception. Instead, the request just hangs forever. I can get around this by wrapping the call in some clever timeout code, but the API itself should fail immediately with an informative exception.
I can reproduce this by just running the example code in a loop 50 times, sleeping for a second between each request so as not to exceed the rate limit.
If I try the request through curl, I get a JSON response saying "rate limit exceeded", so it's clear the result is coming through somewhere, it's just not being interpreted correctly.
The text was updated successfully, but these errors were encountered:
@mhoban The API itself, as you noted, will send a prompt 429 response with the "rate limit exceeded" message. This client is generated using the OpenAPI Generator.
I see support for rate limiting was added to the C# client a few years ago, but I can't find anything for Python. We may need to submit an improvement request with that project.
I suspected it was something like that. In the meantime, it looks like the client will just just keep re-trying until the request limit resets which in this particular case actually works out just fine.
When the daily request limit is exceeded, the client should throw an exception. Instead, the request just hangs forever. I can get around this by wrapping the call in some clever timeout code, but the API itself should fail immediately with an informative exception.
I can reproduce this by just running the example code in a loop 50 times, sleeping for a second between each request so as not to exceed the rate limit.
If I try the request through curl, I get a JSON response saying "rate limit exceeded", so it's clear the result is coming through somewhere, it's just not being interpreted correctly.
The text was updated successfully, but these errors were encountered: