Fix response UnboundError when request fails and custom tenacity.Retrying
is used
#713
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 PR closes #693
It also removes
InstructorRetryException
insidewith attempts
clause as it seems redundant.Summary:
This PR fixes an UnboundError by initializing
response
toNone
in retry functions and simplifies error handling by removing redundant exception raising, with added tests for verification.Key points:
response
toNone
inretry_sync
andretry_async
functions ininstructor/retry.py
to preventUnboundError
.InstructorRetryException
raising within retry loops, simplifying error handling.test_openai/test_retries.py
with a new test casetest_custom_retry_response_error
to verify correct error handling with custom retry strategy.Generated with ❤️ by ellipsis.dev