Closed dbrennand closed 3 years ago
Hmm odd. I re-run the code a few minutes later and now the issue is no longer occurring. ๐ค
Is this occurring because I am hitting the API rate limit perhaps?
Hi, glad to see you were able to resolve the issue/the issue resolved itself.
This kind of error occurs for some API error messages due to the server reporting the response type as plain text while returning JSON data, which upsets the ClientResponse.json()
method as per your snippet.
The current master branch should be able to handle this error state - I assume you are on an older version as run_query
is defined on line 106 (it has moved since then๐
)?
Sorry about the versioning, it's been a bit of a mess lately and I have not gotten around to fix it. ๐ฌ
Hi, glad to see you were able to resolve the issue/the issue resolved itself.
This kind of error occurs for some API error messages due to the server reporting the response type as plain text while returning JSON data, which upsets the
ClientResponse.json()
method as per your snippet.The current master branch should be able to handle this error state - I assume you are on an older version as
run_query
is defined on line 106 (it has moved since then๐ )?Sorry about the versioning, it's been a bit of a mess lately and I have not gotten around to fix it. ๐ฌ
Hi @leonhard-s
I am using whatever is the latest version available via pip ๐
auraxium 0.1.0a1
Hm... I'll have to take a look at that, then.
Thanks again for the report, as I said this should already be resolved - I'll tidy up any loose ends and push a new version as soon as I can find the time.
Hi,
I just ran into an issue using the library.
The following code produces the error:
My code: