Skip to content

fix: return a more sophisticated error for device failure on 429 #11554

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

Merged
merged 2 commits into from
Jan 10, 2024

Conversation

Emyrk
Copy link
Member

@Emyrk Emyrk commented Jan 10, 2024

@mafredri you were right.

I think we should be checking more status codes, but I was only able to reproduce a 429 atm. I do not have the test env to know what the correct status codes are.

@Emyrk Emyrk requested a review from mafredri January 10, 2024 16:03
Copy link
Member

@mafredri mafredri left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice 👍🏻

@Emyrk
Copy link
Member Author

Emyrk commented Jan 10, 2024

Added a quick unit test

@Emyrk Emyrk merged commit 04afb88 into main Jan 10, 2024
@Emyrk Emyrk deleted the stevenmasley/device_429 branch January 10, 2024 17:29
@github-actions github-actions bot locked and limited conversation to collaborators Jan 10, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants