fix: handling OpenAI returning None objects #2280
Merged
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.
What does this PR do?
Fixes #2176
OpenAI sometimes returns a None type object instead of a response object. This could happen when you, for instance, run into a rate limit issue or a content violation error. To prevent the whole run to fail, a check is added if the response object is not of type None, if the object is of type None, the label for that specific topic is set to "No label returned". This approach of handling an issue when generating the label for a topic was chosen in a previous iteration and is kept as is.
No documentation has been added with this PR since this is a very minor fix that doesn't influence documentation. There has been a comment added to the code in line with a previously iteration done to the code.
No tests have been added.
Before submitting