allow null usage for OpenAI embedding model #2488
Merged
Conversation
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
dev-jonghoonpark
force-pushed
the
feature/allow-null-usage-for-openai-models
branch
from
9ac0321 to
a11ceef
Compare
Signed-off-by: jonghoon park <[email protected]>
dev-jonghoonpark
force-pushed
the
feature/allow-null-usage-for-openai-models
branch
from
a11ceef to
24af5ef
Compare
dev-jonghoonpark
changed the title
Member
|
@dev-jonghoonpark Thanks for fixing this. |
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.
The issue described in #2485, where a NullPointerException (NPE) occurs when the
usagefield is null in OpenAI-compatible models, has been fixed.