Open
Conversation
Author
|
I guess I should also point out that you can control what I'm trying to do with the |
Contributor
|
+1 I would structured data to not be turned into string. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This is just a proposal, but basically I have a reasonably complex workflow that requires a lot of calls to the OAI API. Because of this, I'm running into rate limit issues that I would like to handle by adding some retries with backoff functionality. I can just match on
{:error, _}, but having the raw errors would make things a bit easier because I can handle the specific case where the API returns a rate-limit exceeded error and do the retries in that case. Thoughts?