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

Better handle nil response status in client #127

Merged
merged 2 commits into from
Nov 7, 2024
Merged

Conversation

sampart
Copy link
Contributor

@sampart sampart commented Nov 6, 2024

I've seen responses have a nil status when we're experiencing availability issues, so this prevents an "undefined method `>=' for nil" exception.

I've seen responses have a nil status when we're experiencing availability issues, so this prevents an "undefined method `>=' for nil" exception.
@arthurnn arthurnn merged commit 5be26e5 into arthurnn:main Nov 7, 2024
@arthurnn
Copy link
Owner

arthurnn commented Nov 7, 2024

thanks

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.

2 participants