Skip to content

Conversation

@jaymzh
Copy link

@jaymzh jaymzh commented Apr 15, 2025

Currently if you get a 429 (or any other we theoretically catch), we
won't catch it because we're doing string comparisons on integers, and
thus we jsut get a JSON::ParserError.

This fixes that so we get the expected error classes.

In addition it adds a new unknown exception that gives the use some
extra information.

Signed-off-by: Phil Dibowitz phil@ipom.com

Currently if you get a 429 (or any other we theoretically catch), we
won't catch it because we're doing string comparisons on integers, and
thus we jsut get a JSON::ParserError.

This fixes that so we get the expected error classes.

In addition it adds a new unknown exception that gives the use some
extra information.

Signed-off-by: Phil Dibowitz <phil@ipom.com>
@jaymzh
Copy link
Author

jaymzh commented May 15, 2025

@buntine - any chance you can look at this (and my other) PR?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant