fix: Fix OOM error when a bad api key is passed #210
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Mercy811
approved these changes
Aug 8, 2024
yuhao900914
reviewed
Aug 8, 2024
yuhao900914
approved these changes
Aug 8, 2024
github-actions bot
pushed a commit
that referenced
this pull request
Aug 9, 2024
## [1.17.1](v1.17.0...v1.17.1) (2024-08-09) ### Bug Fixes * Fix OOM error when a bad api key is passed ([#210](#210)) ([8f1c047](8f1c047))
|
🎉 This PR is included in version 1.17.1 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
When the server returns a 400 because of a bad api key, we continuously retry without dropping the data. This fixes that issue
Fixes issue #208
Checklist