You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it could be useful to be able to setup up Base API URL for Embedding Model as well. For example if we use a custom Base API URL in Language Model to query OpenAI gpt-4, it is reasonable that we want to use the same custom Base API URL when hitting /embeddings endpoint.
Proposed Solution
From the frontend prospective I think that a new text field, similar to the Language model Base API URL
is consistent with the design principle.
I'm not sure sure about the backend implementation.
The text was updated successfully, but these errors were encountered:
Thank you for opening your first issue in this project! Engagement like this is essential for open source projects! 🤗
If you haven't done so already, check out Jupyter's Code of Conduct. Also, please try to follow the issue template as it helps other other community members to contribute more effectively.
You can meet the other Jovyans by joining our Discourse forum. There is also an intro thread there where you can stop by and say Hi! 👋
Thanks for reporting this issue! Sorry this went undiscovered for so long. I've assigned another contributor to this issue and added it to a milestone for tracking.
Problem
I think it could be useful to be able to setup up
Base API URL
for Embedding Model as well. For example if we use a customBase API URL
in Language Model to query OpenAI gpt-4, it is reasonable that we want to use the same customBase API URL
when hitting/embeddings
endpoint.Proposed Solution
From the frontend prospective I think that a new text field, similar to the
Language model Base API URL
is consistent with the design principle.
I'm not sure sure about the backend implementation.
The text was updated successfully, but these errors were encountered: