Skip to content
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

algod: Even in the face of urllib.error.HTTPError, return the json #529

Merged
merged 1 commit into from
Jun 5, 2024

Conversation

jannotti
Copy link
Contributor

Previously, if we caught a urllib.error.HTTPError, we would try to parse the json response. If we succeeded we would return only the message field of that response. If we failed, we're return the text of the response. By "return" here, I actually mean "pack up into an Exception object and throw it".

Now, if succeed in parsing the response as json, we extend that exception object so that it also contains the JSON that we got. That way, client code can find extra goodies in the json["data"] field.

Also added a utility to the examples so they can be easily run against a locally running algod.

Previously, if we caught a urllib.error.HTTPError, we would try to
parse the json response. If we succeeded we would return _only_ the
`message` field of that response. If we failed, we're return the text
of the response.  By "return" here, I actually mean "pack up into an
Exception object and throw it".

Now, if succeed in parsing the response as json, we extend that
exception object so that it also contains the JSON that we got. That
way, client code can find extra goodies in the json["data"] field.

Also added a utility to the examples so they can be easily run against
a locally running `algod`.
@gmalouf gmalouf merged commit 1b345cf into algorand:develop Jun 5, 2024
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants